Hi there,
I feel like I’m in a different situation than everything I’ve been able to google on this issue. Also, self taught and my understanding of things is full of holes.
My problem is getting “Unable to validate installation id.” quasi instantly during install on my ubuntu 20.04 home server.
bitwarden@Domo:/opt/bitwarden$ ./bitwarden.sh install
_ _ _ _
| |__ (_) |___ ____ _ _ __ __| | ___ _ __
| '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \
| |_) | | |_ \ V V / (_| | | | (_| | __/ | | |
|_.__/|_|\__| \_/\_/ \__,_|_| \__,_|\___|_| |_|
Open source password management solutions
Copyright 2015-2022, 8bit Solutions LLC
https://bitwarden.com, https://github.com/bitwarden
===================================================
bitwarden.sh version 1.46.2
Docker version 20.10.12, build e91ed57
docker-compose version 1.29.2, build 5becea4c
(!) Enter the domain name for your Bitwarden instance (ex. bitwarden.example.com): ***.***.***
(!) Do you want to use Let's Encrypt to generate a free SSL certificate? (y/n): n
(!) Enter the database name for your Bitwarden instance (ex. vault): vault
1.46.2: Pulling from bitwarden/setup
Digest: sha256:47ab15e658ba482e31ed8d3c1ab6f7555d7be7a63de56cd74aa5920a01d8203c
Status: Image is up to date for bitwarden/setup:1.46.2
docker.io/bitwarden/setup:1.46.2
(!) Enter your installation id (get at https://bitwarden.com/host): ***
(!) Enter your installation key: ***
Unable to validate installation id.
Note there isn’t the “Problem contacting Bitwarden server.” part which I had sometimes when messing with the ~/.docker/config.json file (and which I eventually removed). This error took a couple seconds to popup, not like the “Unable to validate installation id.” I get which pops up instantly.
My UFW is open for 80/443, my subdomain’s DNS is setup to redirect to my Nginx server successfully showing the root default landing page (haven’t set a document root).
I’ve created a free org account on bitwarden.com with the email I’m using for getting the id/key.
I’m already running 4 other docker containers behind reverse proxys but I believe there shouldn’t be any ports conflicts:
PORTS
0.0.0.0:5000->5000/tcp, :::5000->5000/tcp
0.0.0.0:6881->6881/tcp, :::6881->6881/tcp, 58846/tcp, 0.0.0.0:8112->8112/tcp, 0.0.0.0:6881->6881/udp, :::8112->8112/tcp, :::6881->6881/udp, 58946/tcp, 58946/udp
0.0.0.0:7474->7474/tcp, :::7474->7474/tcp, 7473/tcp, 0.0.0.0:7687->7687/tcp, :::7687->7687/tcp
0.0.0.0:12000->80/tcp, :::12000->80/tcp
What am I missing to solve this issue? Let me know if I need to share more info or run different tests.
Cheers!