Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Definite firewall/port requirements in documentation #540

Open
jrwimmer opened this issue Aug 5, 2023 · 5 comments
Open

Request: Definite firewall/port requirements in documentation #540

jrwimmer opened this issue Aug 5, 2023 · 5 comments

Comments

@jrwimmer
Copy link

jrwimmer commented Aug 5, 2023

Please consider adding a section to the Panel and Wings installation guide that includes the ports required for each component to work (as well as what ports can be access-restricted)

@zvikasdongre
Copy link

zvikasdongre commented Aug 5, 2023

There is a section in which the diagram of all services are shown in docs.
Please have a look at Pterodactyl Terminology (Advanced Setup Diagram)

image

@jrwimmer
Copy link
Author

jrwimmer commented Aug 5, 2023

Indeed, though this doesn't fully clarify what ports on the wings node must be accessible to the panel vs accessible to the world.

I know that tcp/2022 must be reachable by end users, but what about tcp/8080?

@zvikasdongre
Copy link

zvikasdongre commented Aug 5, 2023

Technically you don't need to make tcp/8080 public, but it would be necessary if you want to monitor the wings on a server.
And making the port tcp/8080 accessible only by the panel's ip will cause the node list to show red heart because the request to node is made from the user's browser, not from the panel, other than that, I think it should be fine.

Also, yeah I agree this information needs to be included docs.

@MinerPL
Copy link
Contributor

MinerPL commented Aug 5, 2023

Both ports (tcp/8080 and tcp/2022) must be accessible by the end user. Port tcp/8080 is responsible for WebSocket communications as well as downloading files.

@zvikasdongre
Copy link

Oh yeah, sorry my bad, forgot about websockets and file download connections. 😅

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

No branches or pull requests

3 participants