I assumed the comments in .env.template mean default values (where clearly interpretable as such). But at least for ROCKET_ADDRESS this seems to be incorrect. The file states:
# ROCKET_ADDRESS=0.0.0.0
The actual listen address:
root@vaultwarden:~# netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 113 52998745 70470/vaultwarden
After setting the option explicitly it listens as expected. Either .env.template is wrong or the rocket default listen is wrong.
Deployment environment
vaultwarden version: 1.27.0
Install method: built from source
Clients used: none
Reverse proxy and version: none
Steps to reproduce
Don't set ROCKET_ADDRESS
Start vaultwarden
Check listen address
Expected behaviour
Listening on 0.0.0.0
Actual behaviour
Listening on 127.0.0.1
Originally created by @dionysius on GitHub (Dec 31, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3077
<!--
# ###
NOTE: Please update to the latest version of vaultwarden before reporting an issue!
This saves you and us a lot of time and troubleshooting.
See:
* https://github.com/dani-garcia/vaultwarden/issues/1180
* https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-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
I assumed the comments in [.env.template](https://github.com/dani-garcia/vaultwarden/blob/main/.env.template) mean default values (where clearly interpretable as such). But at least for `ROCKET_ADDRESS` this seems to be incorrect. The file states:
> # ROCKET_ADDRESS=0.0.0.0
The actual listen address:
```
root@vaultwarden:~# netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 113 52998745 70470/vaultwarden
```
After setting the option explicitly it listens as expected. Either `.env.template` is wrong or the rocket default listen is wrong.
### 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 vaultwarden -->
<!-- Remember to check if your issue exists on the latest version first! -->
* vaultwarden version: 1.27.0
<!-- How the server was installed: Docker image, OS package, built from source, etc. -->
* Install method: built from source
* Clients used: none
* Reverse proxy and version: none
### Steps to reproduce
- Don't set `ROCKET_ADDRESS`
- Start vaultwarden
- Check listen address
### Expected behaviour
Listening on `0.0.0.0`
### Actual behaviour
Listening on `127.0.0.1`
That means the values in the file are generally not the default values.
<!-- gh-comment-id:1368179251 -->
@stefan0xC commented on GitHub (Dec 31, 2022):
Not sure if this is the case for everything but the file clearly states in the beginning that you have to
https://github.com/dani-garcia/vaultwarden/blob/10dadfca068ed449fcd4a74b70ae2cd83990d3d4/.env.template#L3
That means the values in the file are generally **not** the default values.
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 @dionysius on GitHub (Dec 31, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3077
Subject of the issue
I assumed the comments in .env.template mean default values (where clearly interpretable as such). But at least for
ROCKET_ADDRESSthis seems to be incorrect. The file states:The actual listen address:
After setting the option explicitly it listens as expected. Either
.env.templateis wrong or the rocket default listen is wrong.Deployment environment
Install method: built from source
Clients used: none
Reverse proxy and version: none
Steps to reproduce
ROCKET_ADDRESSExpected behaviour
Listening on
0.0.0.0Actual behaviour
Listening on
127.0.0.1@stefan0xC commented on GitHub (Dec 31, 2022):
Not sure if this is the case for everything but the file clearly states in the beginning that you have to
https://github.com/dani-garcia/vaultwarden/blob/10dadfca068ed449fcd4a74b70ae2cd83990d3d4/.env.template#L3
That means the values in the file are generally not the default values.