anyone just have issues getting to forum?
-
it was odd.. I was getting this from 3rd hop in my trace
3 216.80.79.9 reports: Destination net unreachable.
When doing a traceroute to the forum IP of 208.123.73.83 That is router in my isp network.. Traceroute now still goes through same hop.
So not sure if something wrong in my isp, wasn't having any issues getting to anything else.
But now a few minutes later all is back..
-
@johnpoz Same here
-
And here.
@johnpoz said in anyone just have issues getting to forum?:
So not sure if something wrong in my isp
-
@mcury ok - so that kind of rules out ISP issue, I doubt we are on the same isp ;)
-
@johnpoz said in anyone just have issues getting to forum?:
I doubt we are on the same isp ;)
Indeed :)
-
@mcury I even tried routing traffic through vpn, and still was down.. So seems something happened with their routing.. Hmm - curious, but its back so no big deal.. But odd, I don't recall ever seeing that sort of error in traceroute before - it sure not a common error.
-
@johnpoz said in anyone just have issues getting to forum?:
I even tried routing traffic through vpn, and still was down.. So seems something happened with their routing.. Hmm - curious, but its back so no big deal.. But odd, I don't recall ever seeing that sort of error in traceroute before - it sure not a common error.
I have observed these outages during the last month or so, it usually comes back after 5-10 minutes.
But I didn't try to diagnose the issue, I just thought, oh well, forum is down.. -
@mcury Well I know they were moving the forum, there was a maint announcement a few weeks back.
if goes down again, see if can glean some more info. I didn't get a chance to do a trace from one of my vpses before it was back.
-
@johnpoz Forum and ACB was done for me
netgate.com - probably hosted somewhere else - was still working. -
@johnpoz said in anyone just have issues getting to forum?:
Well I know they were moving the forum, there was a maint announcement a few weeks back.
if goes down again, see if can glean some more info. I didn't get a chance to do a trace from one of my vpses before it was back.
Next time it happens and I'm luck enough to be online, I'll trace it too and then PM you if that is ok for you
-
@mcury sure... I just saved off some current traces, from my local box, and from one of my vps boxes. So if catch it down see if showing same sort of error (no route) from different parts of the country.
-
I was having issues with it earlier today. Just spinning waiting to populate the unread threads.
Phizix
-
For the last few days I will intermittently get either an entirely blank page body (just the header at the top shows), or I will get a web server error from nginx. This most often happens as I browse posts and then hit the "back" button to return to the list of posts.
I can refresh the browser page and usually things come back, but then it will repeat at a random interval.
I have also received a couple of pop-up messages in the lower right corner of my browser saying "connection to the forum appears to have been lost -- trying to reconnect" (or something very similarly worded as I don't recall the exact phrasing).
-
Same here...(german telekom ISP),
Last night Firefox would not load anything related to this forum, chromium worked.
Sometimes firefox showed everything correctly, sometimes wrong layout, sometimes nothing (server/site might be offline or too busy)... -
@johnpoz said in anyone just have issues getting to forum?:
Destination net unreachable.
Yesterday, in the afternoon (GMT+2, Paris Time) : I thought the Forum search button was 'broken'. Worked well minutes afterwards.
I knew it was 'the forum' or the route to the forum, not the ISP.Right now, 07h23 over here, all looks normal.
-
@johnpoz said in anyone just have issues getting to forum?:
it was odd.. I was getting this from 3rd hop in my trace
3 216.80.79.9 reports: Destination net unreachable.
When I did tracert yesterday, while the outage was going on, it didn't stop but after the third (not sure) hop, everything had a time out.
PS C:\Users\Bobby> tracert forum.netgate.com Tracing route to forum.netgate.com [208.123.73.83] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms pfSense.home.arpa 2 <1 ms <1 ms <1 ms fritz.box 3 6 ms 5 ms 4 ms i5E86C752.versanet.de [94.134.199.82] 4 4 ms 4 ms 3 ms 62.214.32.83 5 4 ms 4 ms 4 ms VERSATEL-DE.edge5.Berlin1.Level3.net [212.162.40.38] 6 5 ms 5 ms 5 ms 212.162.40.37 7 * * * Request timed out. 8 131 ms 131 ms 131 ms ZAYO-BANDWI.ear5.Dallas1.Level3.net [4.14.49.2] 9 133 ms 130 ms 130 ms ae0.aus01-mls-dc-core-b.infr.zcolo.com [64.20.229.166] 10 132 ms 132 ms 132 ms net66-219-34-198.static-customer.corenap.com [66.219.34.198] 11 131 ms 131 ms 131 ms fw1-zcolo.netgate.com [208.123.73.4] 12 131 ms 131 ms 131 ms forum.netgate.com [208.123.73.83]
-
There was an upstream outage at the datacenter where the forum (and other things) are hosted. Should all be good now.
-
@stephenw10 thanks for quieting the curiosity kats ;)
it was short lived which is really good.. I take in the routes for the network that is on were not being advertised which caused the error I saw in my trace.. I honestly do not recall ever seeing such a response in a trace before... So was curious to the nature of the outage.
-
Yes there were routing/BGP issues. Took a while to converge after connectivity was restored. #funtimes
-
Network issues can be strange sometimes. It could have been a temporary problem with your ISP or a glitch in their routing. If it's working fine now, it might have been a short-lived hiccup.