connection timed out
Hey I just setup a modded server (self host) for a few friends but they can't join the server. I can join the server on my wifi and it runs completely fine. I swear I port fowarded the ports needed on the machine and router. Did I miss something?
https://mcsrvstat.us/server/192.168.50.188:25565
19 Replies
should server-ip= 192.168.50.188 ?
no need to set the server ip to anything
0.0.0.0 is "Use any usable ip"
!cgnat
We may have bad news for you :C
You may be under a CGNAT which is a method that ISP's use to conserve IPV4 IP's due to how limited they are now. What this means in plain terms is that your IP address is being shared with other people as your router goes to the ISP's router, by default this means port forwarding doesn't work.
We need to check if you are under a CGNAT and we got 2 options.
Option 1: commands
Depending on your OS, run the following command:
- Windows:
iex (Invoke-RestMethod -Uri "https://raw.githubusercontent.com/DominicTWHV/Is-It-CGNAT/refs/heads/main/windows.ps1")
- Linux: curl -s https://raw.githubusercontent.com/DominicTWHV/Is-It-CGNAT/refs/heads/main/linux.sh | bash
-# You should never run such things without reviewing and understanding the code
Option 2: manually
Open your router's configuration interface. Somewhere, you'll see something like 'external' or 'public' IP.
If your external IP is in one of the following ranges, you're basically screwed as long as port forwards go:
- 10.0.0.0/8
- 172.16.0.0/20
- 192.168.0.0/16
- 100.64.0.0/10
- any IPv6 address/range - This shouldn't be a problem, but Minecraft's IPv6 support is still rather quirky. You're at your own, but we're happy if you share your experience.
What do I do now?
You should ask your ISP for a public and IPv4 address (but this may cost you money).
NB: your internal IP should and most probably will be in one of the first three ranges, don't mix them upmanually
you are fucked since you are in the 192.168 ip range
:rip:
but check the rest out
ok thanks
oh manually I missed that
oh good
you are NOT behind it
thats good!
😮
Solution
you had put the wrong public ip on it then
entire setup is on 192
it shouldve been on 135
you put everything on your Gateway ip
which is internal
ok thank you so much
:thumbsupcat:
^
Im going crazy. I've been googling for ages and I don't think this is the issue.
In the wings documentation the node allocation can be found out by hostname -I | awk '{print $1}'
https://pterodactyl.io/wings/1.0/installing.html#node-allocations
So it's the internal not external
I've definitely port forward properly
checked on canyouseeme and its is open
I checked using "netstat -a" and udp is empty? idk how thats possible since I set it to BOTH when port forwarding
Installing Wings | Pterodactyl
Pterodactyl is an open-source game server management panel built with PHP, React, and Go. Designed with security in mind, Pterodactyl runs all game servers in isolated Docker containers while exposing a beautiful and intuitive UI to end users.
you can try to just reinstall the whole thing :shrug:
move your volumes to a safe folder away from the ptero path and reinstall
or from your node just use the 135 ip instead of 192
yeah I tried that and it didnt work :/
idk might try a reinstall
but honestly might quit and just do playit.gg
ðŸ˜
might not help when its still an internal ip friend
anyways found some time and it works now. I blame everything on pterodactyl. if anyone's server is not working for some reason, try starting a server without pterodactyl and test ig. Did a reinstall and it works. (also on ptero if its self hosted don't use server address on the console, use your public ip to connect not the machine ip.)