GEKKOI Posted August 13, 2017 Share Posted August 13, 2017 Soooo after server restart i am always getting "timed out" error idk why video ------> Link to comment Share on other sites More sharing options...
JoeDirtDigger Posted August 13, 2017 Share Posted August 13, 2017 been having the same issue for the last 2 hours wife isnt able to connect either Link to comment Share on other sites More sharing options...
Terminator Posted August 13, 2017 Share Posted August 13, 2017 Hello, i tried connecting too, looks like the server is down we will have to wait untill its fixed, by time, or bruny. Link to comment Share on other sites More sharing options...
Techno1001101 Posted August 13, 2017 Share Posted August 13, 2017 Im also always timing out Link to comment Share on other sites More sharing options...
JoeDirtDigger Posted August 13, 2017 Share Posted August 13, 2017 pushing 14 hours and still getting time out errors any update on whats going on? if anything? since gekkoi already posted pings here's a trace route to go with it. don't mind that second line its my firewall saying i don't respond to that crap. I know it doesn't help since it shows all is well but I added it anyway :\Users\Joe>tracert skyfactory.craftersland.net Tracing route to skyfactory.craftersland.net [62.138.5.61] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms testwifi.here [192.168.86.1] 2 * * * Request timed out. 3 8 ms 18 ms 8 ms 173-219-226-117.suddenlink.net [173.219.226.117] 4 20 ms 19 ms 19 ms 173-219-249-248.suddenlink.net [173.219.249.248] 5 33 ms 34 ms 33 ms 173-219-152-193.suddenlink.net [173.219.152.193] 6 34 ms 34 ms 34 ms be4714.ccr41.dfw03.atlas.cogentco.com [38.140.104.225] 7 18 ms 18 ms 18 ms be2763.ccr31.dfw01.atlas.cogentco.com [154.54.28.73] 8 29 ms 30 ms 29 ms be2432.ccr21.mci01.atlas.cogentco.com [154.54.3.134] 9 42 ms 41 ms 41 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166] 10 58 ms 58 ms 57 ms be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222] 11 61 ms 61 ms 62 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130] 12 70 ms 69 ms 69 ms be2299.ccr31.bos01.atlas.cogentco.com [154.54.43.9] 13 129 ms 128 ms 129 ms be2982.ccr41.lon13.atlas.cogentco.com [154.54.1.118] 14 163 ms 568 ms 163 ms be12497.ccr41.par01.atlas.cogentco.com [154.54.56.130] 15 150 ms 150 ms 150 ms be2246.rcr21.sxb01.atlas.cogentco.com [130.117.50.33] 16 163 ms 163 ms 164 ms be2780.nr13.b015623-2.sxb01.atlas.cogentco.com [154.25.5.242] 17 170 ms 169 ms 168 ms 149.14.12.58 18 157 ms 157 ms 156 ms ae2.sxb1-rr-1-2-f1-3.sxb1.legacy [87.230.114.162] 19 151 ms 165 ms 150 ms 217.118.16.46 20 149 ms 148 ms 148 ms static-ip-62-138-5-61.inaddr.ip-pool.com [62.138.5.61] Link to comment Share on other sites More sharing options...
GEKKOI Posted August 13, 2017 Author Share Posted August 13, 2017 fixed for me //close the thread Link to comment Share on other sites More sharing options...
Founder brunyman Posted August 14, 2017 Founder Share Posted August 14, 2017 Looks like there was an internal crash of forge, the server was still running but was timing out all connections. I have updated the monitoring plugin to auto restart sooner if this issue get's detected. Link to comment Share on other sites More sharing options...
Terminator Posted August 14, 2017 Share Posted August 14, 2017 Server is up and running.Topic Closed! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.