+Clifton Posted February 10, 2014 Share Posted February 10, 2014 When I press on "Share this log" on geocaching.com, then normally Facebook copies the log text and adds a nice link to the geocache text. Since a week or so, the texts are copied, but the links is an error message stating "403.6 Forbidden: IP address of the client has been rejected". Who rejects this (FB.com? GC.com? something else?), and for which device is the IP address: my own laptop? GC.com? FB.com? Or perhaps a better question: who is to solve this? Regards, Wim van Dorst (Clifton) Quote Link to comment
Moun10Bike Posted February 10, 2014 Share Posted February 10, 2014 This is a known issue that the team is investigating. Quote Link to comment
+Dgwphotos Posted February 15, 2014 Share Posted February 15, 2014 When I press on "Share this log" on geocaching.com, then normally Facebook copies the log text and adds a nice link to the geocache text. Since a week or so, the texts are copied, but the links is an error message stating "403.6 Forbidden: IP address of the client has been rejected". Who rejects this (FB.com? GC.com? something else?), and for which device is the IP address: my own laptop? GC.com? FB.com? Or perhaps a better question: who is to solve this? Regards, Wim van Dorst (Clifton) I've seen this myself, and weirdly, it doesn't actually reject anything. I can click on the link, and follow it straight to the cache page. Quote Link to comment
+Clifton Posted February 17, 2014 Author Share Posted February 17, 2014 When I press on "Share this log" on geocaching.com, then normally Facebook copies the log text and adds a nice link to the geocache text. Since a week or so, the texts are copied, but the links is an error message stating "403.6 Forbidden: IP address of the client has been rejected". Who rejects this (FB.com? GC.com? something else?), and for which device is the IP address: my own laptop? GC.com? FB.com? Or perhaps a better question: who is to solve this? Regards, Wim van Dorst (Clifton) I've seen this myself, and weirdly, it doesn't actually reject anything. I can click on the link, and follow it straight to the cache page. The links indeed work normally, but instead of a nice cache icon indicing the cache type and a normally readable name, it shows the unpleasant error message. But apparently no solution yet. Regards, Wim (Clifton) Quote Link to comment
+Lejanna Posted February 18, 2014 Share Posted February 18, 2014 I'm having the exact same problem. It's very frustrating but I'm glad that geocaching.com is working on it. Quote Link to comment
+FinnAlex Posted February 19, 2014 Share Posted February 19, 2014 I have the same problem. Hope that Groundspeak will solve the problem Quote Link to comment
+gplamy Posted February 19, 2014 Share Posted February 19, 2014 Sadly, this 403.6 error started occurring to us "non-smartphone" cachers about a year ago whenever we tried to access any cache page. It was reported as a bug at the time, but has never been resolved. Those with phones like mine are no longer able to get any kind of cache information out in the field. It has to do with how the host making the call (my phone or facebook) is passed back to the website, as websites attempt to block automated (robo) accesses to their sites. Has been frustrating to have this capability nonfunctional for this long but apparently that's just how it's going to be... Quote Link to comment
Moun10Bike Posted February 20, 2014 Share Posted February 20, 2014 Our IT team has been investigating this issue and it looks like a block of FacebookIPs were getting detected as anonymous proxies (which are intentionally blocked). These have now been unblocked. Facebook posts should now work; if not, let us know the cache or log ID for the Facebook postand we can then reference that to find the Facebook IP to unblock. Quote Link to comment
+northernpenguin Posted February 20, 2014 Share Posted February 20, 2014 1392860310[/url]' post='5353306']Our IT team has been investigating this issue and it looks like a block of FacebookIPs were getting detected as anonymous proxies (which are intentionally blocked). These have now been unblocked. Facebook posts should now work; if not, let us know the cache or log ID for the Facebook postand we can then reference that to find the Facebook IP to unblock. Just an FYI this intentional blocking also has the side effect of taking out some smartphone browsers that feature data compression, like Opera Mini. Chrome recently added this so watch you don't inadvertently block Chrome users on Android and iOS devices. Problem is most noticeable when trying to view a cache page in Opera Mini for example. Quote Link to comment
+Dgwphotos Posted February 22, 2014 Share Posted February 22, 2014 Our IT team has been investigating this issue and it looks like a block of FacebookIPs were getting detected as anonymous proxies (which are intentionally blocked). These have now been unblocked. Facebook posts should now work; if not, let us know the cache or log ID for the Facebook post and we can then reference that to find the Facebook IP to unblock. Still getting it here. Quote Link to comment
+Lil Devil Posted February 23, 2014 Share Posted February 23, 2014 Our IT team has been investigating this issue and it looks like a block of FacebookIPs were getting detected as anonymous proxies (which are intentionally blocked). These have now been unblocked. Facebook posts should now work; if not, let us know the cache or log ID for the Facebook post and we can then reference that to find the Facebook IP to unblock. Still getting it here. Please note the request in bold above. They need your help to fix it. Quote Link to comment
+Dgwphotos Posted February 23, 2014 Share Posted February 23, 2014 Our IT team has been investigating this issue and it looks like a block of FacebookIPs were getting detected as anonymous proxies (which are intentionally blocked). These have now been unblocked. Facebook posts should now work; if not, let us know the cache or log ID for the Facebook post and we can then reference that to find the Facebook IP to unblock. Still getting it here. Please note the request in bold above. They need your help to fix it. Which I did... Quote Link to comment
BlueRajah Posted February 24, 2014 Share Posted February 24, 2014 (edited) Every cache I have seen is blocked for the past few weeks. These are a few going through my stream. These are posts since Friday that give those errors on facebook http://coord.info/GC4R86B http://coord.info/GC4YXGC http://coord.info/GC4YWBN http://coord.info/GC4YERT http://coord.info/GC4YET9 http://coord.info/GC4YYVC http://coord.info/GC4R9R1 http://coord.info/GC4R9R1 Edited February 24, 2014 by BlueRajah Quote Link to comment
Moun10Bike Posted February 24, 2014 Share Posted February 24, 2014 The IT team has whitelisted the block of Facebook IPs that were identified by the reports of this issue from over the weekend. Please continue to to report instances of this error if you continue to see it. Thanks! Quote Link to comment
+verano Posted January 16, 2015 Share Posted January 16, 2015 This is a consistent problem when posting about geocaching.com pages on Facebook. Some geocaching.com links display thumbnails, some don't. It is really vital for telling the local community about upcoming events to be able to post thumbnails on FB. Today I tried to share a link for an upcoming event, and no go (http://www.coord.info/GC5K88X). Yesterday I did one and it worked fine. None of the online "solutions" for "fixing" links that do not show thumbnails on FB work. The debug shows 403.6 forbidden. -Debbi Quote Link to comment
+LeGodFather Posted December 12, 2015 Share Posted December 12, 2015 The IT team has whitelisted the block of Facebook IPs that were identified by the reports of this issue from over the weekend. Please continue to to report instances of this error if you continue to see it. Thanks! It's been happening again, since yesterday (Dec 11, 2015) Quote Link to comment
+lovekansas Posted December 13, 2015 Share Posted December 13, 2015 I'm glad someone else has noticed it! It isn't like it's stopping me from clicking through to the cache pages, but it just isn't very nice looking. LOL! I really hope someone sees this if they aren't already aware of the issue. Quote Link to comment
Moun10Bike Posted December 14, 2015 Share Posted December 14, 2015 Can you point me to some examples of where you are seeing this issue? Quote Link to comment
Moun10Bike Posted December 14, 2015 Share Posted December 14, 2015 Our IT department has just informed me that they've whitelisted all Facebook IPs. Please let us know if you continue to see this issue. Quote Link to comment
+Lil Devil Posted December 19, 2015 Share Posted December 19, 2015 Our IT department has just informed me that they've whitelisted all Facebook IPs. Please let us know if you continue to see this issue. You missed at least one. About a half hour ago, this cache was posted to a Facebook group, and the preview said "403.6 Forbidden: IP address of the client has been rejected" Quote Link to comment
+HedgHg88 Posted December 19, 2015 Share Posted December 19, 2015 https://m.facebook.com/groups/411330335620099?view=permalink&id=954639667955827 Quote Link to comment
+Rustynails Posted December 19, 2015 Share Posted December 19, 2015 https://m.facebook.com/groups/411330335620099?view=permalink&id=954639667955827 Someone please fix this frustrating problem. Quote Link to comment
+Rustynails Posted December 19, 2015 Share Posted December 19, 2015 (edited) Our IT department has just informed me that they've whitelisted all Facebook IPs. Please let us know if you continue to see this issue. Not fixed. Please read the reply above. Edited December 19, 2015 by rustynails. Quote Link to comment
+Rustynails Posted December 20, 2015 Share Posted December 20, 2015 Our IT department has just informed me that they've whitelisted all Facebook IPs. Please let us know if you continue to see this issue. Not fixed. Please read the reply above. Still BROKEN. Anyone looking at this? Quote Link to comment
+Lil Devil Posted December 20, 2015 Share Posted December 20, 2015 Still BROKEN. Anyone looking at this? rustynails, you've posted 3 times over this weekend. No one is going to look at this until Monday at least. Chill. Quote Link to comment
+ahomburg Posted December 20, 2015 Share Posted December 20, 2015 I think that it is only specific groups. I tried to share to https://www.facebook.com/groups/geocachingmelbourne/ and got the error, but when I shared to https://www.facebook.com/groups/t5geocachingaustralia/, it worked perfectly. Anyway, watching this thread for a fix. Quote Link to comment
+NYPaddleCacher Posted December 20, 2015 Share Posted December 20, 2015 I think that it is only specific groups. I tried to share to https://www.facebook...chingmelbourne/ and got the error, but when I shared to https://www.facebook...chingaustralia/, it worked perfectly. Anyway, watching this thread for a fix. Seems to be showing up here a lot as well: https://www.facebook.com/groups/geocachingpuzzlehelp/ Quote Link to comment
+ARZEL_QC Posted December 21, 2015 Share Posted December 21, 2015 depuis la parution des events organisés pour célébrer la fin de l'année et le début de l'année... donc depuis la mi-décembre, je n'arrive pas à publier les caches dans Facebook http://coord.info/GC67ZND http://coord.info/GC67ZER 403.6 FORBIDDEN :IP ADRESS of the client has been rejected WHY? thank to answer me ARZEL_QC Quote Link to comment
Moun10Bike Posted December 21, 2015 Share Posted December 21, 2015 Our IT team has indicated that they have discovered some additional blocks of Facebook IP addresses and have now whitelisted them. Please continue to let us know if you see this issue. Quote Link to comment
+Rustynails Posted December 22, 2015 Share Posted December 22, 2015 Our IT team has indicated that they have discovered some additional blocks of Facebook IP addresses and have now whitelisted them. Please continue to let us know if you see this issue. Still broken. Please fix this. https://www.facebook.com/groups/54671531070/ and https://www.facebook.com/groups/411330335620099/ Quote Link to comment
+NYPaddleCacher Posted December 22, 2015 Share Posted December 22, 2015 Our IT team has indicated that they have discovered some additional blocks of Facebook IP addresses and have now whitelisted them. Please continue to let us know if you see this issue. Still broken. Please fix this. https://www.facebook...ps/54671531070/ and https://www.facebook...11330335620099/ Have a little patience. It sounds like GS is working on it and it would be easy if there was a definitive list of Facebook IP addresses available somewhere that could be used but it doesn't sound like there is. Quote Link to comment
Moun10Bike Posted December 22, 2015 Share Posted December 22, 2015 I believe it is fixed, but Facebook caches the link when it is first posted. You could try using a different variant of the link (e.g. coord.info vs. geocaching.com), or try purging the cache for that listing via this tool and then reposting. Quote Link to comment
+Rustynails Posted December 22, 2015 Share Posted December 22, 2015 Tried both ways and now tried them again. Some success as I now see the event logo. However the event name is not shown but replaced with that error message. https://www.facebook.com/groups/411330335620099/ Don't know what to do with that help link. Quote Link to comment
+Mr. 0 Posted February 29, 2016 Share Posted February 29, 2016 I'm curious if the various posting to Facebook issues have been resolved, or if I'm doing something wrong. After logging a cache I get the screen saying "Your logs were successfully sent to Geocaching.com" then ask to share to FB and/or Twitter. When I click the slider to select Facebook, it takes me to facebook.com and says "You have already authorized Geocaching.com" and gives the options "cancel" and "ok." When I select OK, it takes me back to the "share with friends" page within the app. When I then click "continue", nothing at all happens. It just stays on the same screen, and I've confirmed nothing is posted to Facebook. 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.