I might be totally going about this the wrong way - but I’d really appreciate anyone who can steer me in the right direction. This means I can’t properly launch Bitwarden. So what I see is that it’s still trying to bind 443, even though I changed https_port to 444 instead. Status: Image is up to date for certbot/certbot:latestĭocker: Error response from daemon: driver failed programming external connectivity on endpoint certbot (e7ad08a13667cf96d3dd2823ea9c7e089020e3c16e79c8514c91d89680e41f2e): Bind for 0.0.0.0:443 failed: port is already allocated. However, after rebuilding I went to do bitwarden.sh start and I get: Open source password management solutionsĭocker-compose version 1.29.2, build 5becea4cĭigest: sha256:d13d98ebf10c37e864da33f89585dfc712185fca0b6740d956106f64d467ee6a
My next step was to figure out how to get Nginx to associate to those ports. Then I ran bitwarden.sh rebuild, to make it pull in those changes. So I went into Bitwarden’s bwdata/config.yml and changed http_port to 800, and https_port to 444. My understanding is that the idea would be for Nginx to be the only thing operating on the main 80 and 443 ports, and it would direct traffic to Bitwarden on a different port, but only if that traffic is looking for bw. What I’m struggling with is configuring this. I found that Nginx Proxy Manager is an option people often use (and, from my understanding, the main Bitwarden already uses Nginx?). Traffic for bw. would be directed to the Bitwarden Docker container, while would go to the main web page. My understanding is that this is where a reverse proxy comes in. This creates a conflict, since Bitwarden wants to use port 80 to serve everything, but I want to also host my generic webpage, which would also use port 80. I stress that I am running this all on a single Debian server. Then, to access my Bitwarden instance, I would use bw. I want to go to my personal website (which I’m writing myself in pure HTML/CSS, rather than using Wordpress or similar - I think it’s fun to learn to do things myself).
The next thing I’d like to do is put the Bitwarden page in a subdomain. Now, if I go to my domain, I am greeted with the Bitwarden main login page. I now have a working installation, and I’m happy about that!
This included buying a domain name (From Namecheap), associating its DNS record to my IP address, etc. I followed all the instructions on Install and Deploy - Linux | Bitwarden Help Center. That being said: I’ve installed Bitwarden on my Debian server. I’m just a nerd with a server in my apartment and I want to learn how to host things on the internet. I’m not an IT employee or anything, I’m not deploying stuff to multiple users, and I don’t need to manage tons of accounts. I’m new to self-hosting, and I’m trying to get things set up.
0 kommentar(er)
