Help on Synology Self hosting : error 404

Ask the Community Password Manager
1

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

2

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.

3

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…

4

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.

5

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…

6

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

7

Hi Marc78,
I think you are setting the reverse proxy wrong, if you use a self-hosted environment.
In reverse proxy you should give <your_id>.synology.me not the bitwarden domain name.
And then to access your bitwarden server in a browser, you should give address
https://<your_id>.synology.me:25647

I do however have a different problem now, I can login on my server webpage, but if I try to login from a Chrome or Firefox plugin again by giving <your_id>.synology.me:25647 in the settings, then it fails to authenticate me with my master password, but the same master password works fine in my webpage.
BR Skotte

8

Hello @Skotte and welcome to the community,

Can you confirm you are running the official Bitwarden container stack?
You may very well be running an unofficial 3rd party server known as Vaultwarden.

The browser extension no longer working is a known issue from the Vaultwarden server with the latest browser extensions.

While I don’t think any incompatibility from Bitwarden is intentional, as Bitwarden makes internal changes and feature additions, things such as this can and have been shown several times in the past to break between the official clients and an unofficial server software such as Vaultwarden.
Of course Bitwarden can only provide support for and ensure compatibly between its own software.

While the Vaultwarden team is fairly quick at releases and updates, especially in cases where a major update causes compatibility issues.
The fact remains it is a hobby project run by a significantly smaller dev team who has to work to reverse engineer the problem, and then come up with a compatible patch in their server software within a completely different coding language rewrite of RUST.
They are good, but these can be some challenges you can face so some additional food for thought.

9

Sorry all for the late reply, but I wish to give an update and maybe help others.

My issue was that after a Synology update, they did something that blocked the containers network. Sorry but I don’t remember where I found the info…

What I did was that I added a firewall rule to allow access to the servers bridge network on my Synology server. That solve the issue.

Hope this might help others…