Installation error

I have to install bitwarden on my server
i get error

[[email protected] isecurity]$ ./bitwarden.sh restart

| |__ () |__ ____ _ _ __ | | ___ _ __
| ’
| | \ \ /\ / / | '__/ _ |/ _ \ ’
| |) | | | \ V V / (| | | | (| | / | | |
|
./||_| // ,|| _,|_|| ||

Open source password management solutions
Copyright 2015-2021, 8bit Solutions LLC
https://bitwarden.com, Bitwarden · GitHub

===================================================

bitwarden.sh version 1.43.0
Docker version 20.10.9, build c2ea9bc
docker-compose version 1.29.2, build 5becea4c

Pulling mssql … done
Pulling web … done
Pulling attachments … done
Pulling api … done
Pulling identity … done
Pulling sso … done
Pulling admin … done
Pulling portal … done
Pulling icons … done
Pulling notifications … done
Pulling events … done
Pulling nginx … done
Creating network “docker_default” with the default driver
Creating network “docker_public” with the default driver
Creating bitwarden-mssql … done
Creating bitwarden-notifications … done
Creating bitwarden-icons … done
Creating bitwarden-identity … done
Creating bitwarden-web … done
Creating bitwarden-api … done
Creating bitwarden-sso … done
Creating bitwarden-events … done
Creating bitwarden-attachments … done
Creating bitwarden-admin … done
Creating bitwarden-portal … done
Creating bitwarden-nginx …
Creating bitwarden-nginx … error

ERROR: for bitwarden-nginx Cannot start service nginx: driver failed programming external connectivity on endpoint bitwarden-nginx (15e7574d42afdfb594a05ade066f9a369064f155173f04265b85c4585c9a4356): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use

ERROR: for nginx Cannot start service nginx: driver failed programming external connectivity on endpoint bitwarden-nginx (15e7574d42afdfb594a05ade066f9a369064f155173f04265b85c4585c9a4356): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.

Do you already have a web server running on port 443?

2 Likes

yes,
any solution for that

This FAQ may be helpful:
https://bitwarden.com/help/article/hosting-faqs/#advanced-configuration

1 Like

Yes, from the link @dh024 posted above:

To use custom ports, instead of 80 and 443, edit the http_port= and https_port= values in ./bwdata/config.yml and run ./bitwarden.sh rebuild to rebuild your server assets.

hello, i have changed as required in config.yml, and i get message

1.43.0: Pulling from bitwarden/setup
Digest: sha256:29bd0777de8b902bd26a67f74c832c8032f1bea41e716277a98f7d439a8f2912
Status: Image is up to date for bitwarden/setup:1.43.0
docker.io/bitwarden/setup:1.43.0

Bitwarden is up and running!

visit https://isecurity.8ty6.co
to update, run ./bitwarden.sh updateself and then ./bitwarden.sh update

but when I hit my URL its showing nothing,

What port number did you use instead of 443? Add that after the URL when you try to access it in your browser. For example, if you used port 1234, add :1234 to the end.

Note: After making changes to this file you need to run the rebuild or update

command for them to be applied.

Full URL for accessing the installation from a browser. (Required)

url: https://isecurity.8ty6.co

Auto-generate the ./docker/docker-compose.yml config file.

WARNING: Disabling generated config files can break future updates. You will be

responsible for maintaining this config file.

Template: server/DockerCompose.hbs at master · bitwarden/server · GitHub

generate_compose_config: true

Auto-generate the ./nginx/default.conf file.

WARNING: Disabling generated config files can break future updates. You will be

responsible for maintaining this config file.

Template: server/NginxConfig.hbs at master · bitwarden/server · GitHub

generate_nginx_config: true

Docker compose file port mapping for HTTP. Leave empty to remove the port mapping.

Learn more: Compose file | Docker Documentation

http_port: 9090

Docker compose file port mapping for HTTPS. Leave empty to remove the port mapping.

Learn more: Compose file | Docker Documentation

https_port: 9191

i have u sed 9191