[SOLVED] Server works flawlessly with Vanila but can't connect with Forge 1.12.2

Posted December 22, 20195 yr

Following issue:
I'm hosting an 1.12.2 mc server via (debian) Linux VPS <-- IPv6 only.

When I'm starting the Server with the offical 1.12.2, I can connect to the server via Windows Client flawlessly, vanila, no issue.
But as soon as I start the server with Forge (1.12.2-14.23.5.2768), my windows client notes "Can't connect to server" and the error is: "io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no further information:"

What's happening? Both addresses are IPv6, it can't be the firewall because vanila worked and I even allowed port 25565 (with ufw) still, nothing changed.

Edited December 25, 20195 yr by Reloading

December 22, 20195 yr

Author

13 minutes ago, diesieben07 said:

Try launching the server with -Djava.net.preferIPV4Stack=false.

I tried the following command on both the server, still ~~doesnt work~~ nothing changed:

java -Xms1G -Xmx2700M -Djava.net.preferIPV4Stack=false -jar forge-1.12.2-14.23.5.2768-universal.jar nogui

Edited December 22, 20195 yr by Reloading

December 22, 20195 yr

Author

Isn't it weird that when I start the server via Vanila, it works flawlessly but the forge one fails with a connection refused error? It's not like the forge.jar is changing the VPSs Firewall or whatever.

December 23, 20195 yr

That's such a generic exception though, can you provide debug.logs from both server and client?

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.

[Workaround line, please ignore]

1

December 23, 20195 yr

Author

@DaemonUmbra @diesieben07

I appended the logs for both client and server in the attachment area.

Here's another interesting thing, I re-installed forge and noticed something weird being printed on my terminal when I ran the installer --installServer command:

java.net.preferIPv4Stack=true
Installing server to current directory

So I deleted everything (except the vanila 1.12.2 jar file since it needed by forge) and reinstalled the installer.jar with Djava.net.preferIPV4Stack=false option but I still get that output printed on the terminal... Maybe that's the issue?

Anyway see the debug.logs I appended, I replaced certain parts such as the IPv6 for example with <VPS IPv6> or other stuff that I deem possibly private info, this should not affect the overall validity of the logs.

In the client log there's an interesting Java Exception at the bottom about the connection refusal.

CLIENTdebug.log SERVERdebug.log

Edited December 23, 20195 yr by Reloading

December 25, 20195 yr

Author

I've discovered the solution to this wide-spread issue that has been plaguing many people's servers.

Due to the recent hostility I've received from (supposedly) the mods/admins I've decided NOT to post the solution here, if you're in need of the solution PM me or google on different forums, you'll see it, I hope future visitors can get a picture of how they'll be treated here.

PS: Giving people warnings and post-moderation bans is not going to achieve ANYTHING, we're not in a kindergarten.

Edited December 25, 20195 yr by Reloading

December 25, 20195 yr

You were reprimanded after posting in other people's threads and DMing mods to draw attention to your own thread, something that is selfish and not allowed.

You are right, this is not kindergarten, not everything is about you.

3 hours ago, Reloading said:

I've discovered the solution to this wide-spread issue that has been plaguing many people's servers.

Due to the recent hostility I've received from (supposedly) the mods/admins I've decided NOT to post the solution here, if you're in need of the solution PM me or google on different forums, you'll see it, I hope future visitors can get a picture of how they'll be treated here.

"I could be helpful, but I won't because I don't like the staff"

Real nice...

3 hours ago, Reloading said:

PS: Giving people warnings and post-moderation bans is not going to achieve ANYTHING, we're not in a kindergarten.

This one I don't quite understand, these are the two meanings I can think of...

"Punishing me doesn't help solve my problem"

It's not supposed to, it's supposed to teach you to be a better forum user

-or-

"Punishing me won't teach me anything, I refuse to learn"

This is a flaw in your character if you refuse to learn or accept that you did wrong

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.

[Workaround line, please ignore]

Sign In

[SOLVED] Server works flawlessly with Vanila but can't connect with Forge 1.12.2

Featured Replies

Posts

[1.20.1] Custom Effect Help

1.20.1 Client crashing when joining the ender portal

1.20.1 Client crashing when joining the ender portal

1.20.1 Client crashing when joining the ender portal

Exit Code 1

Who's Online (See full list)

Important Information

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)