Author Topic: Dedicated Server  (Read 2962 times)

I have had a working dedicated for a while now.  About a week ago I closed it down for three days.  I put it up again and no one was able to connect, including me.  All that it says when you attempt to join is "Connecting to (IP)".  The dedicated console looks fine, it is posting to rtb server and master server.  I tried joining through blockland.us and it didn't work either.  Help would be appreciated.

Did you port forward and try enabling UpNp disabling it in options while reloading the console for dedicated server.

My ports are forwarded and I have UPnP enabled.  I will try disabling UPnP

No modify button?

Well, disabling UPnP had no success.

What happens when you try to manually connect to the internal IP address? Remember to enter ip:port, for example 192.168.1.5:28100.

I'll try that right now.

Still no modify button...

I tried it, and all I got was

Connecting to server...
Connecting to server...
Connecting to server...
Connecting to server...

What happens when you try to manually connect to the internal IP address? Remember to enter ip:port, for example 192.168.1.5:28100.
I'll try that right now.
Did you use the actual IP he posted? Because it needs to be yours.

I used his, but interesting development, it works now.

As far as I can tell..  I didn't do anything to fix it..  it just.. happened. 

I was about to close dedi when I saw someone had joined..  so i got on and tried to join..  and it worked.  What was wrong?

/facepalm
That was an internal ip address, I'm not surprised it didn't work at first.

Explain.  All i did was connect to that IP address, not host or port-forward using it. 

Oh my gosh.  Not connecting again.'

The dedicated never even went down, it's the same server that worked before!

I don't know why you can't connect via the 192.whatever number
but the other people can't connect using that because it refers to a place inside their router.

Also, other people can connect to it, it's only me that can't.

I don't know why you can't connect via the 192.whatever number
Because he tried the IP that someone else gave him that very likely was not correct for him

Also, other people can connect to it, it's only me that can't.
Are you querying LAN or querying master? Some people can only connect their own dedicated server if they query LAN, and since the server is on your LAN you should be doing that anyways since the query is much faster. Or you could connect directly to 127.0.0.1:28000