DanPan
-
Posts
520 -
Joined
-
Last visited
Posts posted by DanPan
-
-
Today, I did a "refresh cache data" of 21 caches and my API daily download balance count was reduced with 42 or 200%...
-
Een dikke pluim aan het voltallige BE-NL reviewers-team voor de vele reviews (> 20 per dag) die jullie dagelijks verrichten!
Ik zie ook dat het BE-NL team uitgebreid werd met Vandergore (zie log)
-
Veel Belgjes zitten hier niet op het Nederlandstalig forum.
Probeer eens hier op het forum van www.geocaching.be
-
-
I did a refresh of 220 caches and my API balance was reduced with 250, due to the retries...
-
After 4 days still no communication from Groundspeak.
I guess everyone at GS is on holidays?
We just have to sit and wait...
-
When i connect to www.geocaching.com i always have to sign in again, even when "Keep me signed in" was selected before.
I'm using a non-shared single computer with IE8.
I am the only one who has this problem?
-
It may be limited to a specific funtion. Last night I added a bunch of caches to a bookmark list from GSAK using the API and it worked fine. What were you trying to do? That info might help GC find it.
"Refresh Cache Data" does not work as before, a lot of retries and no response errors from GS API.
Refresh caches with c:geo, GAPP and "GSAK/Get Recent Logs" work fine. Whacky...
-
I had same issue this morning until I upgraded to ver 8.3.1.29 and then it worked.
Upgrading to GSAK 8.3.1.29 does NOT solve the issue.
It seems the API config is changed at GS side.
We have to wait for a response/confirmation from GS.
-
In GSAK i got "Geocaching.com api error: There was a problem communicating with the Groundspeak api", which i never had before.
Is this error related to the Danish release or another change GS did...?
PLEASE communicate and inform your customers proactively.
-
"Geocaching.com api error: There was a problem communicating with the Groundspeak api"
It is not possible anymore to refresh cache data with GSAK. I just want to refresh 220 caches...
It seems the API service is down or temporarily suspending accepting new requests.
Generating GPX file
... no response after 20 seconds
... no response after 40 seconds
... no response after 20 seconds
... no response after 40 seconds
... no response after 20 seconds
... no response after 40 seconds
... no response after 20 seconds
... no response after 40 seconds
... no response after 20 seconds
... no response after 40 seconds
... no response after 20 seconds
... no response after 40 seconds
... no response after 20 seconds
... no response after 40 seconds
... no response after 20 seconds
... no response after 40 seconds
... no response after 60 seconds
Previous request ended in error, now doing a retry.... 1/4
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 1/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 2/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 3/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 4/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 5/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 6/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 7/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 8/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 9/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 10/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 11/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 12/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 13/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 14/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 15/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 16/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 17/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 18/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 19/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 20/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 21/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 22/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 23/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 24/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 25/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 26/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 27/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 28/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 29/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 30/30
Retry requested by user
... no response after 20 seconds
... no response after 40 seconds
... no response after 60 seconds
Previous request ended in error, now doing a retry.... 1/4
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 1/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 2/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 3/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 4/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 5/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 6/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 7/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 8/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 9/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 10/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 11/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 12/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 13/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 14/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 15/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 16/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 17/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 18/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 19/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 20/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 21/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 22/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 23/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 24/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 25/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 26/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 27/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 28/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 29/30
Previous request ended in error, now doing a retry.... 1/4
Retry delay started: 30/30
Retry requested by user
... no response after 20 seconds
... no response after 40 seconds
... no response after 20 seconds
... no response after 40 seconds
-
Indeed, a lot of no responses/retries on the API when using GSAK/refresh caches:
2013-07-10 16:59:15 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 17:06:58 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 17:07:44 No response: 40 seconds (ver:8.3.1.14)
2013-07-10 17:08:32 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 17:08:32 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 17:10:18 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 17:16:20 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 17:16:40 No response: 40 seconds (ver:8.3.1.14)
2013-07-10 17:17:00 No response: 60 seconds (ver:8.3.1.14)
2013-07-10 17:17:51 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 17:18:11 No response: 40 seconds (ver:8.3.1.14)
2013-07-10 17:18:31 No response: 60 seconds (ver:8.3.1.14)
2013-07-10 17:19:21 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 17:19:41 No response: 40 seconds (ver:8.3.1.14)
2013-07-10 17:20:01 No response: 60 seconds (ver:8.3.1.14)
2013-07-10 22:42:18 No response: 40 seconds (ver:8.3.1.14)
2013-07-10 22:43:08 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 22:43:28 No response: 40 seconds (ver:8.3.1.14)
2013-07-10 22:44:16 No response: 20 seconds (ver:8.3.1.14)
2013-07-10 22:46:18 No response: 40 seconds (ver:8.3.1.14)
-
Looks like Groundspeak has fixed the issues "View logbook" and "Load Cache Logs..."
Thx!
-
Looks like Groundspeak has fixed it.
Thx!
-
FYI: Groundspeak has fixed it. Language preference is now saved between logout/login sessions.
Thx!
-
I continue to see "Loading Cache Logs.../View Logbook" problems.
I am using IE on Server: WEB19; Build: Web.HotFix_20130709.1
-
The link to status.geocaching.com in the "Maintenance banner" on the frontpage is not correct.
http://status.geocaching.com/%20target= should be http://status.geocaching.com/
-
Nice lips...
This issue started and was first reported in Dec 2011 (SUBMITTED (33056) - [bUG] Forum Avatars "Scrambled")
It seems that GS give up to solve this very annoying problem...
-
Same issue here, after login the language is changed to English.
-
Does your browser accept cookies?
-
In deze topic worden gelijkaardige problemen met de kaarten gemeld.
Na het uitschakelen van de firewall in de router is bij sommige gebruikers het probleem opgelost.
-
En heeft je zoon samen met zijn klasgenoten een cache kunnen vinden?
-
We've been told that Groundspeak does read all the suggestions in here, but they no longer respond to them. ... ...I used to defend Groundspeak vociferously, but it's hard to do that anymore.
Same feeling... +1
-
This is not a bug, this is "by design".
Souvenirs not shown in user profile
in Website
Posted · Edited by DanPan
It seems there is an isue with loading the souvenirs in the user profiles, only a red cross is showned.
example