+MartyBartfast Posted April 6, 2017 Share Posted April 6, 2017 I just discovered today that if I try and view a log entry, either by clicking the "view log" link from a gallery picture, or by clicking the view/edit log link below one of my own logs then I get the 403.6 - Forbidden IP address of the client has been rejected. The requested page can not be accessed via anony mous proxies. error. This is an example of a blocked link While I am using my works Internet proxy connection I can access all other site components OK, including writing a log, so it seems there's some inconsistency in the way log.aspx is detecting the proxies. Quote Link to comment
+x_xenolith_x Posted April 13, 2017 Share Posted April 13, 2017 (edited) Had the same issue many years ago. Was using a Blackberry with Opera browser. I had to ditch the BB. Check your browser and/or VPN Edited April 13, 2017 by x_xenolith_x Quote Link to comment
+MartyBartfast Posted April 13, 2017 Author Share Posted April 13, 2017 Had the same issue many years ago. Was using a Blackberry with Opera browser. I had to ditch the BB. Check your browser and/or VPN The Opera Browser used to use a proxy to cache images and speed up browsing, which is why it used to be picked up by the proxy detection. In my case it shouldn't be picking me up as using a proxy (I'm not), and the fact that I can write logs substantiates that. However when I go to edit a log I just wrote then it incorrectly detects a proxy, which suggests that GS are doing the proxy detection differently on the the edit link and it's that inconsistency that's more of a problem. Quote Link to comment
+wxsby Posted April 22, 2017 Share Posted April 22, 2017 I now have this exact problem. Have tried with my PC & laptop, with both Firefox and Microsoft Edge, and my Android tablet with Chrome. Same result every time. I have Cox internet with the same service for many years. I don't know what a proxy is. What am I doing wrong? Quote Link to comment
+p0cy Posted June 16, 2017 Share Posted June 16, 2017 Same for me. For a couple of weeks, when I try to log a cache or a TB, I receive the following message: 403.6 - Forbidden IP address of the client has been rejected. PC with Windows 7, same issue using IE or Chrome. Deleting cookies didn't help. Access to all other pages of the site is fine. Any hint ? Quote Link to comment
+Team DEMP Posted June 22, 2017 Share Posted June 22, 2017 (edited) Just noticed at work that I now get the anonymous proxy error when looking to Add/Edit logs. A couple weeks ago this worked fine from my office when I logged some OM on caches. Edited June 22, 2017 by Team DEMP Quote Link to comment
+niraD Posted July 11, 2017 Share Posted July 11, 2017 I keep running into this when I view calendar appointments at work. Geocaching events include links (e.g., http://coord.info/GC773F9 ), and I can view the event details by following the links, but I can't post a "Will Attend" from work because I get: 403.6 - Forbidden IP address of the client has been rejected. The requested page can not be accessed via anonymous proxies. Quote Link to comment
+Optimist on the run Posted July 13, 2017 Share Posted July 13, 2017 I'm getting the same problem trying to log a "Will attend" for a forthcoming CITO. Could a lackey comment on this please? Quote Link to comment
+smudge42 Posted July 20, 2017 Share Posted July 20, 2017 I am receiving 403.6 errors on links that previously worked. e.g. log a TB or visit logs IP address of the client has been rejected. The requested page can not be accessed via anonymous proxies. Quote Link to comment
+smudge42 Posted July 20, 2017 Share Posted July 20, 2017 Bumping this, as I also started receiving this error today. Never had it before, so something has changed in the way the requests are handled? Quote Link to comment
+MartyBartfast Posted July 20, 2017 Author Share Posted July 20, 2017 (edited) For what it's worth I'm nolonger seeing this problem :-o Edited July 20, 2017 by MartyBartfast Quote Link to comment
+p0cy Posted July 24, 2017 Share Posted July 24, 2017 On 20/07/2017 at 4:54 PM, MartyBartfast said: For what it's worth I'm nolonger seeing this problem :-o Same for me : the problem no longer appears. Quote Link to comment
+Spliffa Posted July 26, 2017 Share Posted July 26, 2017 I haven't encountered this problem either the past few days. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.