Replies: 1 comment 1 reply
-
Hi @EpicLPer, are you sure that the /root/.config/glances/glances_customusername.pwd file contains the hashed password ? On your host, the *.pwd file should be hosted in ~/.config/glances not in ./. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Heya,
I'm a bit lost right now, I've tried a bunch of things but I'm definitely missing (probably a small and tiny) thing somewhere ^^" I want to access Glances over the internet and behind a Proxy + IP restriction but I'm trying to secure it a bit further.
tl;dr - I've set up a Docker, created a password file and if I leave everything at
glances.pwd
it works. However using something likeglances_customusername.pwd
doesn't ask for a password anymore.I'm trying to run Glances in a Docker and want to password protect it, so far I've set everything up as it probably should be. My Docker config looks as following:
I also created a
glances_customusername.pwd
andglances.config
file in the same directory as the docker compose file. The container starts up just fine as it should, it also prints the URL and I can access it, however it doesn't ask for a username and password.The only way I got this to work so far is by using the default
glances.pwd
instead of a custom username, that way I get asked for a username and password. But if possible I'd want to change the username too, just for that extra added protection layer on top :)Thanks already for your help!
Beta Was this translation helpful? Give feedback.
All reactions