Rebuilt My Server - A Couple of Snags

[naked_eskimo]

So, I rebuilt my server. I think I did all correctly, but it has been a long time since I've had to reinstall.

For ports:
http is set to 8080 (this is the port that players append in their browser, no?)
WS is set to 8889 (this is for admin connections?)

I can connect locally, but only if I use the LAN address, not my dns name. Which is odd, never had this issue before I dont think. The port forwarding is the same on my router as the rebuilt server has the same ip. I have included both exe in the Windows Firewall.

When I do try to connect using my dns name, I see a rogue connection attempt from my LAN ip in the log. I don't know if remote players can connect yet. Supposed to have a game in 90 mins, but I can't say for certain they will be able to connect.

[strobe878]

Both ports (http and ws) are required for both admin and regular poker functionality.

Step 1: Double-check you have both ports forwarded to the server LAN ip.

Then:

Step 2: Try accessing your site using your public IP address: http://<your public ip>:8080

If that works:

Step 3: Try accessing your site using your domain name: http://<your domain name>:8080

Depending on which step fails and what the symptoms are can inform next steps . . .

[Kent Briggs]

http is set to 8080 (this is the port that players append in their browser, no?)

Correct. So it would be something like 123.123.123.123:8080 or www.example.com:8080

WS is set to 8889 (this is for admin connections?)

The WebSocket port is what the client uses to make a connection back to the server. The admin console also uses the same two ports.

I can connect locally, but only if I use the LAN address, not my dns name.

Did you append the HTTP port to the domain name? That's required if you're using anything other than 80.

Which is odd, never had this issue before I dont think. The port forwarding is the same on my router as the rebuilt server has the same ip. I have included both exe in the Windows Firewall.

What do you mean by "both exe"? You should just use the "Windows Firewall" button in the PM Service Manager to clear the Windows Firewall.

[naked_eskimo]

Thank you for the reply.

I have my port forwarding set to 8080-8889 So it should cover both.

Somehow, I am able now to access using my dns name, not sure why. I didn't change anything.

Should I be able to connect to the other port like this?
ipaddr:88899/admin

Because that is still not working. Would that mean we couldn't play tonight until that was fixed?

[Kent Briggs]

Should I be able to connect to the other port like this?
ipaddr:88899/admin

Use the http port just like you would with the player client but with /admin appended:

123.123.123.123:8080/admin

or

www.example.com:8080/admin

[naked_eskimo]

Thank you. I must have had an old bookmark, because it had 8889/admin in the url. But you are correct.

I was able to test with a remote player. I think I'm good now.

Thanks again!

[naked_eskimo]

I had thought that maybe I needed a program based rule for the manager exe to make the /admin work. I forgot all about the Windows Firewall button.

I can access the admin page if I go ipaddr:88080/admin but not if I use ipaddr:8889/admin even though the http port is set to 8080 and the WS port is set to 8889

[strobe878]

I can access the admin page if I go ipaddr:88080/admin but not if I use ipaddr:8889/admin even though the http port is set to 8080 and the WS port is set to 8889

Both admin and poker clients use the http port in the browser address.

[Kent Briggs]

I can access the admin page if I go ipaddr:88080/admin but not if I use ipaddr:8889/admin even though the http port is set to 8080 and the WS port is set to 8889

Both the player client and the admin console client are loaded via http on the HTTP port. Both the player client and admin console client use the WS port to make a backchannel websocket connection to the server for two-way communication.