-
Notifications
You must be signed in to change notification settings - Fork 3k
NPM and OpenVPN #274
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
Comments
I had a big response prepared to basically say "TCP doesn't share like that" but then a simple google has led me to this: https://medium.com/bob-kfir-tech/how-to-have-openvpn-and-ssl-on-the-same-port-f0c8df2b2cc2 I don't use openvpn so I can't give it a go. |
Thanks! I'll give it a try. From my research, it seems you can only accomplish this by putting something in front of NPM to split the traffic. sshl or haproxy. Out of curiosity, what VPN are you using to remote back to your home network if you're using one? |
I'm not. My domains are public and I use http method for letsencrypt verification. |
Got it. Thanks for the info. |
@axiom00 Did you find a solution? |
@gartenbauer Unfortunately no. I tried running HAProxy on my pfsense firewall to split VPN and https but was unsuccessful. I'll make sure to update this issue if I end up figuring out a solution. |
Hi @jc21,
I have OpenVPN running on my home network for those times I need to remote back into my network. OpenVPN is configured to tunnel on port 1194/upd and 443/tcp. For the most part, I tunnel on port 1194 but on occasion I am at a client site that blocks port 1194 and have to resort to port 443 to exit their network.
Before installing NPM, both 1194 and 443 were forwaded to OpenVPN.
Now that NPM is installed, 1194 is still forwarded to OpenVPN, but 80/443 to NPM.
Any suggestions on configuring NPM and OpenVPN to share port 443?
Thanks.
The text was updated successfully, but these errors were encountered: