Skip to content

fix(windrose): allow configuring P2P proxy address#536

Open
zappbrannigan34 wants to merge 2 commits into
pterodactyl:mainfrom
zappbrannigan34:fix/windrose-p2p-proxy-address
Open

fix(windrose): allow configuring P2P proxy address#536
zappbrannigan34 wants to merge 2 commits into
pterodactyl:mainfrom
zappbrannigan34:fix/windrose-p2p-proxy-address

Conversation

@zappbrannigan34
Copy link
Copy Markdown

Description

This PR makes the Windrose P2P_PROXY / P2pProxyAddress variable configurable instead of hard-locking it to 127.0.0.1.

The current egg sets:

required|string|in:127.0.0.1

and marks the variable as not user-editable. This can break invite-code / ICE connections on host-network VPS setups, because Windrose uses P2pProxyAddress as the IP address for P2P/ICE listening sockets.

The official Windrose dedicated server guide describes P2pProxyAddress as the “IP address used for listening sockets” and shows a non-loopback LAN IP in the example config.

Tested

Tested on a Pterodactyl Windrose server using host networking.

Before changing P2P_PROXY:

P2P_PROXY=127.0.0.1

The server registered successfully, but player connection through invite code failed during ICE candidate gathering:

Cannot resolve addresses for host . Status message Host not found.
Error on getting local ICE candidates for BL.

After changing the deployed egg variable:

P2P_PROXY=<server public/allocation IP>

invite-code connection worked.

Changes
Renamed P2P PROXY to P2P Proxy Address.
Updated the variable description.
Made P2P_PROXY viewable/editable.
Removed the in:127.0.0.1 validation restriction.
Added README troubleshooting notes for invite-code / ICE failures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant