Birdseye & Geocaching.com not working
-
- Posts: 8
- Joined: Thu Nov 11, 2021 8:52 pm
Birdseye & Geocaching.com not working
Hi,
First I have to say that I already submitted this information to Garmin, so this message is just to hear from others if they experience the same problems and making my information available to them.
The problem is that the Birdseye Imagery has never worked since I bought the device last week. Reset done, no solution, different networks, no solution ...
The second problem is that I never managed to get a registration code for the Geocaching.com site. When I try it from my device, i always get a 'Registration Failed' message.
So after trying a lot of things and submitting my problem to Garmin Tech Support, they weren't able to help me so far. Since i'm working in the IT business, I was able to capture the network traffic between my Garmin and the servers, and guess what, both Birdseye & Geocaching are hosted on the same Akamai infrastructure, so the same server is used for both. That makes sense as both items are not working for me.
So I captured the traffic, and i'll explain shortly what's happening here so everyone can see the problem :
Birdseye Imagery Problem :
Connection is tried to : (Hostname: a88-221-180-177.deploy.static.akamaitechnologies.com)
1 0.000000 10.10.10.44 88.221.180.177 TCP 109 50627 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
Connection is acknowledged to the garmin device :
2 0.024421 88.221.180.177 10.10.10.44 TCP 109 443 → 50627 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 WS=128
Garmin device acknowledges the answer from the server :
3 0.026076 10.10.10.44 88.221.180.177 TCP 107 50627 → 443 [ACK] Seq=1 Ack=1 Win=262140 Len=0
Garmin device sends a 'hello' to let the server know the data can be transferred :
4 0.404111 10.10.10.44 88.221.180.177 TLSv1 259 Client Hello
Server sends first packet :
5 0.411774 88.221.180.177 10.10.10.44 TCP 101 443 → 50627 [ACK] Seq=1 Ack=159 Win=64128 Len=0
Server sends a handshake failure error :
6 0.413347 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
devices acknowledges the error and sends the necessary acks and finishes the connection
This time the device sets up a new connection :
10 0.468903 10.10.10.44 88.221.180.177 TCP 109 50628 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
The server acknowledges the connection request :
11 0.493720 88.221.180.177 10.10.10.44 TCP 101 443 → 50627 [ACK] Seq=9 Ack=160 Win=64128 Len=0
The server acknowledges the connection setup and the garmin too
The garmin sends a new message that it is ready for data transfer, this time in TLSv1.2 as the TLSv1 did not work :
14 1.022909 10.10.10.44 88.221.180.177 TLSv1.2 259 Client Hello
Again, the server sends a handshake failure message, so also TLSv1.2 doesn't work :
16 1.023155 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
From this point, the same process goes on and on, every time a new connection is tried with TLSv1.2 but the server returns a handshake failure.
Geocaching.com problem :
Connection is tried to the same Akamai server as the birdseye :
1 0.000000 10.10.10.44 88.221.180.177 TCP 109 50705 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
The same handshake failure as with the birdseye is happening :
6 0.614230 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
As you can see, there is definitely a problem with the handshaking, a protocol issue, certificate issue in the garmin devices .... ????
Regards,
Bart
First I have to say that I already submitted this information to Garmin, so this message is just to hear from others if they experience the same problems and making my information available to them.
The problem is that the Birdseye Imagery has never worked since I bought the device last week. Reset done, no solution, different networks, no solution ...
The second problem is that I never managed to get a registration code for the Geocaching.com site. When I try it from my device, i always get a 'Registration Failed' message.
So after trying a lot of things and submitting my problem to Garmin Tech Support, they weren't able to help me so far. Since i'm working in the IT business, I was able to capture the network traffic between my Garmin and the servers, and guess what, both Birdseye & Geocaching are hosted on the same Akamai infrastructure, so the same server is used for both. That makes sense as both items are not working for me.
So I captured the traffic, and i'll explain shortly what's happening here so everyone can see the problem :
Birdseye Imagery Problem :
Connection is tried to : (Hostname: a88-221-180-177.deploy.static.akamaitechnologies.com)
1 0.000000 10.10.10.44 88.221.180.177 TCP 109 50627 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
Connection is acknowledged to the garmin device :
2 0.024421 88.221.180.177 10.10.10.44 TCP 109 443 → 50627 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 WS=128
Garmin device acknowledges the answer from the server :
3 0.026076 10.10.10.44 88.221.180.177 TCP 107 50627 → 443 [ACK] Seq=1 Ack=1 Win=262140 Len=0
Garmin device sends a 'hello' to let the server know the data can be transferred :
4 0.404111 10.10.10.44 88.221.180.177 TLSv1 259 Client Hello
Server sends first packet :
5 0.411774 88.221.180.177 10.10.10.44 TCP 101 443 → 50627 [ACK] Seq=1 Ack=159 Win=64128 Len=0
Server sends a handshake failure error :
6 0.413347 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
devices acknowledges the error and sends the necessary acks and finishes the connection
This time the device sets up a new connection :
10 0.468903 10.10.10.44 88.221.180.177 TCP 109 50628 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
The server acknowledges the connection request :
11 0.493720 88.221.180.177 10.10.10.44 TCP 101 443 → 50627 [ACK] Seq=9 Ack=160 Win=64128 Len=0
The server acknowledges the connection setup and the garmin too
The garmin sends a new message that it is ready for data transfer, this time in TLSv1.2 as the TLSv1 did not work :
14 1.022909 10.10.10.44 88.221.180.177 TLSv1.2 259 Client Hello
Again, the server sends a handshake failure message, so also TLSv1.2 doesn't work :
16 1.023155 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
From this point, the same process goes on and on, every time a new connection is tried with TLSv1.2 but the server returns a handshake failure.
Geocaching.com problem :
Connection is tried to the same Akamai server as the birdseye :
1 0.000000 10.10.10.44 88.221.180.177 TCP 109 50705 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
The same handshake failure as with the birdseye is happening :
6 0.614230 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
As you can see, there is definitely a problem with the handshaking, a protocol issue, certificate issue in the garmin devices .... ????
Regards,
Bart
-
- Posts: 8
- Joined: Thu Nov 11, 2021 8:52 pm
Re: Birdseye & Geocaching.com not working
When trying to download Birdseye Imagery through Basecamp with the Garmin connected (see attached screenshot)
So I think it's not specifically on the device ??
So I think it's not specifically on the device ??
You do not have the required permissions to view the files attached to this post.
- GPSrChive
- Site Admin
- Posts: 3921
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Birdseye & Geocaching.com not working
Just tested both services on multiple devices, all worked flawlessly.
Until we tested the 66sr, which failed both.
Multiple attempts did finally see the geocaching registration succeed, and BirdsEye imagery was downloaded.
Reported to Garmin.
Until we tested the 66sr, which failed both.
Multiple attempts did finally see the geocaching registration succeed, and BirdsEye imagery was downloaded.
Reported to Garmin.
-
- Posts: 8
- Joined: Thu Nov 11, 2021 8:52 pm
Re: Birdseye & Geocaching.com not working
I literally tried a thousand times. Didnt work, they filed a case finally.
What more proof do they want, a whole insight of the network communication that fails ...
Ill try again continuously until it works
What more proof do they want, a whole insight of the network communication that fails ...
Ill try again continuously until it works
-
- Posts: 8
- Joined: Thu Nov 11, 2021 8:52 pm
Re: Birdseye & Geocaching.com not working
Hi,
I still cannot get birdseye direct working on my 66sr. It is already swapped for another one, still doesn't work. Who else has the same problems ??
KR
Bart
I still cannot get birdseye direct working on my 66sr. It is already swapped for another one, still doesn't work. Who else has the same problems ??
KR
Bart
- GPSrChive
- Site Admin
- Posts: 3921
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Birdseye & Geocaching.com not working
We were something similar, our 66sr just displaying 'waiting for connection to BirdsEye servers...' indefinitely. But after waiting for about five minutes it finally connected and worked OK after that.
How far in the process can you get with your 66sr?
How far in the process can you get with your 66sr?
-
- Posts: 8
- Joined: Thu Nov 11, 2021 8:52 pm
Re: Birdseye & Geocaching.com not working
Hi,
My 66sr always says 'Waiting for connection to Birdseye imagery servers '. Even under the 'Download' button it says the same. After a minute or so it just times out with the message 'Cannot connect to the imagery servers. Check your connection, and try again. '
No matter how many times i try. With smartphone connected or not, wifi or 4g on smartphone , no difference.
Who can help ??
My 66sr always says 'Waiting for connection to Birdseye imagery servers '. Even under the 'Download' button it says the same. After a minute or so it just times out with the message 'Cannot connect to the imagery servers. Check your connection, and try again. '
No matter how many times i try. With smartphone connected or not, wifi or 4g on smartphone , no difference.
Who can help ??
- GPSrChive
- Site Admin
- Posts: 3921
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Birdseye & Geocaching.com not working
We just tested our GPSMAP 66sr and Montana 750i, and both display the "Waiting for connection to BirdsEye imagery servers." message.
After a few minutes, the GPSMAP 66sr eventually made the connection, but our Montanan 750i still has not.
I suspect Garmin BirdsEye servers are experiencing some technical issues at the moment resulting in intermittent connection success.
The good news is that your GPSMAP 66sr is not the problem.
The bad news is there is nothing you can currently do to resolve the issue.
Perhaps contact Garmin to open a support ticket?
After a few minutes, the GPSMAP 66sr eventually made the connection, but our Montanan 750i still has not.
I suspect Garmin BirdsEye servers are experiencing some technical issues at the moment resulting in intermittent connection success.
The good news is that your GPSMAP 66sr is not the problem.
The bad news is there is nothing you can currently do to resolve the issue.
Perhaps contact Garmin to open a support ticket?
-
- Posts: 949
- Joined: Sat Jan 16, 2021 4:08 pm
Re: Birdseye & Geocaching.com not working
Can't confirm. Used yesterday and today BirdsEye direct to download some maps. Worked like a charm on my Montana.
Garmin DriveSmart 86 MT-D (FW 6.80, HW V8, GPS 9.00.50, 32GB SD)
Garmin Montana 750i (FW 19.00, HW V6, GPS 2.90, Touchscreen 85.07, 64GB SD)
Garmin Montana 750i (FW 19.00, HW V6, GPS 2.90, Touchscreen 85.07, 64GB SD)
-
- Posts: 8
- Joined: Thu Nov 11, 2021 8:52 pm
Re: Birdseye & Geocaching.com not working
I have some very good news. God knows why, but when i ran basecamp and connected my 66sr by usb, went to birdseye. I could download imagery !!! I was connected to my hotspot on my mobile phone instead of normal WiFi. When everything worked in basecamp, i disconnected the usb cable, connected to the normal wifi with the 66sr and went to birdseye direct. It also worked from there now ! So once activated, it seems to work with whatever connection, but to make it work the very first time, i had to use basecamp with the hotspot.
So if someone else ever experience this ... you know what to do.
So if someone else ever experience this ... you know what to do.