Installing bitwarden on Synology Diskstation

Until lately I had been using 1Password as my trusted password manager. I had been using it since 1Password 4 and lately bought the upgrade to 1Password 7 for Mac and Android. Syncing between devices was done by using Dropbox. It was pretty easy. But then it was time to share some passwords with my wife. I was looking the possibilities. Creating 1Password vault and shared it per Dropbox, or using the 1Password for families for 4,99 USD per month. Other alternatives, such as Lastpass, Dashlane and Bitwarden, are subscription model and you need to upload your password to their server.

But Bitwarden advertises itself as open source and can be self-hosted. But although it’s self-hosted, you have to pay the monthly subscription to use all the features. Then I came to an unofficial implementation of the Bitwarden server written in Rust, called bitwarden_rs. It has all the official Bitwarden’s features minus the subscription.

Continue reading Installing bitwarden on Synology Diskstation

Synology NAS as backup drive

Using Apple TimeMaschine to backup entire Macbook is an easy step. But what about files, which are shared between users/devices? here comes a Synology NAS to help.

I’ve been using Synology since DS207. Now a DS216+ saves all the precious data and pictures. As I wrote, backup a Mac with TimeMaschine on a Synology DiskStation is an easy step. But what about shared file on cloud platform like Dropbox, Google Drive and so on? Synology can handle that too 🙂

Continue reading Synology NAS as backup drive

Connection refused after installing DSM 6.0 Beta

After installing the newly released DSM 6.0 beta for Synology NAS, I was unable to reach the DSM again. My Chrome browser showed “Connection refused”. Not really a good start for beta testing new software. connection-refused

Luckily SSH is still up. Since DSM running on nginx, it’s straightforward to look for some error log in the nginx error log.

shows following log records

in the file /usr/syno/etc/ssl/ssl.chain.crt/server.crt I found a weird certificate formatting

There’s a missing newline between the chained certificate. Put a new line between the certificate and restart nginx.

and restart nginx

Tadaaaa… DSM is available again.