Skip to content
This repository has been archived by the owner on May 14, 2024. It is now read-only.

[Bug]: Ground Branch cannot be connected to if behind NAT #2906

Open
joecasanova opened this issue Apr 14, 2024 · 3 comments
Open

[Bug]: Ground Branch cannot be connected to if behind NAT #2906

joecasanova opened this issue Apr 14, 2024 · 3 comments
Labels
bug Something isn't working not confirmed bug has not been reproduced or confirmed

Comments

@joecasanova
Copy link

joecasanova commented Apr 14, 2024

Panel Version

1.11.5

Wings Version

1.11.11

Service

ground branch

Modified

No, I did not modify the egg

Expected Behavior

Install the server, start it and connect successfully with the game client.

Actual Behavior

Server installs and starts. Server shows up in in-game server list. Clients can try to connect but it fails with a pop up after ~15 seconds that says "Pending Connection Failure" - "The pending connection to the server failed."

This also occurs when I try to connect via the console using either assigned port and the WAN or private IP address of the server (NAT configuration but working successfully with many other eggs).

The wings server shows it is listening on the assigned ports via netstat/ss. Netstat/ss within the docker for the ground branch server also show it listening on the assigned query port. Scanning the IP internally or via WAN using nmap shows both ports are open.

Steps To Reproduce

Step 1: Install server via egg without any configuration changes on a wing that is properly configured behind NAT with ports forwarded from the firewall/router.
Step 2: Start server.
Step 3: Try to connect to server with game client from server list.
Step 4: Wait for connection to time out.

Install logs

https://pteropaste.com/o3k2u3jhmv50

@joecasanova joecasanova added bug Something isn't working not confirmed bug has not been reproduced or confirmed labels Apr 14, 2024
@joecasanova
Copy link
Author

Install log from wing server with public IP: https://pteropaste.com/d4az8yjkhms3

@parkervcp
Copy link
Collaborator

If you have a server behind a firewall you need to have the ports forwarded to the internal ip.

@joecasanova
Copy link
Author

joecasanova commented Apr 14, 2024

They are forwarded. I have plenty of other eggs that work fine behind NAT on the two wing servers I tested on and allow players external to the NAT to connect to them via the WAN connection.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working not confirmed bug has not been reproduced or confirmed
Projects
None yet
Development

No branches or pull requests

2 participants