VK4P4tpn 0 Posted ... Hi, Whenever I try to access airvpn.org using Chrome I get an HTTP 429 response with the following on the page: We're sorry, our tubes are clogged up.Your IP or your IP range is temporarily suspended.We're working to deliver more tubes on a bigger truck and solve the problem.Please see https://twitter.com/airvpn for information and updates in the meantime. However it doesn't seem to have anything to do with my IP as I can access the site with Firefox (or with Chrome when I specify a Firefox user agent). My normal user agent is Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/65.0.3325.181 Chrome/65.0.3325.181 Safari/537.36 I get the same response using a Chrome on Windows or Chrome on Android user agent as well. However if I switch to a Firefox or Edge user agent I can access the site with no problem. It is not a big deal since I have a workaround. But, I was wondering if anyone has seen this before and has any idea how to resolve it? Thanks. Quote Share this post Link to post
Staff 9972 Posted ... Hello! Can you please try to delete cookies and cache on the "problematic" Chrome and check whether the problem remains the same or not? Kind regards Quote Share this post Link to post
madrat 19 Posted ... Hi, Whenever I try to access airvpn.org using Chrome I get an HTTP 429 response with the following on the page: We're sorry, our tubes are clogged up.Your IP or your IP range is temporarily suspended.We're working to deliver more tubes on a bigger truck and solve the problem.Please see https://twitter.com/airvpn for information and updates in the meantime. However it doesn't seem to have anything to do with my IP as I can access the site with Firefox (or with Chrome when I specify a Firefox user agent). My normal user agent is Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/65.0.3325.181 Chrome/65.0.3325.181 Safari/537.36 I get the same response using a Chrome on Windows or Chrome on Android user agent as well. However if I switch to a Firefox or Edge user agent I can access the site with no problem. It is not a big deal since I have a workaround. But, I was wondering if anyone has seen this before and has any idea how to resolve it? Thanks. Have been getting the exact same notification off and on for the last few days now. I'm on Firefox, OSX El Capitan and Eddie 2.17.2. Changing the server from one Vancouver server to another Vancouver server fixed the problem for me last time I got the message. Also, sometimes I could access the site, but got the notification each time I tried to log in. Quote Share this post Link to post
VK4P4tpn 0 Posted ... Clearing cookies and cache did nothing. It seems to have something to do with the specific version of Chrome. All it takes is for the string 65.0.3325.181 to be in the user agent. If anyone from AirVPN is reading this. I can reliably reproduce the issue from multiple IPs with: curl -A "65.0.3325.181" https://airvpn.org but as long as the user agent does not contain that string I get the normal main page. For example: curl -A "65.0.3325.182" https://airvpn.org returns the normal main page. FYI -- This version of Chrome is the latest available on Raspberry Pis. Quote Share this post Link to post
Staff 9972 Posted ... Clearing cookies and cache did nothing. It seems to have something to do with the specific version of Chrome. All it takes is for the string 65.0.3325.181 to be in the user agent. If anyone from AirVPN is reading this. I can reliably reproduce the issue from multiple IPs with: curl -A "65.0.3325.181" https://airvpn.org but as long as the user agent does not contain that string I get the normal main page. For example: Thank you very much! Under investigation. Kind regards Quote Share this post Link to post
Staff 9972 Posted ... Hello! Problem has been fixed, can you please test again? Kind regards 1 madrat reacted to this Quote Share this post Link to post
madrat 19 Posted ... Hello! Problem has been fixed, can you please test again? Kind regards I personally have not had the problem since I made the last post. All seems fixed. Quote Share this post Link to post