Your Hotspot was possibly blacklisted.

[ghost]

"Your Hotspot was possibly blacklisted."
What should i do ?

[FezzFest]

Unfortunately, there's not much you can do. This blacklist was implemented without community approval or oversight and its existence denied until it was impossible to deny it any longer. If the helium developers stick to their promises, a new firmware will be released soon on https://quay.io/repository/team-helium/miner that does not contain a blacklist anymore.

That does not mean the blacklist has been abolished however. If the result of the "Maintain Temporary Hotspot Denylist" vote on heliumvote.com turns out in favor of a blacklist (and it looks like it will), I expect a new blacklist will be implemented again in the future.

[serbyxp]

@FezzFest my hotspot isn't on that list. But my hotspot is having all sorts of dial errors this is just a log from the 1/12/2022.1 update attached I'm no programmer or nothing basic skills and troubleshooting whats going on with my hotspot. If you have the framework or database already running, maybe you have a way to extract this log file and have it do some sort of matching script against the failed to dial /p2p/ adders against that database. Not a request or anything but maybe it'll clarify whats happening with hotspots that aren't on that list. getting failed to dial errors,

I have a feeling that if there is someone that say has 10000 hotspots like a manufacturer or a "group" of people running an alternate firmware, or has some sort of settings disabled or altered, that may be blocking inbound messages.

** Maybe its not manufacture specific, but maybe its an ISP issue. I personally disabled a feature on my comcast xfinity called " advanced security, which would trigger on " irreputable IP" which would need to be cleared on my router app to take the hotspot out of relay mode*

I dunno I'm not into conspiracy theories or anything but we need some sort of clear picture of whats going on, Say manufacture X has a setting on all their miners that's different then manufacture Y, that isn't letting them communicate whether intentional or just a container setting like the network group being " Attached" or not .. I dunno here it is. do what you wish with it.

I only have this on this computer, but the rest are in the helium github issue thats pinned

error_log_1.13.22_fw_1.12.2022.1.txt
errorlog.txt