-
Notifications
You must be signed in to change notification settings - Fork 701
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
Comments
There is a section in which the diagram of all services are shown in docs. |
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? |
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. Also, yeah I agree this information needs to be included docs. |
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. |
Oh yeah, sorry my bad, forgot about websockets and file download connections. 😅 |
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)
The text was updated successfully, but these errors were encountered: