search

leshik / bisq-docker

Bisq in Docker with VNC
MIT License
5 stars 4 forks source link

Error viewing Bisq in the browser: "handler exception: 401 None" #2

Open hodlwave opened 4 years ago

hodlwave commented 4 years ago

Hello,

I'm trying to get bisq-docker running on my single-board computer, and I'm running into the following issue.

I can get the docker containers to run; however, when I try to open the app in my browser, I got the following prompt for my username and password repeatedly:

Authentication Required

http://<ip-where-bisq-docker-is-running>:8080 is requesting your username and password. The site says: “Websockify”

No matter how many times I enter the username / password defined in the .env file the prompt keeps popping up, and Bisq won't load.

I added a logfile for websockify, and every time I try to open up Bisq in the browser, I see the following log:

handler exception: 401 None

I don't see any errors in the bisq app log file, so my guess is there's some issue with the connection to Bisq. For reference, I get the same issue when I try to open bisq with Tor Browser and the onion address. I don't have any prior experience with either websockify or noVNC so any help debugging this would be greatly appreciated!

leshik commented 4 years ago

Something might be wrong with the permissions. You can try to docker exec into the container and check env to see if it was set correctly.

hodlwave commented 4 years ago

It worked! The USERNAME environment variable passed inline in docker-compose.yml wasn't overriding the root username that ended up being required to authenticate with websockify.