Glideport problem

On Tuesday, June 4, 2019 at 1:38:25 PM UTC-6, soarsz wrote:
When I originally posted my concern about Glideport, I was unable to get it to accept my new Garmin/Inreach mapshare link. I tried again a few days ago and Glideport accepted my link, and my wife subsequently saw my tracking. I have since then gone back to check and my new link is still there, so I think someone has fixed the code issue which was causing a problem with the changed mapshare format introduced by Garmin sometime in the last few months.

Monday morning, none of the contests were loading, only normal tracking was working. However, contests loaded fine a bit later. Perhaps a server restart was in progress earlier, or a process had to be restarted. Never heard back if there was intervention.

Frank Whiteley

On Tuesday, June 4, 2019 at 12:46:01 PM UTC-7, Frank Whiteley wrote:
On Tuesday, June 4, 2019 at 1:38:25 PM UTC-6, soarsz wrote:
When I originally posted my concern about Glideport, I was unable to get it to accept my new Garmin/Inreach mapshare link. I tried again a few days ago and Glideport accepted my link, and my wife subsequently saw my tracking. I have since then gone back to check and my new link is still there, so I think someone has fixed the code issue which was causing a problem with the changed mapshare format introduced by Garmin sometime in the last few months.

Monday morning, none of the contests were loading, only normal tracking was working. However, contests loaded fine a bit later. Perhaps a server restart was in progress earlier, or a process had to be restarted. Never heard back if there was intervention.

Frank Whiteley

There are multiple unrelated issues reported in this thread.
First the format is still https://share.garmin.com/xxxxxxx the new format someone suggested is incorrect so dont try this new format.
The issue I am having has nothing to do with anything discussed here. According to Pedja “GP has logic that when there are many unsuccessful consecutive attempts to retrieve data for a device, it gives up and marks the device as invalid. Apparently inReach servers were down for long enough for that to happen…�

This issue repeated itself for me twice a year and for those who fly less frequently maybe not as often. But the end result is that once your InReach is marked as invalid you will never show up again without admin intervention. Creating a new account does not fix the issue. I know of few other inreaches which were dropped permanently and I bet there are many more. I suggested to Pedja at the rime to remove this logic of marking devices as invalid when servers are down, but I guess this logic still exists and now there is no one to fix this. I would be happy to click a donate button if this will help sustaining and improving this valuable service.

Bottom line, glideport is unreliable now.

Sigh!

Ramy

On Tuesday, June 4, 2019 at 2:50:40 PM UTC-6, Ramy wrote:
On Tuesday, June 4, 2019 at 12:46:01 PM UTC-7, Frank Whiteley wrote:
On Tuesday, June 4, 2019 at 1:38:25 PM UTC-6, soarsz wrote:
When I originally posted my concern about Glideport, I was unable to get it to accept my new Garmin/Inreach mapshare link. I tried again a few days ago and Glideport accepted my link, and my wife subsequently saw my tracking. I have since then gone back to check and my new link is still there, so I think someone has fixed the code issue which was causing a problem with the changed mapshare format introduced by Garmin sometime in the last few months.

Monday morning, none of the contests were loading, only normal tracking was working. However, contests loaded fine a bit later. Perhaps a server restart was in progress earlier, or a process had to be restarted. Never heard back if there was intervention.

Frank Whiteley

There are multiple unrelated issues reported in this thread.
First the format is still https://share.garmin.com/xxxxxxx the new format someone suggested is incorrect so dont try this new format.
The issue I am having has nothing to do with anything discussed here. According to Pedja “GP has logic that when there are many unsuccessful consecutive attempts to retrieve data for a device, it gives up and marks the device as invalid. Apparently inReach servers were down for long enough for that to happen…�

This issue repeated itself for me twice a year and for those who fly less frequently maybe not as often. But the end result is that once your InReach is marked as invalid you will never show up again without admin intervention. Creating a new account does not fix the issue. I know of few other inreaches which were dropped permanently and I bet there are many more. I suggested to Pedja at the rime to remove this logic of marking devices as invalid when servers are down, but I guess this logic still exists and now there is no one to fix this. I would be happy to click a donate button if this will help sustaining and improving this valuable service.

Bottom line, glideport is unreliable now.

Sigh!

Ramy

Ramy,

Appreciate your comments. SSA has been discussing the issue and we'll consider suggestions.

Frank Whiteley

The new format is provided by Garmin on new inReach devices and they have been unwilling to assign the original format. Glideport would need to be modified to accept the new format to work for new purchasers of inReach devices.