Problem FTB U - Server Issues

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Alec Bush

New Member
Jul 29, 2019
4
0
0
We were bumbling arround in the twilight forest, came home and dumped some Twilight items in out sorting chest (Uses Ender Chests, Pipes and tubes / filters) and then neither of us could open any chests and then we both crashed with an error: Internal Exception: Java.net.socketTimeoutException: Read timed out thrown on our screens.
Pastebin to the FTB launcher log: http://pastebin.com/zDLRwdJV
EDIT: Tried to connect again and got an error on the server log: http://i.imgur.com/bRqJM8C.png
BUT nothing shows up in the server logs. No crash report, nothing on the console, nothing!
Now whenever we try to relog it gives us the same error after a few minutes.
I've tried disabling some addons but none work, I've tried removing player profiles and everything but nothing seems to work. I can say though that replacing the world folder DOES work, but is not a fix for us since we spent so much time in the world.
Anyone have any ideas!? My friend seems to think it has something to do with twilight forest items and filters, but I removed Twilight Forest and the same thing happens.
We are not running any mods other than what FTB Ultimate has in it, and we have gregtech disabled.
If need be I can upload the server / World folders.
Thanks!
 

Dingham

New Member
Jul 29, 2019
294
0
0
Based what your friends have said, I had a similar issue when i uninstalled Xycraft from my server. Some of my players where voiding their materiel, to be hopefully though i said it was unnecessary. I ran into issues initially when I started the server with the new update, turn out, i think, it was the materials in the filters and managers. My resolve was to up the map in the old version(with Xycraft) and go to the locations and punch out said machines.

I don't know how this specifically can help you as its a different cause, and I can't do much without logs/reports.

Additions...

2013-03-26 23:10:15 [INFO] [STDERR] at org.bouncycastle.crypto.io.CipherInputStream.nextChunk(Unknown Source)
2013-03-26 23:10:15 [INFO] [STDERR] at org.bouncycastle.crypto.io.CipherInputStream.read(Unknown Source)
I just noticed this at the end of your report. I see this bouncycastle.crypto line a lot when people have bad connections and get booted, I joke with them and telling the to stop bouncing on bouncy castles . I think its to do with latency between the client and the server. The server info always rules, so, educated guess, if the difference between the to is too inaccurate, the server boots the client. This only happens with players with poor internet connections, the player it happens mostly to admits is connection is shit, and then recently had a member try to join from NewZealand who said his PC wasn't great spec.
 

Alec Bush

New Member
Jul 29, 2019
4
0
0
Thanks for the reply!

Unfortunately, I can almost be sure to rule out shoddy internet connections.
1. The server is hosted on my computer that I am booting MC on to connect, using 127.0.0.1
2. It works fine when I create a new world.
3. We have never had this issue before, with years of playing MC.
4. http://www.speedtest.net/result/2603928590.png

I've tried disabling and re enabling some addons, and nothing has updated recently.

EDIT: Tried to connect again and got an error on the server log: http://i.imgur.com/bRqJM8C.png

I wish I did keep backups =/
 

CrazylikE

New Member
Jul 29, 2019
55
0
0
Got the same problem on my server hosted by Creeperhost. This issue is going back several years and I have yet to find a fix for it :/
 

Luke_H

New Member
Jul 29, 2019
273
0
0
Your Twilight forest versions are slightly wrong, change both server and client to the latest 1.4.7 reision of Twilight forest.
 

Alec Bush

New Member
Jul 29, 2019
4
0
0
Your Twilight forest versions are slightly wrong, change both server and client to the latest 1.4.7 reision of Twilight forest.

Nope, same error and everything. Also removing that mod does nohing.

Thanks for the idea though!