58
submitted 1 year ago by [email protected] to c/[email protected]

I have a suite of services exposed using a reverse proxy (npm) protected with passwords, but I'm always a bit nervous that username/passwords aren't enough -- is there a way to set up 2FA either on Nginx Proxy Manager side or on, e.g., the 'arr suite of apps?

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 3 points 1 year ago

If you're comfortable with using Cloudflare, you can use their zero trust tunneling and setup an application layer that adds auth to those services. I have mine protected by my GitHub login.

[-] [email protected] 3 points 1 year ago

Oh interesting. I'm using zero trust tunneling already to get through my ISP network chicanery. How would that work? Do yo uhave any tutorials you can recommend?

[-] [email protected] 4 points 1 year ago

cloudflare dash

You can secure your tunnels using the Access menu and then adding an application. It should be somewhat straight-forward but you're basically looking to create an access policy and then adding the rules you want. For example a simple one is to add an allow rule for certain emails. When you enter your email an access code will be sent to you before you can access the application resource. That's just one of many ways to secure it using their application config and access policies.

[-] [email protected] 1 points 1 year ago

I used to expose my Vaultwarden instance with it, but I think it didn't work with the protected CF login.

[-] [email protected] 1 points 1 year ago

Likely because the apps need access to the host and the policies were likely blocking it since it's non-interactive.

this post was submitted on 25 Jul 2023
58 points (96.8% liked)

Selfhosted

39251 readers
313 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS