feat: add wings internal fqdn option #151

Closed
opened 2026-04-05 19:50:56 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @he3als on 5/26/2025

Separates the Wings FQDN option into public and internal:

  • Public is the publicly accessible FQDN that browsers connect to
  • Internal is what the panel uses to connect to Wings internally (optional)
    • If not specified, public is used

Before this PR, Docker dev required container internal IPs to be accessible from the host. This meant rootless Docker didn't work, that https://github.com/chipmk/docker-mac-net-connect was required on macOS Docker Desktop, and that Wings connection would never work on Windows.

However, this PR fixes those issues, while maintaining network isolation. Docs PR: https://github.com/pyrohost/pyrodactyl-docs/pull/16

*Originally created by @he3als on 5/26/2025* Separates the Wings FQDN option into public and internal: - Public is the publicly accessible FQDN that browsers connect to - Internal is what the panel uses to connect to Wings internally (optional) - If not specified, public is used Before this PR, Docker dev required container internal IPs to be accessible from the host. This meant rootless Docker didn't work, that https://github.com/chipmk/docker-mac-net-connect was required on macOS Docker Desktop, and that Wings connection would never work on Windows. However, this PR fixes those issues, while maintaining network isolation. Docs PR: https://github.com/pyrohost/pyrodactyl-docs/pull/16
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pyrodactyl#151