The port setup is necessary like that because I have a few more services running on the same machine. I do use a reverse proxy, which is located on a whole different machine and handles all of my internal servers. The proxy is using the configuration from here: https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples
Neither SIGNUP_ALLOWED nor ADMIN_TOKEN really do change anything. The message I get when I try to open the admin page in the browser is The admin panel is disabled, please configure the 'ADMIN_TOKEN' variable to enable it.
And I can sign up for new accounts on the web vault, which is basically what I want to disable, since I plan to make my the server available from outside of my home network.
Deployment environment
bitwarden_rs version: 1.20.0 with bitwardenrs/server:latest
Install method: Docker image, using docker-compose
Clients used: web vault
Reverse proxy and version: nginx, most recent nginx:alpine image available. I use a acentral reverse proxy on a RPI to handle all my in-house network stuff.
Other relevant details:
Steps to reproduce
See above - configure a file and start it. The try to open the admin page
Expected behaviour
Admin page is available
Actual behaviour
Admin page is not available
Troubleshooting data
Originally created by @rspindler on GitHub (Apr 5, 2021).
<!--
# ###
NOTE: Please update to the latest version of bitwarden_rs before reporting an issue!
This saves you and us a lot of time and troubleshooting.
See:
* https://github.com/dani-garcia/bitwarden_rs/issues/1180
* https://github.com/dani-garcia/bitwarden_rs/wiki/Updating-the-bitwarden-image
# ###
-->
<!--
Please fill out the following template to make solving your problem easier and faster for us.
This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them.
Remember to hide/redact personal or confidential information,
such as passwords, IP addresses, and DNS names as appropriate.
-->
### Subject of the issue
The environment variable settings in the docker-compose file don't seem to have any effect on the running instance of the bitwardenrs server.
I did configure mine as follows:
```
version: '3'
services:
bitwarden:
image: bitwardenrs/server:latest
container_name: bitwarden
restart: always
ports:
- 8082:80
- 3021:3021
environment:
- WEBSOCKET_ENABLED=true
- SIGNUP_ALLOWD=false
- ADMIN_TOKEN=removed
volumes:
- ./data:/data
```
(For security reasons, I removed the admin token)
The port setup is necessary like that because I have a few more services running on the same machine. I do use a reverse proxy, which is located on a whole different machine and handles all of my internal servers. The proxy is using the configuration from here: https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples
Neither `SIGNUP_ALLOWED` nor `ADMIN_TOKEN` really do change anything. The message I get when I try to open the admin page in the browser is _The admin panel is disabled, please configure the 'ADMIN_TOKEN' variable to enable it_.
And I can sign up for new accounts on the web vault, which is basically what I want to disable, since I plan to make my the server available from outside of my home network.
### Deployment environment
<!--
=========================================================================================
Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab.
That will auto-generate most of the info requested in this section.
=========================================================================================
-->
<!-- The version number, obtained from the logs (at startup) or the admin diagnostics page -->
<!-- This is NOT the version number shown on the web vault, which is versioned separately from bitwarden_rs -->
<!-- Remember to check if your issue exists on the latest version first! -->
* bitwarden_rs version: 1.20.0 with bitwardenrs/server:latest
<!-- How the server was installed: Docker image, OS package, built from source, etc. -->
* Install method: Docker image, using docker-compose
* Clients used: web vault
* Reverse proxy and version: nginx, most recent nginx:alpine image available. I use a acentral reverse proxy on a RPI to handle all my in-house network stuff.
* Other relevant details:
### Steps to reproduce
See above - configure a file and start it. The try to open the admin page
### Expected behaviour
Admin page is available
### Actual behaviour
Admin page is not available
### Troubleshooting data
<!-- Share any log files, screenshots, or other relevant troubleshooting data -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rspindler on GitHub (Apr 5, 2021).
Subject of the issue
The environment variable settings in the docker-compose file don't seem to have any effect on the running instance of the bitwardenrs server.
I did configure mine as follows:
(For security reasons, I removed the admin token)
The port setup is necessary like that because I have a few more services running on the same machine. I do use a reverse proxy, which is located on a whole different machine and handles all of my internal servers. The proxy is using the configuration from here: https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples
Neither
SIGNUP_ALLOWEDnorADMIN_TOKENreally do change anything. The message I get when I try to open the admin page in the browser is The admin panel is disabled, please configure the 'ADMIN_TOKEN' variable to enable it.And I can sign up for new accounts on the web vault, which is basically what I want to disable, since I plan to make my the server available from outside of my home network.
Deployment environment
Install method: Docker image, using docker-compose
Clients used: web vault
Reverse proxy and version: nginx, most recent nginx:alpine image available. I use a acentral reverse proxy on a RPI to handle all my in-house network stuff.
Other relevant details:
Steps to reproduce
See above - configure a file and start it. The try to open the admin page
Expected behaviour
Admin page is available
Actual behaviour
Admin page is not available
Troubleshooting data
@jjlin commented on GitHub (Apr 5, 2021):
See https://github.com/dani-garcia/bitwarden_rs/wiki/Configuration-overview