Hotspots going relayed into after 2021-09-03~ update multiple users

[MMOStars]

Hello, there are at least 10-15 people on Sensecap discord reporting same issue that after 2021-09-03~ update

100% this change broke something for us: f31e45f

This is what we get via peerbook:

| address | name |listen_add|connectio| nat |last_updat|
+----------------------------------------------+-----------+----------+---------+-------+----------+
|/p2p/113gAgf8DTFi4YQFrQYMRhN7WUj25rTwS2mkTM5uj|odd-clay-wo| 2 | 5 |symmetr|15306.244s|
+----------------------------------------------+-----------+----------+---------+-------+----------+

+--------------------------------------------------------------------------------------------------+
| listen_addrs (prioritized) |
+--------------------------------------------------------------------------------------------------+
| /ip4/xxxxxxxxxxxxxx/tcp/44158 |
|/p2p/11KgYQR9h3Rz9cmzVZLwtZiHxThMs731uFTraLiyPmfHcxp7DYx/p2p-circuit/p2p/113gAgf8DTFi4YQFrQYMRhN7W|
+--------------------------------------------------------------------------------------------------+

+---------------------------------------------------------+
| connections |
+---------------------------------------------------------+
|/p2p/11KgYQR9h3Rz9cmzVZLwtZiHxThMs731uFTraLiyPmfHcxp7DYx |
|/p2p/1128k7YK3UfSh5qaAp37qe2jw3LaG6ycQUAAqD33L9v9DoRHdrkK|
|/p2p/112BwJXdn117Y9pNcte1VKpZWFViakbi9tuUMrDsmpnZsM6DEfPb|
|/p2p/11GxM19uKgCpoArMGBUDGeNLxRYM8L9ferCCd8sHkgFdZtVU86P |
|/p2p/11XG5Dw6L1jmu9XE61b1LJ6TdgWm7An1a1Nut34XwMbUyiUWoQV |
+---------------------------------------------------------+

Sensecap dashboard reporting this:

Listen IP(Based on Helium API):
/ip4/xxxxxxxx/tcp/44158,/p2p/1121Gc63SGenk9emVaEe3TsQejLgQHp193ptawGmtp7q34M4X9yQ/p2p-circuit/p2p/113gAgf8DTFi4YQFrQYMRhN7WUj25rTwS2mkTM5ujXP68mCGNw8
NAT Type: Symmetric
Relayed: Yes

Port 44158 has been confirmed to be open as per https://www.yougetsignal.com/tools/open-ports/

The hotspot WAS NOT relayed until last update!
The NAT type on Router is COG (In other words I presume CONE), NOT SYMMETRIC! And this change somehow changes our nat type to symmetric, but it's not symmetric!
https://explorer.helium.com/hotspots/113gAgf8DTFi4YQFrQYMRhN7WUj25rTwS2mkTM5ujXP68mCGNw8/activity
HELIUM EXPLORER DOES NOT REPORT THAT HOTSPOT IS RELAYED!

After we reboot the hotspot, the relay is reporting is NONE and Relayed status is: No.
After 2-4 hours, poof, we become relayed and start listing on both IP + P2P, which should not happen.
I own 3 hotspots, 1 hotspot on same ISP, does not have this type of issue, which is super odd, but this can't because of our router settings as technically we are not choosing to somehow assign 2 listening IPs to API, which should not be happening.

Please help solve this issue ASAP!

[ranezinjo]

I am having THE SAME issue!

[sullyjman]

Been seeing a lot of reports of this in the helium discord

[Vagabond]

This won't actually harm you, although it is an issue. This is likely fallout from the IP changing issue fixes over at #374 . I know the app might scream at you but if you have a valid external IP as the first row in the listen addrs you're fine, they're tried in the order they appear.

I will take a look as to how this is happening again. If you have an affected hotspot you can email me the name/serial number/manufacturer and I can try to work with the manufacturer to pull logs.

[MMOStars]

This won't actually harm you, although it is an issue. This is likely fallout from the IP changing issue fixes over at #374 . I know the app might scream at you but if you have a valid external IP as the first row in the listen addrs you're fine, they're tried in the order they appear.

I will take a look as to how this is happening again. If you have an affected hotspot you can email me the name/serial number/manufacturer and I can try to work with the manufacturer to pull logs.

Good day, my person is odd-clay-worm (https://explorer.helium.com/hotspots/113gAgf8DTFi4YQFrQYMRhN7WUj25rTwS2mkTM5ujXP68mCGNw8)

If you need logs, Jerry (dev) from Sensecap would be willing to work on this 1 with you.

I would like to encourage other posters to share their addresses for this issue to be fixed ASAP.

[Vanlushai]

I have the same issue. . .please let me know how to fix it

[trillion95]

I have the same issue 🙃

[arnoudius]

I have the same issue. Rebooting the device does indeed temporarily fix the issue, but then a few hours later the issue occurs again. I have had this since the 2021-09-03 firmware update. Before that, it was working fine / not switching to relayed after a few hours.

[ArnoutVerbeken]

So MMOstars was able to compile a list of all hotspots affected by this issue. He could not access Github and asked me to post this json file here. See attached.
Maybe it can help you troubleshooting or prioritizing this issue.
As an overview, here are the total numbers:
"{"helium": 1, "calchip": 922, "nebra": 137, "syncro": 21, "bobcat": 1800, "LongAP": 38, "mimic": 0, "rak": 4, "kerlink": 0, "dewi": 0, "sensecap": 281, "unknown": 0}"
Which boils down to the following numbers in percentage (of the total fleet of that brand):
Bobcat ~3%
calchip ~1.6%
Sensecap ~2.4%
Nebra ~2.1%
LongAP ~7.6%
bugged_miners.zip

[arnoudius]

It also seems to happen more frequently now. I just rebooted the miner an hour ago (sensecap m1), and now (+/- one hour later) it's already saying it's relayed again. It seems the service can still be reached though. If I for example use canyouseeme.org, it does report the port is open / can see the service, but on the Sensecap dashboard it reports it as being relayed / p2p status unhealthy. I also don't receive any rewards while it's reporting that it is being relayed. As soon as I restart the device, I start receiving rewards again, until it gets relayed again (after a few hours).

[thatsaint]

This same issue is happening to 2 of my Bobcats

[trillion95]

They need to fix this ASAP!!! I shouldn’t have to restart my hs every time!!!!!

[Vagabond]

If you read my earlier response, you will know that this bug is not actually going to harm you. I will work on fixing it but the relay status is not going to cause you any problems itself.

[kzkz0]

This is happening to my SenseCap M1 Hot Spot after I switched it from WiFi to ethernet cable. The dashboard says it's not relayed but the Helium app says it is and I have a really long string of numbers and characters for my Listen IP.

I have confirmed port 44158 is open and I have created challenges and a few beacons but haven't seen any witnesses since this has happened. If you need more details please let me know.

[GoviCoin]

having same issue , i switched from WiFI to Ethernet, still says relayed...checked API. says p2p
https://explorer.helium.com/hotspots/11MwQFbLUPso73YZQY2mjdbiCBVNjTkCVX2yB8asTFtcBsk7Knk
any help?