mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #94] How to pass to VPN Server? #82
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#82
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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!
@jc21 commented on GitHub (Mar 5, 2019):
So you're running a VPN on your network and:
@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.
@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.comand access the VPN that way, same for your other services.@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.
@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!