"Connection forcedly closed", weird temporary solution but annoying

  • Thread starter Thread starter HululusLabs
  • Start date Start date
  • 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
H

HululusLabs

Guest
Title "Connection forcedly closed", weird temporary solution but annoying

Launcher Type Server

Modpack FTB Revelation

Modpack version 1

Have you modified the pack? No

Link to log file http://paste.feed-the-beast.com/view/fda03449

Details of the issue Me and a friend set up a server for FTB Revelation. Sometimes when we connect we get an error saying the connection was forcibly closed by remote host, and no amount of restarts of the server or clients or router would work. The server only gives the "player disconnected" feedback, I will still post the logs as soon as I get in contact with my friend.

We have discovered a temporary solution, which is to close the actual server, launch an old backup copy of the server (a separate server folder, below referred to as the jank server), and connect to it, then disconnect and close the jank server, and launch the actual server. This always fixes the issue for some reason. We have resolved to do this every time because the issue comes up a lot, but it's slow and time-consuming having to launch the server three times, and also the weirdest solution ever. Why would launching then closing a completely isolated copy of the server fix the problem; does it refresh some kind of cache I don't know about?

On a side note, a day before Revelation was released, we were trying to setup an Infinity Evolved server on my computer. It was laggy but my friend could connect. Then Revelation released and we found it was wonderfully not laggy in singleplayer, but we couldn't get my friend to connect to my Revelation server. We had to switch to running it on his computer. For this issue I'm just wondering why an Infinity server worked but Revelation server didn't.

Thank you for your time and support!
 
Last edited by a moderator:
There have been reports of this issue - it might be a issue with the forge version (this isn't confirmed - last I heard).

Might have to wait for next version of the pack.

Another suggestion to try: log in to a single player world and out again (perhaps restart the client after that), and try again. See if that has the same effect as setting up a copy of the server.
 
  • Like
Reactions: HululusLabs
grandrolf said:
There have been reports of this issue - it might be a issue with the forge version (this isn't confirmed - last I heard).

Might have to wait for next version of the pack.

Another suggestion to try: log in to a single player world and out again (perhaps restart the client after that), and try again. See if that has the same effect as setting up a copy of the server.
Click to expand...

Thank you for the tip. I've already transitioned to ripping my hair out at setting up a server on AWS, so can't confirm for now. If the same problem comes up on AWS I will try this out.

I forgot to mention there are various different connection issues as well, such as the "closed by remote host", "fatal error, connection terminated" etc. (The latter just showed up on the AWS server).

Edit: Me and a friend both tried connecting to a singleplayer world and rebooting client, but it's still giving errors.
 
Last edited:
Could this be an issue with the world file (the jank solution worked again)? Also, would I be able to install a different version of forge?
Thanks again!
 
Last edited:
HululusLabs said:
Could this be an issue with the world file (the jank solution worked again)?
Click to expand...
Not sure, sorry.

HululusLabs said:
Also, would I be able to install a different version of forge?
Click to expand...

Yes ofc you could do that, but then it's hard to get support on the pack, you need to find a version of forge that works with all the mods in the pack + you need to update both on the server and the clients that are going to connect.

I wouldn't do it, I would wait for a fix.
 
Okay. We're only three people so it may be worth it, but we don't want to break everything else while trying.
 
NICE I will try it out ASAP

Will the server beta work with the normal client or will everyone have to update?
 
Both server and clients need to be on the same version.
 
Update: since the official 1.1.0 came out we tried it but it still is broken. Will give feedback again once 1.2.0 is out

Update: 1.2.0, the problem still exists
 
Last edited:
I'm giving this thread a nice bumperoo. Exact problem as des.cribed in the above description on version 1.3.0

There is some sort of timeout issue that logs an user out after 'what appears to 12 seconds' unless some unknown state of completeness is finished, such as the world chunks all loaded in completely for the user.

Today or tomorrow I will be testing a few things:
-Singleplayer launch/disconnect trick suggested by grandrolf
May work only if the server has been relaunched
-reducing server and client chunks loaded to a minimum.
Inconclusive with about 10 tries each.
-use glasswire to document the connection quality of successful/unsuccessful connection attempts.
Data usage is generally the same in both instances, again I will mention it seems to transmit for around 12 seconds before flat-lining.

A full reset of the client and the server, then logging the client into the server with little-to-nothing done previously is the only highly-successful thing that works, with about a 50/50 chance ofc. t is very likely then that the bug is both inside of the client and the server in the forge/minecraft handshake.

Respawning after a death also leads to a potential disconnect. Also another 50/50 chance.
 
Last edited:
uh20 said:
I'm giving this thread a nice bumperoo. Exact problem as des.cribed in the above description on version 1.3.0

There is some sort of timeout issue that logs an user out after 'what appears to 12 seconds' unless some unknown state of completeness is finished, such as the world chunks all loaded in completely for the user.

Today or tomorrow I will be testing a few things:
-Singleplayer launch/disconnect trick suggested by grandrolf
May work only if the server has been relaunched
-reducing server and client chunks loaded to a minimum.
Inconclusive with about 10 tries each.
-use glasswire to document the connection quality of successful/unsuccessful connection attempts.
Data usage is generally the same in both instances, again I will mention it seems to transmit for around 12 seconds before flat-lining.

A full reset of the client and the server, then logging the client into the server with little-to-nothing done previously is the only highly-successful thing that works, with about a 50/50 chance ofc. t is very likely then that the bug is both inside of the client and the server in the forge/minecraft handshake.

Respawning after a death also leads to a potential disconnect. Also another 50/50 chance.
Click to expand...

So what has been working for me and my two friends basically 100% of the time (when trying to get onto our own server) is to log in to one of the public servers, then log off. Or, since this causes unnecessary strain on the public servers, launch a server instance on your local computer and connect to that. No need to setup anything, just download the server file and run it, then connect to it through localhost. Then disconnect and connect to the server you want.

I do this routinely without even trying to log into our server, I simply log into a different server first, then switch over.
 
You must log in or register to reply here.
Top Bottom