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. The browser extension no longer working is a known issue from the Vaultwarden server with the latest browser extensions. You may very well be running an unofficial 3rd party server known as Vaultwarden. net: 25647”Ĭan you confirm you are running the official Bitwarden container stack? *6 10:12:23 23013#23013: 481950 upstream timed out (110: Connection timed out) while reading response header from upstream, client: xx.x.xxxx, server: bitwarden. and all other files are on /volume1/docker/bwdata/ĮDIT: as a complementary info, I found the /var/log/nginx/ log files, it has the following entry:.My bitwarden.sh script is on folder /volume1/docker/.net (I manually add the “s” on “https”)ĭo you see something wrong with these configurations? globalSettings_baseServiceUri_vault= bitwarden.globalSettings_baseServiceUri_vault= localhost.Here are some settings on my config files: When I try to access my vault on bitwarden. my Synology reverse proxy settings is → (http port specified on the config.yml file).my server is accessible on a custom port, lets say 25647: sousdomain.To summarize, here is my server settings (sorry for the spaces on the URLs, but I can’t post more than 2 links ): I’m writing because I’m having some trouble to access my new Bitwarden install on my Synology NAS.
0 kommentar(er)
