Unable to reach the unturned server using my public IP address.
Unable to reach the unturned server using my public IP address.
I configured and have been operating an Unturned 3.0 server on my PC. I can reach it by entering localhost at port 27015 and using the router's IP 192.168.0.195. However, when I try to connect using my public IP (for security reasons) on the same port, the connection fails with a "connection failed" message. I’ve confirmed that ports 27015 through 27018 are open via TCP and UDP, as verified by a software tool (link provided). I also set up inbound and outbound exceptions in my firewall for both Unturned and the server. My PC’s IP is now static, and I can still connect to the server from another device on the same LAN using 192.168.0.185. Essentially, I followed all the recommended steps but still face issues with public IP access.
It appears there may be a problem with your router's firewall or the port forwarding configuration.
The problem isn't there. When you reach an IP not listed in the computers ARP table, it asks the router. If the router doesn’t have it, it checks DNS servers. Because the WAN interface gets assigned to the router itself, you can link to it inside the private network. The router simply sends the request back to itself. You should set up port forwarding to reach a specific internal host. In short, you’re linking to a device on your network by first disconnecting from the public internet. Likewise, I can access my SSH/SFTP server either via its server IP or my home’s public IP—both work, but one is redundant.
I’ll attempt to have another person assist and check their ability. I’ll inform you of the outcome.
The firewall on the router is turned off, but port forwarding is functioning as shown in the diagram provided.
Have you considered checking the basics or looking for any errors?
Did you configure your machine with a fixed IP address and verify that the ports were forwarded correctly? The next possible culprits could be the router's firewall or the Windows security settings.
The ports are set right, I’ve double-checked 27015-27018. Tomorrow I’ll share a photo of the static IP configuration. My computer isn’t powered on yet, but I’m confident it functions since I can reach the internet. The router’s firewall is completely disabled, and both Windows and the public firewall are off—even after testing, it still can’t connect.
To ensure security, enable the firewall and configure exceptions on the server. You can easily add required ports to the exception list. Port forwarding functions as an exception too, especially if set up for UDP and TCP ports 3-4. I’m curious about this. When using a web browser, enter your public IP followed by :27015 (or similar) and see what happens. Do you encounter a special error? For instance, in Chrome, trying to connect to a closed port results in a long delay and an ERR_CONNECTION_TIMED_OUT message. However, connecting to an open port yields an invalid response like ERR_INVALID_HTTP_RESPONSE. This issue usually indicates the server is listening for SSH/SFTP but not responding properly via HTTP. Sometimes developers add custom responses for HTTP requests so you see a simple text saying “protocol mismatch,” which suggests you actually have access to the server on that port. In short, give it a shot—if the software isn’t built to handle requests, you should receive some error feedback.