Exploratory Public: When trying to close a project, it failed with git timeout error

Issues
#1

With Public Edition, when you try to close a project, you might get this error.

fatal: unable to access 'https://exploratory.io/git/abcd/Test.git/': Failed to connect to exploratory.io port 443: Timed out

This error suggests that Git cannot connect to the server at exploratory.io on port 443 (the standard port for HTTPS). Several potential root causes for this issue include:

  1. Network Connectivity Issues:
  • The client machine may be experiencing network problems that prevent it from reaching the server. This could be due to:
    • Unstable or disconnected internet connection.
    • Issues with local network configuration, such as a firewall blocking outgoing requests on port 443.
  1. DNS Resolution Issues:
  • The client might be unable to resolve the domain name exploratory.io due to DNS configuration issues. You can check if you can resolve the domain by using commands like ping exploratory.io or nslookup exploratory.io to ensure the DNS is functioning correctly.
  1. Server Downtime:
  • The server at exploratory.io might be temporarily down or experiencing high traffic, making it unable to respond within the timeout period.
  1. Blocked by Firewall or Proxy:
  • Some corporate or personal firewall settings or proxy servers might block the request to the domain or the port. Check if a proxy is being used in your network and whether it has restrictions in place.
  1. Port Blocked on Client:
  • The local machine’s firewall could be configured to block outbound traffic on port 443, preventing the Git client from making a secure connection.
  1. Incorrect Git Configuration:
  • There could be a misconfiguration in Git, such as a wrong proxy setting, that prevents it from connecting to the remote repository.
  • You can check if a proxy is set using git config --global --get http.proxy.

Troubleshooting Steps:

  • Check Network: Ensure that your internet connection is stable and the domain exploratory.io is reachable.
  • Test DNS Resolution: Use ping or nslookup to check whether the domain resolves properly.
  • Check Proxy/Firewall Settings: Verify if there are any proxy settings in Git (git config --global --get http.proxy) or a firewall blocking the request.
  • Try a Different Network: If possible, switch to a different network to determine if the issue is local to your current network.
1 Like