I updated the server to use forge and added mods that are compatible with the version. I got my local client working with the correct config but im unable to connect. I’m not sure if I missed a step.
thanks
Reproduction Steps
I updated the configuration of the server to use forge and uploaded some mods
I restarted and updated the server to make sure the changes were added.
I checked the logs to make sure nothing went wrong
My friend and I tried to connect using my forge client with the correct settings and we were unable to
Can’t help if you don’t provide the actual error you were getting on the client/ in the console.
Make sure you’re using the right modloader and version in the settings.
Apologies, its been a while since I last loaded MC and a ton of stuff I don’t remember.
I tried to connect directly to the server and I’m getting
Failed to connect to the server
Connection timed out: getsockopt
I tried to a bunch of things related to firewall settings. I allowed Java through the firewall and turned off the firewall but still no fix. My friend is also encountering the same issue.
I’ve been able to connect to other servers using the forge client and I can connect to my server using the official MC client.
I’m using the same version modloader on the client and server (forge 51.0.33), and I’ve used the same jar files for the mods on the server and my client.
I’m using hostinger for this. It works when trying to connect using the official MC launcher but I added the 25565 port UDP&TCP to the allowed firewall connections to make sure but still no resolution.
This isn’t Hostinger support, you’d have to double check the Linux firewall on your VPS to see if there’s a firewall rule being missed.
You can run ampinstmgr dumpfirewall to list the rules, and ampinstmgr updatefirewall to re-apply them.
If you don’t know how to get to the Linux command line, ask Hostinger’s support how.
I see, its odd that hostinger forwarded me to this site to ask for requests instead of having their support take a look.
I messaged them, so I’ll take a look at what the say the root cause could be. Their CLI is easy to access but the support agent looks to be restarting the server, so I’ll take a look afterwards.
I found a fix. I ended up using Fabric instead of Forge and that solved the issue. I’m still not sure of the root cause but I tried all the suggestions you had and anything I found online about this error. It very well could have been an issue with Hostinger and the packages they use for forge. If anyone runs into this issue without any solve, try using a different loader.