novnc web page no longer works as well as vnc port 5900

[xamindar]

The epic store keeps throwing up the captcha to this docker (notifications tell me), however, the access on port 5900 or 6080 no longer work. While It's running, I just receive a connection refused. I assume something has been broken recently as this used to work.

The logs are also stating: VNC is running on port 5900 (no password!) noVNC (VNC via browser) is running on http://localhost:6080

Which is slightly wrong as I do pass the password env to it for vnc. So that appears broke as well.

[SapitoSucio]

Something similar is happening to me

I have a sh script like this:

#vasper
echo "Ejecutando Vaspernin"
docker run --rm -p 6080:6080 -v fgc:/fgc/data --pull=always -e NOTIFY='discord://XXXXXXXXXX' -e BROWSER_DIR=data/browser2 ghcr.io/vogler/free-games-claimer node epic-games >> /var/log/cron.log 2>&1

#sapito
echo "Ejecutando Sapito"
docker run --rm -p 6080:6080 -v fgc:/fgc/data --pull=always -e NOTIFY='discord://XXXXXXXXXX' ghcr.io/vogler/free-games-claimer >> /var/log/cron.log 2>&1

the vasper one has started to do prime-gaming and gog, even when I declare only to be epic-games. Also, I cannot longer use/see vasper's session VNC, only sapito's

[vogler]

however, the access on port 5900 or 6080 no longer work. While It's running, I just receive a connection refused.

If the script is done, the container will stop and you can't connect to VNC anymore. Are you sure it's still running while you try to connect? Nothing in the code has changed regarding VNC.

Which is slightly wrong as I do pass the password env to it for vnc. So that appears broke as well.

Which password do you mean? The message is about VNC_PASSWORD.

[vogler]

the vasper one has started to do prime-gaming and gog, even when I declare only to be epic-games.

The command looks fine and should work the same as before.

Also, I cannot longer use/see vasper's session VNC, only sapito's

If you run them sequentially, that's to be expected since the container will no longer be running then.

[vogler]

Feel free to reopen with details.

[xamindar]

Which password do you mean? The message is about VNC_PASSWORD.

I mean just what I said. The logs report: "VNC is running on port 5900 (no password!)" But I am passing the VNC_PASSWORD variable so it should NOT be saying "no password" in the logs.

That was just a side issue I noticed. The main issue is not being able to access the vnc session at all: I understand the vnc session goes away after it completes. That is not what this issue is about. It is about not having ANY vnc session connection at all while it's running. My container is unable to complete epic games because of a captcha. My assumption is I should be able to connect to the vnc session while it is trying to complete the epic part, before the timeout. But this is not the case.