[SOLVED] Client times out on joining own server

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • 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

TristanBomb

New Member
Jul 29, 2019
4
0
0
Title:
Client times out on joining own server
Launcher Version:
1.4.11
Modpack:
FTB Infinity: Evolved
Modpack Version:
2.3.5
Log Link:
Details of the issue:
Server log: http://hastebin.com/uxebawurod
Client log (sorry for no text wrap!): http://hastebin.com/getivefatu
Server FML log: https://www.dropbox.com/s/q7oajxr2rcgumdj/fml-server-latest.log?dl=0
Client FML log: https://www.dropbox.com/s/4mo5w9bc3cf8n52/fml-client-latest.log?dl=0

Running Debian 8 (Jesse) w/ GNOME, 64-bit system, Java 7u91

I've been trying to set up a FTB Infinity Evolved server to play with some friends, but unfortunately I have been unable to join the server (connecting via localhost) at all. Both the server and client stay up after connection attempts (so it's not actually a crash), but the client times out. Note that the client does see the server in the multiplayer menu, with full green bars and all. Also, FTB is playable in singleplayer with no issues. I'm not sure if this is an issue on the client or server side.

I have tried force-updating the client and reinstalling the server, neither have helped. I haven't gotten anyone else to try a connection yet, though I suspect that the addition of the Internet wouldn't really help. Both the client and server have ample memory (4GB and 8GB, respectively, on a 16GB system) and I'm running a pretty beefy system in general.

At this point I'm really not sure what else to try, other than running a Windows version via WINE.
 

Moasseman

New Member
Jul 29, 2019
1,679
-2
1
Urrfff I don't like dese kinda things, even tho it's technically right up my alley

Tryyy connecting with your local ip (192.... or 172... or 10....) and not localhost/127.0.0.1? Maybeee...
 

TristanBomb

New Member
Jul 29, 2019
4
0
0
Urrfff I don't like dese kinda things, even tho it's technically right up my alley

Tryyy connecting with your local ip (192.... or 172... or 10....) and not localhost/127.0.0.1? Maybeee...
Just tried this, as well as connecting through my external IP address (having port forwarded). In both cases, Minecraft detects the server but still cannot join it.

The connection itself doesn't seem to be the issue, rather something might be wrong with the packets? Might have to do with line Attempting connection with missing mods [] at CLIENT or something related to RF Tools. I saw another post somewhere - a rather old one - saying RF Tools was conflicting with Thermal Expansion. I'll disable it on both client and server and report back.

EDIT: Well, I can't really do anything with RF Tools enabled. The client still can't join but says "Fatally missing blocks/items," despite the mod being disabled on both server and client and a new world generated. Singleplayer still works. Even a complete reinstall of FTB Infinity on the client side didn't help; I re-enabled RF Tools as well.

EDIT 2: Got a friend to try, he's getting the same problem.

EDIT 3: Solved by simply nuking everything related to the server from my computer and reinstalling. I have no clue why that didn't work the first time!
 
Last edited: