Author Topic: I'm having port problems again, and I need a solution.  (Read 2241 times)

Setting a static IP at your workstation and Port forwarding is the only permanent solution to your hosting issues. O  nce you do so, you shouldn't have to forget with it ever again unless your router somehow erases itself
Wot, how do.

Well, the router is owned by me, but it is not like.. down the street from me(The datacenter). If worst comes to worst and I MUST port forward, I am capable of driving down there and logging on locally. But the problem is that I don't want to do this often, as the problem occurs "often". That's why I stated multiple times in OP that I would like to know the solution other than port forwarding. If port forwarding is the only solution, well then rip.

Why don't you have remote access to your router? If you're doing to drive there, set that up aswell for the future.

Wot, how do.
Once you are able to log into your router, refer to the Port Forwarding Guide I wrote up for you earlier

Well, the router is owned by me, but it is not like.. down the street from me(The datacenter). If worst comes to worst and I MUST port forward, I am capable of driving down there and logging on locally. But the problem is that I don't want to do this often, as the problem occurs "often". That's why I stated multiple times in OP that I would like to know the solution other than port forwarding. If port forwarding is the only solution, well then rip.
does the datacenter like hold your router for you? if thats the case why did you lock yourself out of it lmao

anyways i doubt driving down there and logging on manually will let you access the default gateway, but its worth a shot. At the very least you can reset the router and see if that lets you access the gateway

MEGA EDIT: I got confused with the Router and Modem for some reason. So, Correction: we own the Modem not the router. The router is owned by the datacenter, and there is no way for me to port forward on it.

MEGA EDIT: I got confused with the Router and Modem for some reason. So, Correction: we own the Modem not the router. The router is owned by the datacenter, and there is no way for me to port forward on it.
So contact them and ask what to do. It's really simple.

Bump on request of Dragonoid.Slayer

A solution has come courtesy of Cat123, found by the use of him using my server.
Supposedly, blockland woould host on two different ports, and you have to manually change the ports that it hosts on, accordingly to the BATCH file that runs blockland.

Steps for solution:

1 - Open the port on the firewall
2 - Put the port on the .exe
3 - Run the exe
4 - Do: $Pref::Server::Port = "Your Port";
5 - Do quit(); // - IF YOU DONT DO THAT IT WON'T SAVE
6 - Restart


This solution would be applied to servers, that do not have access to a router, hence cannot port forward with any orthodox methods.

I'm not sure if this is useful to anybody, because I don't know if anybody else hosts the way I do, but if it is.. I hope it helps.

So contact them and ask what to do. It's really simple.
Thank you Rotondo!

noedit: (I quoted the wrong person in thanking for the bump)
Bump on request of Dragonoid.Slayer
Thank you Rotondo!

The 'other' port it hosts on happens when the port it wants to use is in use for one reason or another.

I actually have this issue when Blockland crashes in any way, then I open another Blockland (even after waiting 10 mins)

I usually close and reopen the port from the router and it works for me.