Server port 16262 closed

[Rivet]

I hosted server in DIgital Ocean it was fine for 6 days but suddenly It said 16262 port is closed even tho in the UI of DIgital ocean its all OPen. Now my ping is spiking 20-800

[Beard]

Did you perhaps enable the "Use Steam Relay" in your Main Menu > Join screen?

[Rivet]

Originally posted by Beard:

Did you perhaps enable the "Use Steam Relay" in your Main Menu > Join screen?

Thanks it was the steam issue all along.

[White Rider]

Originally posted by Beard:

Did you perhaps enable the "Use Steam Relay" in your Main Menu > Join screen?

I'm having the same issue when hosting a game just through the in game host option.
When I invite my friend once I'm in game, they have a message at the bottom of the screen when loading in saying port 16262 is closed.

Where should I (or they) be looking to sort this?

[Beard]

Originally posted by White Rider:

Originally posted by Beard:

Did you perhaps enable the "Use Steam Relay" in your Main Menu > Join screen?

I'm having the same issue when hosting a game just through the in game host option.
When I invite my friend once I'm in game, they have a message at the bottom of the screen when loading in saying port 16262 is closed.

Where should I (or they) be looking to sort this?

The "port 16262 closed" error is specifically caused by the 16262 UDP port not being correctly opened either on the server owner’s router or in their firewall. It can be ignored if you are getting it on small coop servers.
If you do want to remove the error message, I can only recommend making sure that you correctly port forward the UDP protocol 16261 and 16262 ports to your Local IP. Alternatively, it will show up if you use the "Use Steam Relay" option when connecting to a dedicated server, in which case the players would have to disable that to remove the error message.

Here are some good guides on how to open the ports:
https://www.noip.com/support/knowledgebase/general-port-forwarding-guide
https://www.windowscentral.com/how-open-port-windows-firewall

If doing that still does not work, I can only recommend contacting your Internet Service provider to make sure that they allow hosting a server on your IP and that they do not block the 16262 port themselves.

[White Rider]

Originally posted by Beard:

Originally posted by White Rider:

I'm having the same issue when hosting a game just through the in game host option.
When I invite my friend once I'm in game, they have a message at the bottom of the screen when loading in saying port 16262 is closed.

Where should I (or they) be looking to sort this?

The "port 16262 closed" error is specifically caused by the 16262 UDP port not being correctly opened either on the server owner’s router or in their firewall. It can be ignored if you are getting it on small coop servers.
If you do want to remove the error message, I can only recommend making sure that you correctly port forward the UDP protocol 16261 and 16262 ports to your Local IP. Alternatively, it will show up if you use the "Use Steam Relay" option when connecting to a dedicated server, in which case the players would have to disable that to remove the error message.

Here are some good guides on how to open the ports:
https://www.noip.com/support/knowledgebase/general-port-forwarding-guide
https://www.windowscentral.com/how-open-port-windows-firewall

If doing that still does not work, I can only recommend contacting your Internet Service provider to make sure that they allow hosting a server on your IP and that they do not block the 16262 port themselves.

Awesome thanks. I'll have a look and try and sort it out.

It's mainly myself and my Mrs that play together (it was my Mrs that's getting the message on screen) but occasionally we might have other friends join so it'd obviously be better if the connection is stable for all.

Thanks again!

[Bykso]

Originally posted by White Rider:

Originally posted by Beard:

The "port 16262 closed" error is specifically caused by the 16262 UDP port not being correctly opened either on the server owner’s router or in their firewall. It can be ignored if you are getting it on small coop servers.
If you do want to remove the error message, I can only recommend making sure that you correctly port forward the UDP protocol 16261 and 16262 ports to your Local IP. Alternatively, it will show up if you use the "Use Steam Relay" option when connecting to a dedicated server, in which case the players would have to disable that to remove the error message.

Here are some good guides on how to open the ports:
https://www.noip.com/support/knowledgebase/general-port-forwarding-guide
https://www.windowscentral.com/how-open-port-windows-firewall

If doing that still does not work, I can only recommend contacting your Internet Service provider to make sure that they allow hosting a server on your IP and that they do not block the 16262 port themselves.

Awesome thanks. I'll have a look and try and sort it out.

It's mainly myself and my Mrs that play together (it was my Mrs that's getting the message on screen) but occasionally we might have other friends join so it'd obviously be better if the connection is stable for all.

Thanks again!

Hello, friend. I'm trying to do this, but when it comes to opening the doors, I have some fields to fill in. For example, I see that I have to fill in the following fields...

* External port
- START
- END

* Internal door
- START
- END

* Protocol

As you can see, I need to enter the number of a START port and an END port. I have these two fields to fill in for both the external and internal port. In which fields should I put 16261 and 16262? How many rules should I create?