Hi,
So I installed the unified version on RHEL 9 in docker/podman. The container seems happy and comes up and stays running. However I don’t seem to be able to connect to it?
I assume I should be able to http://192.168.1.10:8080 or similar, depending on IP of my docker/podman box.
I also assume that the port setting in the settings.env file, are all that is needed? As long as that file is referenced when I start the container I should be good?
# Webserver ports
BW_PORT_HTTP=4040
BW_PORT_HTTPS=4043
So the container is started like
docker run -d --name bitwarden -v /$(pwd)/bwdata/:/etc/bitwarden --env-file ./settings.env bitwarden/self-host:beta
and the container seems to be ok
0bda9216e2e docker.io/bitwarden/self-host:beta 8 hours ago Up 8 hours ago bitwarden
[mike@docker1 bitwarden]$ docker logs bitwarden
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Adding group `bitwarden' (GID 1000) ...
Done.
Adding user `bitwarden' ...
Adding new user `bitwarden' (1000) with group `bitwarden' ...
Not creating home directory `/home/bitwarden'.
2023-04-06 08:12:33,911 INFO Included extra file "/etc/supervisor.d/admin.ini" during parsing
2023-04-06 08:12:33,911 INFO Included extra file "/etc/supervisor.d/api.ini" during parsing
2023-04-06 08:12:33,911 INFO Included extra file "/etc/supervisor.d/events.ini" during parsing
2023-04-06 08:12:33,911 INFO Included extra file "/etc/supervisor.d/icons.ini" during parsing
2023-04-06 08:12:33,911 INFO Included extra file "/etc/supervisor.d/identity.ini" during parsing
2023-04-06 08:12:33,911 INFO Included extra file "/etc/supervisor.d/nginx.ini" during parsing
2023-04-06 08:12:33,911 INFO Included extra file "/etc/supervisor.d/notifications.ini" during parsing
2023-04-06 08:12:33,911 INFO Included extra file "/etc/supervisor.d/scim.ini" during parsing
2023-04-06 08:12:33,911 INFO Included extra file "/etc/supervisor.d/sso.ini" during parsing
2023-04-06 08:12:33,914 INFO RPC interface 'supervisor' initialized
2023-04-06 08:12:33,914 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-04-06 08:12:33,914 INFO supervisord started with pid 1
2023-04-06 08:12:34,916 INFO spawned: 'identity' with pid 63
2023-04-06 08:12:34,918 INFO spawned: 'admin' with pid 64
2023-04-06 08:12:34,920 INFO spawned: 'api' with pid 65
2023-04-06 08:12:34,922 INFO spawned: 'icons' with pid 66
2023-04-06 08:12:34,924 INFO spawned: 'nginx' with pid 67
2023-04-06 08:12:34,928 INFO spawned: 'notifications' with pid 69
2023-04-06 08:12:50,301 INFO success: identity entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-04-06 08:12:50,301 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-04-06 08:12:50,301 INFO success: api entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-04-06 08:12:50,301 INFO success: icons entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-04-06 08:12:50,301 INFO success: nginx entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-04-06 08:12:50,301 INFO success: notifications entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
[mike@docker1 bitwarden]$
[mike@docker1 logs]$ curl https://localhost:4043
curl: (7) Failed to connect to localhost port 4043: Connection refused
[mike@docker1 logs]$ curl http://localhost:4043
curl: (7) Failed to connect to localhost port 4043: Connection refused
[mike@docker1 logs]$ curl http://localhost:4040
curl: (7) Failed to connect to localhost port 4040: Connection refused
[mike@docker1 logs]$
I assume I don’t have to configure the email settings to do a quick connect test?
Any ideas very welcome?
Thanks.
D