How to resolve the “Unable to reach JFrog Artifactory” error while browsing Artifacts

JFrog Support
2023-01-22 11:09

Sometimes your Artifactory UI may be slow to respond to the point that the system will time out and generate the following error message:

Should this occur, to capture the details regarding this error you can use the Chrome as follows: Tools > More Tools > Developer Tools > Network. More information regarding how to measure resource loading times is available HERE.

In the course of executing your details capture, Chrome’s Network tool might return an HTTP response that looks like this:

response: 

status: 504,
statusText: "Gateway Time-out",
httpVersion: "HTTP/1.1",
}

In this instance, you’ll want to ensure that your proxy is not timing out before Artifactory finishes any of its requests. A status: 504 browse failure message could mean that this is precisely the problem. If so, you’ll need to make an adjustment to the Nginx proxy for your Artifactory server by adding these variables (in seconds) to your nginx.conf file:

proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 600;

If Apache is serving as the proxy for your Artifactory server, try adding these variables (in seconds) to your httpd.conf file:

# Timeout: The number of seconds before receives and sends time out.
Timeout 600

Let’s take a look at another example:

"response": {
"status": 0,
"statusText": "",
"httpVersion": "unknown",
"headers": [],
"cookies": [],
"content": {
"size": 0,
"mimeType": "x-unknown"
},
"redirectURL": "",
"headersSize": -1,
"bodySize": -1,
"_transferSize": 0,
"_error": "net::ERR_BLOCKED_BY_CLIENT"
}

According to research, the status message: ERR_BLOCKED_BY_CLIENT can be caused by Adblocker or a similar ad-blocking extension (about which, more information is available HERE), which can detect a keyword in the URI like "ad" and block it. Should you be using this type of content filter, try disabling it or whitelisting Artifactory to see if this doesn’t resolve the issue.
 

Further Troubleshooting
If none of the recommendations above proves helpful in resolving the issue you’re encountering, collect the following pieces of information and send them to JFrog Support for further investigation:

  • Detailed steps to reproduce the issue
  • Use the Chrome browser to capture the encountered error (as described at the beginning of this article). Thereafter, save your data in a HAR file by following the instructions available HERE.
  • Your Artifactory version number
  • The version number of your proxy (e.g., Nginx or Apache)
  • Your Artifactory logs
  • Your proxy’s logs
  • Your proxy configuration files