Help on Synology Self hosting : error 404

Hello to all,

I’m writing because I’m having some trouble to access my new Bitwarden install on my Synology NAS.

To summarize, here is my server settings (sorry for the spaces on the URLs, but I can’t post more than 2 links :frowning:):

When I try to access my vault on https:// bitwarden . domain .net : 25647, I’m having a 404 error :frowning:

Here are some settings on my config files:

  • global.env:
    • globalSettings__baseServiceUri__vault=http:// localhost
  • global.override.env:
    • globalSettings__baseServiceUri__vault=https:// bitwarden . domain .net
  • app-id.json:
    • “ids”: “https:// bitwarden . domain .net
  • config.yml:
    • url: https:// bitwarden . domain .net (I manually add the “s” on “https”)
    • generate_compose_config: true
    • generate_nginx_config: true
    • http_port: 27270
    • https_port:
    • ssl: false
    • real_ips:

Do you see something wrong with these configurations?

  • My bitwarden.sh script is on folder /volume1/docker/
  • and all other files are on /volume1/docker/bwdata/

EDIT: as a complementary info, I found the /var/log/nginx/ log files, it has the following entry:

*2022/02/16 10:12:23 [error] 23013#23013: 481950 upstream timed out (110: Connection timed out) while reading response header from upstream, client: xx.x.xxxx, server: bitwarden .domain .net, request: “GET / HTTP/2.0”, upstream: “http:// 127 .0 .0 .1 :27270/”, host: “bitwarden .domain .net: 25647”

Thank you in advance for your help,

Best regards,
Marc

Hi @Marc78 - Bitwarden server is not supported on Synology NAS systems. My guess is you are installing a different piece of software like Vaultwarden, which is not a Bitwarden product. Sorry.

Thanks for the reply.

Actually I first installed Vaultwarden, and then when I realized it was a 3rd party app, I start to do some digging to see if there was a 1st party app.

I contacted Bitwarden support (as a premium user) and they explain that the steps described in their documentation should be similar on my NAS.

I also found some blog posts (here and there) that explain the procedure.

I’m having some chat with the support, but I also decided to try my lucky over here, maybe someone knows what I’m getting wrong with my conf…

My best guess it is a firewall rule issue within the Synology.
I know I have seen a few similar posts in the Vaultwarden forums for people who install that in their Synology. The issue of accessing the internal docker container through the Synology reverse proxy tends to cause this issue. I will try to update back if I can find some specific posts you can reference and check against your installation.

Hello and thanks for the reply.

I’m not sure about the firewall issue. At the moment I have Vaultwarden up and running well.
One time I also had a Subsonic server, and it worked well.

I also have some other reverse proxy rules, they all seems to work: Vaultwarden, subsonic, …

I can’t be 100% sure, but for me I think it’s port related, somewhere on the configuration files. Or maybe something wrong with the install, that I can’t identify…

So any news?

For information, I did some more testing, changing my reverse proxy port to 443, but nothing changes.
I also arrives to ping bitwarden.domain.net.

My latest test was to try http://<server_IP>.27270, but in this case I’m getting a 504 error.

Other way I’m getting a little tired, I’m thinking in stick with my already working Vaultwarden instance…

Thanks again for all the help,

Best regards,
Marc