Closed technerdist closed 1 month ago
you can check the docs for setting up a vnc password you know; i don't know why it would ask for one based on the network used by the container
I just rebuilt my container with the NOVNC variable set to a password of my choosing, but I still get the same authentication failure.
-e VNCPWD="pw" \
could you test with a password that's at least 6 characters long?
I used a password quite longer than 5 characters long.
On Fri, Dec 8, 2023 at 7:42 AM realies @.***> wrote:
could you test with a password that's at least 6 characters long?
— Reply to this email directly, view it on GitHub https://github.com/realies/soulseek-docker/issues/81#issuecomment-1847104169, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT3RQXBRP5HDYV4IF6AIEW3YIMDL3AVCNFSM6AAAAABAITBDCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGEYDIMJWHE . You are receiving this because you authored the thread.Message ID: @.***>
anything unusual in the logs?
Are you using Reverse Proxy? If so add a web socket in Reverse Proxy >> Custom Headers >> Create Web Socket.
I tend to have connectivity issues on the default bridge network on my Synology's Docker instance. Because of this, I like to put my containers on the host network. Well, unlike the bridge network, when I connect to the container on the host network, I get a prompt for authentication to NOVNC. I'm not sure of the password, or a password that would work in this context. Please assist me understand how to mitigate this issue.