this post was submitted on 23 Oct 2023
29 points (93.9% liked)

Selfhosted

40132 readers
563 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
29
Bitwarden and Nginx proxy manager (aussie.zone)
submitted 1 year ago* (last edited 1 year ago) by tuff_wizard@aussie.zone to c/selfhosted@lemmy.world
9 comments fedilink hide all child comments
 

Hello

I installed bitwarden via their install script a while back and all was working well.

recently I wanted to start running a reverse proxy because security and also its cooler to type in a domain name instead of numbers. I disabled the ngnix instance that bitwarden had installed because it was hogging the same ports a Ngnix Proxy Manager.

Now how should I get Bitwarden accessable? I have the .conf file from the bitwarden Ngnix instance, can I just load that into NMP somewhere?

or should I just change the ports the old ngnix operates on and point NPM at it when the bitwarden subdomain is accessed?

if it was just one service it would be simple but there are many running in the bitwarden stack, all on the same port and I'm very new to ngnix so I can't fully grasp what the .conf file is doing and I'm unable to add new passwords to bitwarden until I get this sorted out.

Thanks

Edit: bitwarden is in docker container, as is Nginx Proxy Manager

you are viewing a single comment's thread
view the rest of the comments
[–] spez_@lemmy.world 3 points 1 year ago (1 children)

SWAG works perfectly, so much easier. It also handles the Let's Encrypt certificates automatically - no more having expired domains.

If a service config isn't available, you can confidently copy another and make a few modifications and have it up and running in no time

[–] Contend6248@feddit.de 1 points 1 year ago* (last edited 1 year ago)

Nginx Proxy Manager does also manage certificates, it makes it even easier to create separate certificates for different subdomains, which is nice for my sanity.

I don't like that anybody checking out one certificate of any service and get all the subdomains I'm running too, and wildcard certificates are bad practice.

I was running the LS.io Letsencrypt container as it was named before, and SWAG for years, without any problems, it does its job, but then i've tried NPM and it made my life easier, i love the ability to change access rules or proxy settings with some simple clicks too, without having to edit countless config files for simple changes everywhere, that's what ultimately made me stay there.