Please read the rules and FAQ before starting a new topic

Internal Exception: java.io.IOException: An existing connection was forcibly closed by the remote host

Start new topic

Posted February 29, 20205 yr

I have been getting issues with everyone who tried to connect the server getting that message above our a "Connection Lost Disconnected" message. What is weird is that this only happens the first time you attempt to log into the server after the clients first starts up. Any attempted login connection you have to the server after that point seems to be fine and you can play the game as normal and you can continue to reconnect so long you keep your client up. Why this only happens the first connection, every time the client has been freshly loaded is strange. There is no crash log, the client does not crash, but it does kick you from the server on the first connection. Occasionally from my client i am able to be physically in the game for a matter of seconds and move around briefly and then I get kicked and the message pops up again.

We have been using my own version of a modpack on twitch as well as individuals having made their own builds using the same mods. This pack is a Direwolf20 2.5.0 pack with the Bloodmoon mod added. Everyone gets this connection issue on first connection

We have tried:

- Restarting the server.

- Restarting the clients.

- Updating the mods it suggested to update.

- Disable journey map on both server and client.

- Disable astral sorcery on both server and client.

- Edit server properties such as turning down the view distance.

EDIT:

- We also tried updating the forge versions for the server and client - this made no difference

I should add the forge versions are:

Client: 14.23.5.2821

Server: 14.23.5.2847

Link to the server and client logs:

https://drive.google.com/drive/folders/1HqxJPipdE5UTfpP8_pH6KmuLhDyHXoxj?usp=sharing

So far everything we have done to try and methodically sort this has not worked.

Edited February 29, 20205 yr by redninja685

February 29, 20205 yr

1.12 is no longer supported on this forum.

Please update to a modern version of Minecraft to receive support.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler

Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
Make a launcher profile targeting this version of Forge.
Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

or alternately,

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

Open a command prompt (CMD, Powershell, Terminal, etc).
Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
Run the following commands:
1. git init
2. git remote add origin [Your Repository's URL]
  - In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
3. git fetch
4. git checkout --track origin/master
5. git stage *
6. git commit -m "[Your commit message]"
7. git push
Navigate to GitHub and you should now see most of the files.
- note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
Now you can share your GitHub link with those who you are asking for help.