search

realies / soulseek-docker

🐳 Soulseek Docker Container
https://hub.docker.com/r/realies/soulseek/
MIT License
209 stars 35 forks source link

VNC keeps disconnecting? #87

Closed deadrubberboy closed 4 months ago

deadrubberboy commented 5 months ago

Hi!

Been using this container for years without issue. Today it started acting weird. It connects, and as soon as I log into SLSK VNC disconnects and I end up in a loop back at the SLSK log in screen again. Same thing happens. I don't see any errors in the terminal log in Portainer/Dockge.

Any ideas why this started and how I can correct?

realies commented 5 months ago

try an incognito tab to check if there's any cache causing this

mamema commented 5 months ago

i have similar issues. After some recent update i get constantly disconnected. Using another VNC Viewer revealed the issue. I get "too many security failures". This is new. Quick fixes like: vncconfig -display :0 -set BlacklistTimeout=0 -set BlacklistThreshold=1000000

are not working als this command isn't allowed

realies commented 4 months ago

i've updated the base image and have added a newer soulseek app build from https://groups.google.com/g/soulseek-discussion/c/E69FDwm1puw/m/FGOazKBoAAAJ; please give the latest image a go and let me know if there's any issues

mixm1xmix commented 4 months ago

Updated the image, recreated my container. It just continues to restart the container, never loads properly.

realies commented 4 months ago

I'm looking into fixing this, a temporary workaround should be running it as root.

deadrubberboy commented 4 months ago

I'm looking into fixing this, a temporary workaround should be running it as root.

Thanks for working on this!

Sorry for dumb question: how do we implement this work around? Not sure where to enter root credentials or what they are for the container.

mixm1xmix commented 4 months ago

I'm looking into fixing this, a temporary workaround should be running it as root.

Thanks for working on this!

Sorry for dumb question: how do we implement this work around? Not sure where to enter root credentials or what they are for the container.

If you edit the container, under General Settings enable 'Execute container using high privilege'

However, when I edit the container, it doesn't like these paths, so I cannot save it.

/data/Soulseek Downloads /data/Soulseek Chat Logs

realies commented 4 months ago

To run as root inside you should set PUID and PGID to 0.

You can replace the paths with a space inside with ones without a space. Those are just the default folders the Soulseek app uses, but they are configurable from its settings.

mixm1xmix commented 4 months ago

To run as root inside you should set PUID and PGID to 0.

You can replace the paths with a space inside with ones without a space. Those are just the default folders the Soulseek app uses, but they are configurable from its settings.

Confirmed, PUID and PGID to 0 allowed this to run. Will monitor for a fix and redeploy. Thanks!

deadrubberboy commented 4 months ago

To run as root inside you should set PUID and PGID to 0.

You can replace the paths with a space inside with ones without a space. Those are just the default folders the Soulseek app uses, but they are configurable from its settings.

Works! Thank you!!!

realies commented 4 months ago

Please try the latest build with your previous settings that didn't work. It's best not to run as PUID and PGID set to 0.

mixm1xmix commented 4 months ago

Please try the latest build with your previous settings that didn't work. It's best not to run as PUID and PGID set to 0.

I believe I've patched the image, but it continues to restart with my PUID and PGID.

realies commented 4 months ago

Can you provide a log, @mixm1xmix?

mixm1xmix commented 4 months ago

Can you provide a log, @mixm1xmix?

soulseek.csv

realies commented 4 months ago

This is not the latest image, @mixm1xmix. Try stopping the container and deleting the image you have first.

mixm1xmix commented 4 months ago

Thanks - watchtower had not grabbed the latest update. Looks good, appreciate all your help!

On Sun, 5 May 2024 at 10:28, realies @.***> wrote:

This is not the latest image, @mixm1xmix https://github.com/mixm1xmix. Try stopping the container and deleting the image you have first.

— Reply to this email directly, view it on GitHub https://github.com/realies/soulseek-docker/issues/87#issuecomment-2094810659, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARBGZYFPF6QWW6Q2YSGQHWTZAYXYPAVCNFSM6AAAAABFLG43LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUHAYTANRVHE . You are receiving this because you were mentioned.Message ID: @.***>

deadrubberboy commented 4 months ago

Works for me!