Update NGINX proxy manager documentation #6180
-
Is your feature request related to a problem? Please describe.I just spent some time debugging why my nextcloud AIO talk constantly dropping (video)calls and never establishing a connection. While the docs clearly state to open port 3478 on the firewall, it was not immediately clear to me how to forward that traffic to nextcloud. Describe the solution you'd likeThe solution was simple, but might help newbies like me: add a stream host on my reverse proxy (nginx proxy manager) to stream traffic on 3478 TCP/UDP to the nextcloud IP. I was not aware of the stream hosts feature of nginx PM and that part was not in the reverse proxy docs. Ideally, a sub-section/note could be added to the reverse proxies to note that, if Talk is to be used, a stream host (or equivalent for the reverse proxy) needs to be added. Describe alternatives you've consideredN/A Additional contextN/A |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Streams are a bad idea since you will loose the real ip |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, I am not sure I understand as I lack the knowledge, though then makes it even more interesting as to what the SOTA way is to expose Talk's ports when behind a reverse proxy... I think it's still relevant to Nextcloud AIO and its docs as it could be a useful addition. |
Beta Was this translation helpful? Give feedback.
Streams are a bad idea since you will loose the real ip