9/27/2023 0 Comments Docker bitwarden server![]() What is that sorcery?įor more tests I modified the Bitwarden nginx configuration $ cp /opt/bitwarden/bwdata/nginx/nf /opt/bitwarden/bwdata/nginx/ It seems Bitwarden is only accepting direct connections from the browser, but not local ones. A OUTPUT -p tcp -m tcp -dport 8180 -m state -state NEW -j ACCEPT A INPUT -p tcp -m tcp -dport 8180 -m conntrack -ctstate NEW,ESTABLISHED -j ACCEPT If I open the 8180 port I can make a connection to Bitwarden. ![]() $ tail /opt/bitwarden/bwdata/logs/nginx/access.log So back to Bitwarden: $ docker stop some-nginx I can also access it through the reverse proxy from my browser. To make sure my Apache has the right configuration, I tested with another nginx Docker: $ mkdir test With this, I cannot connect to the server locally through either wget or my browser. I initially wanted to have a SSL passthrough, but it didn't work: $ cat /opt/bitwarden/bwdata/config.yml | grep -P "(ssl:|8180)" Of course I configured my Bitwarden to serve on port 8180 without SSL. SSLCertificateChainFile /etc/letsencrypt/live//chain.pem SSLCertificateKeyFile /etc/letsencrypt/live//privkey.pem ![]() SSLCertificateFile /etc/letsencrypt/live//cert.pem I configured my Apache with this $ cat /etc/apache2/sites-available/.conf I installed Bitwarden under Docker but cannot make it work through a reverse proxy. I have some websites running in Apache on an Ubuntu 20.04 VM. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |