[Bitwarden Self-Hosted Password Manager on Docker]

Just upgraded the memory. It was quite easy, and gave me the chance to remove a lot of dust from the DIsk Station.

Now Bitwarden works perfectly. Thanks all for helping.

 

Yours,

BInkem

[Bitwarden Self-Hosted Password Manager on Docker]

I checked :

 docker logs bitwarden-mssql

 

Quote

sqlservr: This program requires a machine with at least 2000 megabytes of memory.

 

Ok ordered the 8 gb memory module as outlined in this post:

http://blog.fedorov.com.au/2016/02/how-to-upgrade-memory-in-synology-ds216.html

 

Now wait for Amazon to deliver the goods...

[Bitwarden Self-Hosted Password Manager on Docker]

I am now getting mssql restarts. According to the internet this may be a memory problem. My DS216+ has only 1 GB of memory and mssql wants a minimum of two. Has anyone else got the same problem? Or can you run mssql on a 1 Gb machine?

[Bitwarden Self-Hosted Password Manager on Docker]

@shrabok

 

This seems to be helpful. I can now start BItwarden and connect to it from my home network. Tomorrow i'll try to get it to work outside the network.

 

Yours,

 

Binkem 

[Bitwarden Self-Hosted Password Manager on Docker]

Hello,

 

I am trying to install Bitwarden, but running the bitwarden.sh install script it doesn't prompt for the proxy information eg.:

Quote

(!) Do you want to use the default ports for HTTP (80) and HTTPS (443)? (y/n): n (!) HTTP port: 8123 (!) Is your installation behind a reverse proxy? (y/n): y (!) Do you use the default ports on your reverse proxy (80/443)? (y/n): y (!) Do you want to use push notifications? (y/n): y

 

I've got no idea how to get bitwarden to ask these questions and  I do not know what to include in the ./bwdata/config.yml to manually add the proxy. Can anyone help me out here?