• Help port forwarding for a Starbound server?
    28 replies, posted
I know this is probably the wrong place to ask but the guys in the thread couldn't help me so oh well. I was able to find out the things needed to port forward and all that, but what I'm trying to set up is a Starbound server, I'm able to join the game with my internal IP fine but it's not working for anyone else and I can't find out the problem. I will provide more details if needed, this is the page I put the port # and IP into. [t]http://i.imgur.com/7Fd8Kwr.jpg[/t] Needless to say I'm about ready to just port forward the fucker out the window.
Are you giving your friends you external ip? (HINT: It's not going to be 192.168.1.101, that's your internal IP) [url=http://www.whatismyip.com/]This[/url] website can help you if you don't know your external IP address.
No, I can join the server fine. I'm using "68.207.83.29" which isn't working. It's saying port "20125" isn't opening either on here. [url]http://www.yougetsignal.com/tools/open-ports/[/url]
You can try setting the protocol to both, also double check that your internal IP is actually 192.168.1.101, If you have already tried those you can try disabling hamachi, I have had some experiences with hamachi messing up routing, although that was years ago.
I'm positive on my internal IP, and I've tried setting to both.
The only other things I could think of would be restarting your router and disabling hamachi. Otherwise resetting the router to defaults and port forwarding again might fix it but I would try turning it off and back on first.
Well, I'm working off this wireless linksys router, and I'm also directly connected to a modem. Should I just keep the "direct" network disabled or what? I've already disabled hamachi, aswell.
If by direct connection to the modem you mean you have an Ethernet cable plugging your PC into the modem and you aren't using the router then you would either need to plug your PC into the router or connect to it wireless.
So, just take the ethernet cable out of the modem and into the router and see what that does, then? [editline]27th December 2013[/editline] So, just take the Ethernet cable out of the modem and into the router and see what that does, then?
Yup, your router can't route packets from/to your server if you aren't plugged into it.
Extremely late response, but that didn't work either.
Did you setup a static IP for your computer?
[QUOTE=Joshua Raphael;43325945]Did you setup a static IP for your computer?[/QUOTE] Yes, I have done this and replaced the ".101" with the ".111" here. [IMG]http://i.imgur.com/BtWRkkB.png[/IMG]
Is your IPv4 address 192.168.1.111 or 192.168.1.101? Also check the "Validate settings upon exit" box
[QUOTE=Joshua Raphael;43326021]Is your IPv4 address 192.168.1.111 or 192.168.1.101? Also check the "Validate settings upon exit" box[/QUOTE] It [I]was[/I] .101, but I set up .111 to make it static.
And you changed that 101 in your port forwarding range to 111?
Yes, I have. [t]http://i.imgur.com/2BkpyW5.png[/t]
In your server.cfg file is upnpPortForwarding set to true, and in your default_configuration.cfg file is gamePort set to 21025, controlPort set to 21026, and authPort set to 21027?
Yes, also this was in "Starbound.config" now.
Since you have made your IP static have you tried launching the server and getting people to try and connect?
Yes, and it didn't work.
Did you set your static IP for your local area or your wireless network?
[QUOTE=Joshua Raphael;43327866]Did you set your static IP for your local area or your wireless network?[/QUOTE] Sorry to be dumb, but how do I tell the difference?
When you were here which one did you click on? [t]http://i.imgur.com/a8AJMQu.png[/t]
Wireless network connection is the one I clicked on.
Well is the port at least open now?
Nope.
Some ISP's block the ports that are well known. AT&T blocks 27015 as far as I'm aware. Try changing the port to something like 22025 in your router's port forwarding page and change the gamePort param in starbound.config to the same and see if that helps.
How did you check if the port was open? Did you telnet the port at all?
Sorry, you need to Log In to post a reply to this thread.