Netgate blocked my public IP on ACB
-
@stephenw10 Yes, it showed a high number of alerts saying “An error occurred while uploading the encrypted pfSense configuration to https://acb.netgate.com/save (Connection timed out)”.
I noticed it today because I wanted to upgrade the build and install some packages.I can confirm that I only manage one pfSense, with a fairly standard segmented LAN behind it.
Today I ran several analyses to see if there were any rogue devices on my network, but I didn't find anything, and in any case, I don't think that even if there were, it would hit the ACB repositories, but never knows...
I really don't know what to think.
-
It wasn't ACB it was hitting it was the repo data servers. As though it was running 'pfSense-repoc' continually, or multiple devices running it. Let me see....
-
I wonder if this post is relevant perhaps?
-
I believe is was actually a home assist plugin misbehaving.
-
@tinfoilmatt Thank you very much for the suggestion.
As Stephen said, the most likely hypothesis is that a Home Assistant integration caused the problem.
Unfortunately, I don't have any logs to confirm this hypothesis, but the integration was (afaik) the only thing besides me that had control over pfSense, so it's the main suspect. -
@tinfoilmatt said in Netgate blocked my public IP on ACB:
I wonder if this post is relevant perhaps?
This post shows : at 7 AM, 30 minutes, so ones a day, an "pkg update" is executed, a bit like option 13 on the console or visiting System > Package Manager inn the GUI, although the latter might work with a cache.
You could decide to do the update test every 5 minutes (or even less ?), and that means the Netgate update servers are hit 288 times per day by your pfSense.
Common sense would tell us this isn't a wise thing to do.No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
Yeah, it was a lot more than that. I don't think it would be possible to do it deliberately. It seems more likely a bug in the plugin at that time.
-
@Gertjan Don't get me wrong, it's a useful script. Was a pure shot in the dark.
-
@Gi82 Haven’t seen a case where Netgate blocks a residential static IP before — usually that kind of rate-limit only hits VPN endpoints or cloud IPs. The “too many queries” line sounds like an automated abuse trigger on their backend rather than something intentional. Still, refusing to unblock it and giving no real explanation isn’t a great look.
-
@SarahBrown13 Actually after a few days of discussions and examinations on TAC and here in the forum, my IP was unblocked.
The guys were great.
Only the technician who first responded to TAC cut short immediately, showing no desire to go into detail nor help me, which annoyed me quite a bit.
