'Log Your Visit' Not working

[+TwoNomadicBrits 0]

Is there a problem with the site this morning? I'm just trying to log caches found in the last three days and the button 'Log Your Visit' on the cache page gives me this error message:

 

An Error Has Occurred

Your request has resulted in an error. Please return to this site's home page to continue.

 

I also get the same message if I click 'Log Visit' from the box that appears from the map before actually selected the link to view the complete cache page.

 

Is this a known bug today... or just me?!

[+TwoNomadicBrits 0]

Logging via the app does seem to be working, but I don't want to do that as I try to have a story to tell which will be just a pain to type in on the iPhone! []

[+KST44 0]

I am experiencing the same problem, so it is not just you ! Let's hope this problem will be solved very quickly !

 

 

Is there a problem with the site this morning? I'm just trying to log caches found in the last three days and the button 'Log Your Visit' on the cache page gives me this error message:

 

An Error Has Occurred

Your request has resulted in an error. Please return to this site's home page to continue.

 

I also get the same message if I click 'Log Visit' from the box that appears from the map before actually selected the link to view the complete cache page.

 

Is this a known bug today... or just me?!

[+on4bam 1524]

Just tried it and get the normal logpage. I haven't logged any caches via the site since GSAK does a better job at it via the API though.

[+RecipeForDisaster 21]

I have been having this problem also. I tried to log via the map, the "log a cache" page, and the regular old button. Very frustrating! What is weird is that I had just logged one cache with no problem, and went on to the second to find that I couldn't log anymore.

[+KST44 0]

Same to me, I logged a cache yesterday and as I wanted to log a second, it gave me the error. I contacted Groundspeak for this problem.

Still hoping for a very quick solution...

[+gogrannie 0]

Same problem works on lap top but not on IPad. Hope it is fixed soon.

[+Skoki 0]

I am having the same problem. Was able to log a find early last evening, then later in the evening was unable. No change this morning.... very frustrating! Anyone have any suggestions? I so rarely have problems on this site that it's disconcerting when something doesn't work. Hope this is fixed soon!

[+hilltoppper 0]

For me it started yesterday. I get the same messages. I'm using an iPad and the web page. Not the app. Tried the usual stuff of restarting and clearing cache if that might help. Glad I'm not alone!

[+Michaelcycle 163]

I've had the same problem since last night. Tried the usual restart, etc. still getting the error page no matter which cache I try to log.

 

Running: Safari 8.0.6 on MacBook Pro with OS 10.10.3

[+DadOf6Furrballs 2]

It's working for some people, apparently. I've been getting find logs on our caches, and other notifications elsewhere. Both yesterday, last night, and this morning.

[Moun10Bike 471]

