4200 unable to connect to Netgate or user forum
-
Yep, I am seeing other posts about these issues. As of 2am PT the licensing and repo servers are still down. Hopefully it'll be fixed in the morning. Least now I know it's not my instance as I was trying to reinstall few packages in hopes to fix the php errors I was getting.
-
@Darkk it’s been down for more than a day. The forum was down for 2 days before it finally came back up. Not sure what’s going on. Their repo is going on 52 hours of being down.
-
@SamJWard said in 4200 unable to connect to Netgate or user forum:
@Darkk it’s been down for more than a day. The forum was down for 2 days before it finally came back up. Not sure what’s going on. Their repo is going on 52 hours of being down.
Repo down for 52 hours? That's strange as I was able to install pfblockerNG few hours ago. Now I am trying to reinstall and it can't due to repos being down.
-
@Darkk Yeah, something is till on going. Can't update a package (pfblcker ng). The processes just hangs and the system logs just says it is timing out on the very first step to backup on netgate servers:
Apr 30 17:53:31 php 83737 /usr/local/sbin/acbupload.php: New alert found: An error occurred while uploading the encrypted Netgate pfSense Plus configuration to https://acb.netgate.com/save (Connection timed out after 30094 milliseconds)
Apr 30 17:53:31 php 83737 /usr/local/sbin/acbupload.php: An error occurred while uploading the encrypted Netgate pfSense Plus configuration to https://acb.netgate.com/save (Connection timed out after 30094 milliseconds) - Connection timed out after 30094 milliseconds
Apr 30 17:52:39 php-fpm 11417 /pkg_mgr_install.php: Beginning configuration backup to https://acb.netgate.com/save
Apr 30 17:52:39 check_reload_status 53397 Syncing firewall
Apr 30 17:52:39 php-fpm 11417 /pkg_mgr_install.php: Configuration Change: [redacted]@x.x.x.x (Local Database): Creating restore point before package installation.I've rebooted the box, before the reboot, there was also a mention that it couldn't contact the repo (log not available anymore)
PS: It seems, it is now resolved at the time I was replying this. I've just started again the process and it is flowing now. fingers crossed
-
It seems the forum must still be having issues as well. I am not receiving notifications of new posts in this thread even though I am still listed as “Watching”.
-
@wgstarks I just got a notification like 10 min ago.. I do show that forums were down lately between
down 2024-04-29 19:46:19
up 2024-04-29 19:56:19
Duration
10 minutes and 0 secondsdown 2024-04-29 18:07:19
up 2024-04-29 19:25:31
Duration
1 hour and 18 minutesI would have to double check how often my monitoring checks, so those times could be a bit off.. Because its not checking like every 30 secords or anything crazy like that. Prob have it set to 5 or 10 minutes.
-
@johnpoz I went through my user settings and found that all email notifications had been disabled. I have corrected that now and hopefully the problem with notifications is fixed.
-
@johnpoz said in 4200 unable to connect to Netgate or user forum:
@wgstarks I just got a notification like 10 min ago.. I do show that forums were down lately between
down 2024-04-29 19:46:19
up 2024-04-29 19:56:19
Duration
10 minutes and 0 secondsdown 2024-04-29 18:07:19
up 2024-04-29 19:25:31
Duration
1 hour and 18 minutesI would have to double check how often my monitoring checks, so those times could be a bit off.. Because it’s not checking like every 30 secords or anything crazy like that. Prob have it set to 5 or 10 minutes.
I suspect that the problems I was seeing weren’t that the forums were off-line necessarily. I could connect most of the time via my Verizon cellular and very occasionally via my Spectrum cable internet provider. Really sounds like an internet backbone issue.
Regardless, it seems to be working now.
-
@wgstarks could of been internet sort of issue.. But my monitoring checks from multiple locations globally, so not like a specific isp or path problem.
-
The forum routing issue was not related to the pkg repo outage. It wasn't down for anything close to 52 hours. It was more like 6.
Anyway it's back up now and our monitoring has been changed appropriately.
Apologies for the inconvenience.
Steve