[GH-ISSUE #94] How to pass to VPN Server? #82

Closed
opened 2026-02-26 05:34:14 +03:00 by kerem · 5 comments
Owner

Originally created by @CyberSecGuy on GitHub (Mar 4, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/94

Hi, I'm running a Pulse Secure VPN on my network, and was wondering what I need to do to allow access to my VPN using this. Any info would be great, thanks!

Originally created by @CyberSecGuy on GitHub (Mar 4, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/94 Hi, I'm running a [Pulse Secure VPN](https://www.pulsesecure.net/) on my network, and was wondering what I need to do to allow access to my VPN using this. Any info would be great, thanks!
kerem 2026-02-26 05:34:14 +03:00
Author
Owner

@jc21 commented on GitHub (Mar 5, 2019):

So you're running a VPN on your network and:

  1. you want to allow VPN requests to pass through this software using port fowarding? or
  2. you want to access NPM proxied sites after connecting to your VPN, and they are not accessible to the public internet?
<!-- gh-comment-id:469502626 --> @jc21 commented on GitHub (Mar 5, 2019): So you're running a VPN on your network and: 1. you want to allow VPN requests to pass through this software using port fowarding? or 2. you want to access NPM proxied sites after connecting to your VPN, and they are not accessible to the public internet?
Author
Owner

@CyberSecGuy commented on GitHub (Mar 5, 2019):

The former. Right now I port-forward 80/443 to vpn.ip.address.here which means I cant access nextcloud, jenkins, gitlab etc, because they all want 80 as well.

So I was hoping with this software I could just do vpn.domain.com and ci.domain.com etc.

<!-- gh-comment-id:469504418 --> @CyberSecGuy commented on GitHub (Mar 5, 2019): The former. Right now I port-forward 80/443 to vpn.ip.address.here which means I cant access nextcloud, jenkins, gitlab etc, because they all want 80 as well. So I was hoping with this software I could just do vpn.domain.com and ci.domain.com etc.
Author
Owner

@jc21 commented on GitHub (Mar 5, 2019):

I would think your VPN wouldn't run on HTTP/S ports unless it's for the Web Management interface.

But anyway, yes you can foward 80/443 to this product and create a Proxy Host for vpn.yourdomain.com and access the VPN that way, same for your other services.

<!-- gh-comment-id:469505002 --> @jc21 commented on GitHub (Mar 5, 2019): I would think your VPN wouldn't run on HTTP/S ports unless it's for the Web Management interface. But anyway, yes you can foward 80/443 to this product and create a Proxy Host for `vpn.yourdomain.com` and access the VPN that way, same for your other services.
Author
Owner

@jc21 commented on GitHub (Mar 5, 2019):

However if you are using 80/443 for your VPN tunnelling connections, then you're a bit screwed and should change your VPN ports to something else.

<!-- gh-comment-id:469505560 --> @jc21 commented on GitHub (Mar 5, 2019): However if you are using 80/443 for your VPN tunnelling connections, then you're a bit screwed and should change your VPN ports to something else.
Author
Owner

@CyberSecGuy commented on GitHub (Mar 5, 2019):

I'm sorry, I'm stupid as shit... when I was creating the proxy hosts for the VPN, I set the port to be 80, even though I selected HTTPS. Setting the port to 443 instead, resolved the issue.

Resolved!

<!-- gh-comment-id:469651391 --> @CyberSecGuy commented on GitHub (Mar 5, 2019): I'm sorry, I'm stupid as shit... when I was creating the proxy hosts for the VPN, I set the port to be 80, even though I selected HTTPS. Setting the port to 443 instead, resolved the issue. **Resolved!**
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#82
No description provided.