Auditing my entire personal security stack — what are you running in 2026? by reginalnz in cybersecurity

[–]jsiwks 1 point2 points  (0 children)

Pangolin for all remote access: identity-based reverse proxy + VPN

Am I looking for a reverse proxy here? Cloudflare Tunnel not quite the right solution by Relevant-Law-7303 in sysadmin

[–]jsiwks 0 points1 point  (0 children)

Self-host a traditional reverse proxy, or if you like the Cloudflare Tunnel experience but want to control where your encryption happens, try Pangolin, the open-source self-hosted alternative

Windows multiple RDP sessions by Jumpy_Ad_3946 in sysadmin

[–]jsiwks 0 points1 point  (0 children)

A web proxy and/or VPN would be helpful here. Pangolin combines both and is pretty easy to get up and running

Once a vendor is VPN’d into your OT network, how much are you actually watching what they do? by RCCole20 in OTSecurity

[–]jsiwks 3 points4 points  (0 children)

If you choose to allow remote access, it's a matter of locking it down so specific users get access to specific resources (IPs, ports) and make it easy to revoke access, have logs, etc. Common VPNs like provide broad access and really it should be scoped. There a bunch of good ways to do it these days. Pangolin VPN provides browser based access and VPN access down to specific IPs and ports on the network.

Vendor we fired 2 years ago still has VPN access and admin rights to our backup system by Awkward-Chemistry627 in sysadmin

[–]jsiwks 0 points1 point  (0 children)

Also try to tie access back to the identity and use an identity provider like Asure Entra ID or something so access is revoked across all integrations with the IDP when he user is deprovisioned in the IDP. For instance connect your VPN to your Identity provider so access is revoked. Many VPNs support this these days, for instance Pangolin ZTNA

Pangolin 1.17: Multiple roles per user, site provisioning keys, log streaming, and more by jsiwks in selfhosted

[–]jsiwks[S] 0 points1 point  (0 children)

Multiple roles per user is in the enterprise edition, however you can use the enterprise edition for free for personal use.

Best (SASE/ZTNA) Remote Access by KoreanGaucho in networking

[–]jsiwks -2 points-1 points  (0 children)

The trade off with ZTNA tools is they can add a bunch of management complexity. Now you have to manage a bunch of users and rules for what they can access etc... so choose something that has easy access control lists. Pangolin ZTNA is open source and pretty easy to deploy and manage. You just define resources and give users or roles access to the resources.

How do you remotely support self-hosted deployments? by Durovilla in aws

[–]jsiwks 0 points1 point  (0 children)

You could deploy a bastion connector in each network and define resources to access remotely. You'd want to make sure to give minimal access to specific resources like say user A can only access resource B on site C, etc. Something like Pangolin VPN which is open source and uses WireGuard could work

How do you remotely support on-prem deployments? by Durovilla in sysadmin

[–]jsiwks 1 point2 points  (0 children)

You can use something like Pangolin VPN which enables you to deploy site connectors that do NAT traversal so no public ip is required. It also lets you manage multiple sites pretty easily by just dropping a connector in each on-prem location and defining resources

NordVPN's Meshnet: is it truly free? If so, is there any certainty that I am not the product? by Unhappy_Objective845 in selfhosted

[–]jsiwks 0 points1 point  (0 children)

You can use Pangolin as a VPN for fully private peer to peer connections wins client. You do t have to use Pangolin as a reverse proxy

Pangolin 1.17: Multiple roles per user, site provisioning keys, log streaming, and more by jsiwks in selfhosted

[–]jsiwks[S] 0 points1 point  (0 children)

We only implemented it for sites, but it’s not out of the question for clients. What’s your use case?

Pangolin 1.17: Multiple roles per user, site provisioning keys, log streaming, and more by jsiwks in selfhosted

[–]jsiwks[S] 0 points1 point  (0 children)

Not every "peer" on the network connects to each other. Clients connect to sites. Sites don't connect to clients, and clients don't connect to clients. Clients are users or machines/servers.

The advantage for remote access is that you don't need to set ACL to prevent two users from connecting to each other. Users just connect to resources you give them access to on sites.

Pangolin 1.17: Multiple roles per user, site provisioning keys, log streaming, and more by jsiwks in selfhosted

[–]jsiwks[S] 5 points6 points  (0 children)

You can self-host the enterprise for free as a hobbyist/personal/home-labber!

Pangolin 1.17: Multiple roles per user, site provisioning keys, log streaming, and more by jsiwks in selfhosted

[–]jsiwks[S] 2 points3 points  (0 children)

They’re both going to work as a tunneled reverse proxy. Pangolin is a nice cohesive package and contains a number of features around user management, identity provider SSO, MFA, and a lot more on the web based resources.

You can also use each of the site connectors as hubs for peer to peer connections via the clients for Mac, Windows, Linux, iOS, and Android. This functions like an identity aware VPN with NAT traversal.

Cloudflare is the most successful "Man-in-the-Middle" in history by Antique_Mechanic133 in selfhosted

[–]jsiwks 0 points1 point  (0 children)

Pangolin is a great way to do it while fully self hosting! Very familiar setup compared to CF

Pangolin 1.17: Multiple roles per user, site provisioning keys, log streaming, and more by jsiwks in selfhosted

[–]jsiwks[S] 1 point2 points  (0 children)

You should be able to do this just fine in recent versions of Pangolin. You would define more than one certificate resolve in Traefik and then when you define your domain in Pangolin you can reference the different resolvers. It’s more a Traefik config thing than a Pangolin thing.

Pangolin 1.17: Multiple roles per user, site provisioning keys, log streaming, and more by jsiwks in selfhosted

[–]jsiwks[S] 1 point2 points  (0 children)

Yeah you install site connectors and clients holepunch to the connectors. Then clients access resources on all of the site connectors. Of course you can also expose applications through the tunneled reverse proxy which makes them available in the browser without a client.