PP feeders with changed share codes


#1

Some Planeplotter share codes have recently been recycled so users are reminded to register their new codes in FlightAware to maintain their feeds.


#2

Im about to dump PP alltogether. 2nd or 3rd time Ive had to redo it all My 3 servers I never have issues with backing up data
for users.

Im looking even more at getting a Raspberry. Im waiting for Christmas and see if Santa brings one if Not Im going to order
shortly after.

If Bev doesnt fix it without me having to change this time Im erasing it.


#3

Hello, would you mind pointing me in the right direction on how to do this? my share code changed a couple of days ago and I have looked everywhere in my account settings to change it here but can’t find where.

Many thanks.


#4

Hello, would you mind pointing me in the right direction on how to do this? my share code changed a couple of days ago and I have looked everywhere in my account settings to change it here but can’t find where.

Many thanks.

You register the new code same way as you did your old one
flightaware.com/adsb/register


#5

When I try to register my new PP sharecode I get the following message (in red).

This unclaimed device is recognized, but your current IP address does not match. Please visit this page from the same computer or any other computer with the same external IP address as the device.

I guess my new PP sharecode is still used by another user. How can I fix that?
Thanks.


#6

Hi, my share code changed during the last Planeplotter outage and my new code has already been registered by a previous owner of that code so I am unable to share to Flightaware. Is there anything I can do to make it work again?


#7

This error is the result of some assumptions created by the designers of this system. Why do the admins assume IP addresses are directly associated with an end user? Those who have a load balanced connection with two pipes only have a 50% chance of the IP being the same as before. How about folks with dynamically assigned IPs? Point being, this is really bad practice and should be discontinued. It would resolve half of the issues reported on this forum. Continuing this practice solves…nothing that can’t otherwise be done.


#8

If you are unable to register because a code has already been used admin should be able to rectify that if you tell them your site number and the new share code feeding from it


#9

I agree it is imperfect. However, the odds of a user typo’ing their share code far or guessing every permutation of share code (there’s not many) and registering someone else’s device far, far, far exceeds the odds of someone being on a different IP from their local device.


#10

I’m now conflicting with some previous guy in GB, so my nearest Airport and Long/Lat are totally wrong :frowning:


#11

We updated dozens of codes based on data from COAA. This should be fixed now.


#12

I’m still showing as near EGTF when it should be near CYFC (the options to “Click here to change” also aren’t working). Thanks for working on this!


#13

What’s your old & new code?


#14

No old code, I’m a new sharer but apparently my code conflicts with a code that was recycled when the codes changed (since I see activity ended on Dec 19th before I started). Code is Ep.


#15

Oh i see! OK, I’ve reset it, give it an hour and let’s see what happens.


#16

Mine is still saying it is registered to another party. My new code is vf. Old code was gO, during the outage I was also gs for a short time and had updated my Flightaware code to that.


#17

vf is a duplicated code. You could try closing PP and restarting it and it will hopefully give you a unique code!


#18

No change - I’ve been vf for a week now, since the PP trouble was resolved. I guess I’ll have to hope there is a further update soon which will allow me to register it.


#19

Glad I deleted it and went Raspberry.


#20

Fixed