Migrated self-host problem starting BW behind reverse proxy

Hi all. I have migrated my self-host instance from one server to another. The original instance used certbot to give me my certificate. My new instance is behind a reverse proxy and so I don’t need to use certbot. I’ve performed the migration by copying the bwdata directory to a new install.

My problem is that when I try to start bitwarden, I believe that it is still trying to do something with certbot on port 80. However, I have another service using port 80. I believe I had set the config to a) not use certbot, and b) not use port 80. However I must have missed something because I can’t start bitwarden unless I stop nginx for my other web service, start bitwarden, then restart nginx (after which everything is fine).

in docker-compose.yml (not my real port numbers but they’re not 80 or 443):

      - '<notport80>:<notport80>'
      - '<notport443>:<notport443>'

in config.yml:

http_port: <notport80>
https_port: <notport443>
ssl: false
ssl_managed_lets_encrypt: false

I’ve done bitwarden.sh rebuild before trying to start. I get this error:

docker: Error response from daemon: driver failed programming external connectivity on endpoint certbot (5ebc3355fe6c13fff89b69db2413d038fe4dcc82e7d26410aaabebeb2884b643): Error starting userland proxy: listen tcp4 bind: address already in use.

What am I doing wrong here? How can I either stop certbot or get it to use a different port? Thanks for your help in advance.

Found the answer in another post only seconds after posting my question. In short, I had to delete the bwdata/letsencrypt directory. Then the start script doesn’t try to check/renew the certificate and all is good.

1 Like