Jump to content

Self hosted Server: Connection refused


Go to solution Solved by Belankar,

Recommended Posts

Posted (edited)

Hello,

I have set up a server. The server itself works fine, I can connect via localhost but neither me nor anyone else can connect using my IP address. 
The things i checked:
I'm whitelisted. 
The port forwarding is set up in my firewall. Opening it fully doesn't change anything.
My router is also configured to allow the connection.
The Server does not show up in the global list, even though I've set "/serverconfig advertise on", which makes me think that it cant communicate outwards at all.

Currently it's a long loading time and the Message: Unable to connect to server. Connection refused.
I'm running the Server on Linux Mint.

Thanks in advance

Screenshot from 2026-04-03 15-34-12.png

Edited by Belankar
  • Belankar changed the title to Self hosted Server: Connection refused
Posted

Not a Linux expert, but if you have a firewall running at all try disabling it; if that fixes the issue, you need to add inbound and/or outbound rules to allow the port.

  • Solution
Posted (edited)
5 hours ago, Zane Mordien said:

@Belankar Is this your first server or do you have others you have set up before? It's stupid to say this, but it is almost always the port forwarding. Use one of the websites that checks if your port is open would be my first advice. 

This led me on the correct path. My internet provider uses so called CG-NAT which means that I share a IPv4 with other people and thus can't connect via v4. Using IPv6 solved the issue. 

One can figure this out by looking up the connected IP address in the terminal: "curl ifconfig.me"
it gave me a IPv6 instead of a v4. Check again with your IPv4: "curl -4 ifconfig.me". If it gives you a different IP than your router shows for your device on the routers website you have to use IPv6.
For windows users, much luck getting to know your ipconfig i guess :P

Edited by Belankar
  • Like 1
Posted
2 hours ago, Belankar said:

I share a IPv4 with other people and thus can't connect via v4. Using IPv6 solved the issue. 

I never would have gotten to this answer, but it's always something stupid like this.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.