This definitely is not a global issue - I was able to log a couple of caches successfully this morning on the web site. If you encounter this error, could you please post the exact time when you hit it and what server you are on (back up one page from the error, view the page source, then look at the very bottom for server info, or visit http://www.geocaching.com/whoami)? Thanks!

[gearguru 1]

I had this same issue several times last night and again this morning, just tried a few minutes ago and I am still getting the following message

 

An Error Has Occurred

Your request has resulted in an error. Please return to this site's home page to continue.

 

tried at 11:01 am PDT

I am: WEB01

You are: 24.113.73.146

 

I hope this helps!

[+TwoNomadicBrits 0]

This definitely is not a global issue - I was able to log a couple of caches successfully this morning on the web site. If you encounter this error, could you please post the exact time when you hit it and what server you are on (back up one page from the error, view the page source, then look at the very bottom for server info, or visit http://www.geocaching.com/whoami)? Thanks!

 

Time - 19:06 BST

Server - WEB03

 

I've been getting it all day, but just seen your reply and tried it again.

Edited July 8, 2015 by TwoNomadicBrits

[+TwoNomadicBrits 0]

Just tried again switching my VPN off.

 

Time 19:10 BST

Server - WEB15

[+Michaelcycle 163]

Another fail just now:

 

I am: WEB04

[bigfishvt 0]

i still can't log geocaches.

 

i am- web07

 

you are- 66.30.53.16

[+der_mountainbiker 0]

This definitely is not a global issue - I was able to log a couple of caches successfully this morning on the web site. If you encounter this error, could you please post the exact time when you hit it and what server you are on (back up one page from the error, view the page source, then look at the very bottom for server info, or visit http://www.geocaching.com/whoami)? Thanks!

 

It depends what you mean by "global issue". I´m experiencing these problems here in Austria ... I have several issues the last 12 hours, since about 6 hours I´m not able to post new logs ... regardless which cache I try to log ... There are also troubles visiting the stats etc.

 

"An Error Has Occurred

 

Your request has resulted in an error. Please return to this site's home page to continue."

 

ThanX.

 

I am: WEB16

You are: 81.217.xx.xx

Edited July 8, 2015 by der_mountainbiker

[+TwoNomadicBrits 0]

Time: 19:43 BST

Server - WEB06

 

From a 'global' perspective, I am in Turkey but it also didn't work connecting via a UK VPN.

Edited July 8, 2015 by TwoNomadicBrits

[+TwoNomadicBrits 0]

Time - 19:46 BST

Server - WEB15

 

Connected through a USA VPN.

[stebu 2]

This definitely is not a global issue - I was able to log a couple of caches successfully this morning on the web site. If you encounter this error, could you please post the exact time when you hit it and what server you are on (back up one page from the error, view the page source, then look at the very bottom for server info, or visit http://www.geocaching.com/whoami)? Thanks!

I can't give you an example, but this has been reported in Finland by several people. So that makes it pretty global

[+der_mountainbiker 0]

I am: WEB02

You are: 81.217.xx.xx

 

2100 local time (Austria)

 

I tried to log this cache: http://www.geocaching.com/geocache/GC49FFW_die-brucke-von-steinegg but it does not depent on special caches as I even can´t log ANY cache for now - even caches outside of Austria e.g.

 

Some hours before the whole site "http://www.Waymarking.com" has been down for hours which is now available again.

Edited July 8, 2015 by der_mountainbiker

[+der_mountainbiker 0]

Strange - works with Firefox (39) but not in Safari 8.0.7

[+der_mountainbiker 0]

Seems the problem has something to do with cookies ... when I delete all cookies in Safari the error-page does NOT appear! Strange.

[+TwoNomadicBrits 0]

I now have 22 caches I'm unable to log. Hope it gets fixed soon!

I just tried to log on an iPad through safari and I still got the error message.

[+TwoNomadicBrits 0]

Seems the problem has something to do with cookies ... when I delete all cookies in Safari the error-page does NOT appear! Strange.

 

Have you tried to log a second one? I was able to log one this morning and then that was it.

 

I will give the cookies thing a try tomorrow. It's bed time now here in Turkey

I was using a MacBook earlier, so maybe it's a safari issue, but it's the first time I've had this problem and I've not changed any of my settings (or downloaded the newest update I keep getting reminders for!).

 

Thanks for the suggestion.

[+isenfriesen 0]

This happens to me, too. I'm in Austria

 

I am: WEB09

You are: 93.82.12.175

 

and I could log the first of Monday's caches, but no more.

Edited July 8, 2015 by isenfriesen

[Moun10Bike 471]

I'm not seeing anything corresponding to these events in the logs on the indicated servers, so a dev is likely going to have to investigate, provided we can get more information.

 

Have you tried logging out and back in? A cookie issue could be at the root of the problem as der_mountainbiker has suggested (we have been making changes around that and session state in order to improve performance). Please try clearing cookies and then let me know if the issue clears up and/or returns.

 

Thanks for your patience.

[+The A-Team 1861]

FWIW, I have no problems here in Western Canada on two completely different Windows systems (work and home) using IE, Chrome, and Firefox. I am WEB01 and WEB02 on the respective systems.

 

However, when I just tested from my iPhone using Safari, I get the error message whether I'm connected to wifi or just using the cell network. On wifi, I'm WEB18, and on the cell data I'm WEB16.

[+der_mountainbiker 0]

I could log all my caches and TBs using Firefox instead of Safari on OS X 10.10.4.

 

Log out/log in did not change anything in Safari.

 

When I delete all cockies and go to "Log your visit", the for the moment usual error page does not appears but the information that I should log in ...

 

In Firefox no troubles at all, sole the average D/T rating is not shown (broken icon instead).

Edited July 8, 2015 by der_mountainbiker

[+hilltoppper 0]

This definitely is not a global issue - I was able to log a couple of caches successfully this morning on the web site. If you encounter this error, could you please post the exact time when you hit it and what server you are on (back up one page from the error, view the page source, then look at the very bottom for server info, or visit http://www.geocaching.com/whoami)? Thanks!

[+hilltoppper 0]

I'm on WEB 02 at 3:56CDT. Here is what I see. I'm using an iPad via wifi. Latest Safafi and IOS. I cannot log a cache so I clear and log out completely from GC web page. Then I go to Settings and clear cookies and history. Then I log back into GC web page, go to cache in question and I can log it. However, if I go to another cache to log, BANG, the error message returns.

 

So, by exiting, clearing cookies, re entering GC, I can log only one cache without getting the error.

[Moun10Bike 471]

From the data compiled so far it appears possible that the cookie is in some instances storing the last log date in a format that it then cannot subsequently read. This would explain why the first log works after clearing cookies, but not the next one.

 

For those who are running into this, could you please provide:

 

• The browser and version you are using, and on what platform
• What your language/region settings are on the device running that browser
• Your chosen date format

Thanks again!

[+der_mountainbiker 0]

• Safari, 8.0.7, OS X 10.10.4

• German

• 08.07.2015

[+hilltoppper 0]

Safari on iPad version 8.4

Gregorian calendar

English language

Mm/dd/yyyy

 

Is that sufficient?

[+stenll 0]

Mac OS 10.10.3

Safari Version 8.0.6 (10600.6.3)

Swedish

yyyy-mm-dd

 

On the same computer, I tried Chrome to log my founds - it worked!

Google Chrome Version 43.0.2357.130 (64-bit)

[Moun10Bike 471]

We pushed out an update about 20 minutes ago that we think will address the problem (although we can't be sure as we have not been able to repro this issue in-house). Can you check and see if you still run into this problem?

[+dcaches 0]

iPad version 8.3

English

Month/day/year

 

Hi I was having this problem yesterday, seems to work ok today though. No error message.

Edited July 9, 2015 by cdcaches

[+KST44 0]

I got an answer from Groundspeak. They suggested to delete all cookies and try again. So, I deleted cookies and ... it works again :-) I logged all my caches !

[+Michaelcycle 163]

We pushed out an update about 20 minutes ago that we think will address the problem (although we can't be sure as we have not been able to repro this issue in-house). Can you check and see if you still run into this problem?

 

Jon, just logged four caches without issue. Thanks for the quick work on this fix!

[+der_mountainbiker 0]

Yes, seems to work - fine!

 

The only thing that does not work is average Difficulty/average Terrain - that´s sometimes not working since at least one week.

 

Thanx a lot for your support!

[gearguru 1]

Jon everything seems to be working fine at this moment. I am running Safari 7.0.6 on a MacBook Pro with OS X 10.9.5 date format is mm dd yyyy Thank you for the quick work in resolving this issue. Thanks Jeff

[+TwoNomadicBrits 0]

Everything working fine for me this morning too, without me having to do any logging in/out or clearing cookies. I've been able to log more than one on both the iPad and Macbook (via Safari running 10.10.3. date format DDMMYYYY English language)

 

Thank you for a swift resolution!

[+knowschad 20]

We pushed out an update about 20 minutes ago that we think will address the problem (although we can't be sure as we have not been able to repro this issue in-house). Can you check and see if you still run into this problem?

Nice job of deducing the problem and implementing a fast fix! Well done!