You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.
I installed the rtorretvpn image and I think I have things working appropriately (thanks for making this so easy!)
I was wondering about some of the firewall settings for the nginx ports. I'm running with wireguard as the VPN and noticed that the iptables rules (I think) can allow traffic from the VPN to hit the nginx proxy. I can't actually get a connection through from the VPN endpoint but I thought it might be good to have an option to explicitly lock down access in the container.
I have a separate nginx reverse proxy that handles authentication and so disabled authentication on the web interface presented in the container.
I installed the rtorretvpn image and I think I have things working appropriately (thanks for making this so easy!)
I was wondering about some of the firewall settings for the nginx ports. I'm running with wireguard as the VPN and noticed that the iptables rules (I think) can allow traffic from the VPN to hit the nginx proxy. I can't actually get a connection through from the VPN endpoint but I thought it might be good to have an option to explicitly lock down access in the container.
I have a separate nginx reverse proxy that handles authentication and so disabled authentication on the web interface presented in the container.
iptables snipit
and
The above suggests that traffic could come in over wireguard to the nginx instance. Is that prevented in some other way?
The text was updated successfully, but these errors were encountered: