realies
After update on Synology, soulseek UI doesn't work
I updated Soulseek on Synology today using the usually successful method of updating via the Container Manager. All port settings seem to be as before. This time I can't access the UI and the logs are full of the same errors being repeated over and over:
Can anyone help?
I don't have a Synology system, but using the docker compose in this repository works fine: https://github.com/realies/soulseek-docker/blob/b145e0d8f294b058d802cf33f5791d18b62d6b5f/docker-compose.yml
Can you provide more information on how you run the container?
It has been working without issue until the last update. I use container manager to run the container.
There was also an update to the Synology OS which I applied 2 days ago in case that's maybe related. https://www.synology.com/en-uk/releaseNote/DSM
It has been working without issue until the last update. I use container manager to run the container.
There was also an update to the Synology OS which I applied 2 days ago in case that's maybe related. https://www.synology.com/en-uk/releaseNote/DSM
Sounds like we have identical experiences
@pixelpowder, to do a fix, I need to reproduce the issue. I don't have Synology hardware. Can DSM be used without it?
@realies havent tried personally:
https://www.youtube.com/watch?app=desktop&v=EKRdsDp_e34&t=521
haven't had enough time to check yet, the DSM virtualisation appears to require some; could you guys try to LLM it in the meantime?
I can use standalone for now its not a problem but when im not on my local network your solution allows me to externally connect to soulseek and download directly to NAS which is so good.
Just updated to the latest release today. Unfortunately the issue hasn't been resolved.
Yup same unfortunately
On Mon, Nov 18, 2024 at 8:50 AM jamesblonde007 @.***> wrote:
Just updated to the latest release today. Unfortunately the issue hasn't been resolved.
— Reply to this email directly, view it on GitHub https://github.com/realies/soulseek-docker/issues/101#issuecomment-2482307428, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4D5CZKK2SWPOFETDN6SJ2T2BGS6DAVCNFSM6AAAAABQVWZRC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBSGMYDONBSHA . You are receiving this because you were mentioned.Message ID: @.***>
I got DSM running in a VM and I don't see the same issue. In fact, it runs as expected. What hardware are you running it on?
I just tried it and still same errors
latest DSM DSM 7.2.2-72806 Update 2 DS1522+ hardware
On Fri, Dec 20, 2024 at 6:07 PM realies @.***> wrote:
I got DSM running in a VM and I don't see the same issue. In fact, it runs as expected. What hardware are you running it on? dsm-soulseek.png (view on web) https://github.com/user-attachments/assets/ffaa1302-7f2d-4fe7-b46e-259fb4ede348
— Reply to this email directly, view it on GitHub https://github.com/realies/soulseek-docker/issues/101#issuecomment-2557484779, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4D5CZO5WSJHEOC52OC32ID2GRMHVAVCNFSM6AAAAABQVWZRC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJXGQ4DINZXHE . You are receiving this because you were mentioned.Message ID: @.***>
thanks for the feedback, I'll release a debug build later today which can hopefully tell us more about why it crashes
Ok, thanks for the update.
On Sat, 21 Dec 2024 at 15:43, realies @.***> wrote:
thanks for the feedback, I'll release a debug build later today which can hopefully tell us more about why it crashes
— Reply to this email directly, view it on GitHub https://github.com/realies/soulseek-docker/issues/101#issuecomment-2558155422, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4D5CZLNREEV7HTB2PIDYHL2GWECDAVCNFSM6AAAAABQVWZRC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGE2TKNBSGI . You are receiving this because you were mentioned.Message ID: @.***>
I've added more logging and a static port configuration in the file that appears to cause the crash: https://github.com/realies/soulseek-docker/blob/55b887936bea3017abf8b50b47d8e48b9df32cf1/rootfs/etc/s6-overlay/s6-rc.d/svc-novnc/run#L4-L14
What do you see in the logs with the realies/souseek:debug image?
https://hub.docker.com/layers/realies/soulseek/debug/images/sha256-c8a4009b8903f6843e45b5188d2d123331f54d3c40149bddf10a6ed0e496bcef
I would love to help if I can but I'm afraid that I don't understand how to help. Would you mind setting out the steps?
- Find out how to set the image name and tag in the container configuration
- Set it to
realies/soulseek:debug - Run it and copy the startup log here
ok, I hope I understood correctly. Here was the result:
soulseek-debug date,stream,content 2025/01/03 12:23:10,stdout,[mi] mieq: warning: overriding existing handler (nil) with 0x5599b0560580 for event 3
2025/01/03 12:23:10,stdout,[mi] mieq: warning: overriding existing handler (nil) with 0x5599b0560580 for event 2
2025/01/03 12:23:10,stdout,Errors from xkbcomp are not fatal to the X server
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86NavInfo
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86SidevuSonar
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86ClearvuSonar
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86TraditionalSonar
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86RadarOverlay
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86DualRangeRadar
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86SingleRangeRadar
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86FishingChart
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86NavChart
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86Sos
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86MarkWaypoint
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86AutopilotEngageToggle
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86PreviousElement
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86NextElement
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86CameraAccessToggle
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86CameraAccessDisable
2025/01/03 12:23:10,stdout,> Warning: Could not resolve keysym XF86CameraAccessEnable
2025/01/03 12:23:10,stdout,The XKEYBOARD keymap compiler (xkbcomp) reports:
2025/01/03 12:23:10,stdout, - proxying from :6080 to localhost:5900
2025/01/03 12:23:10,stdout, - No SSL/TLS support (no cert file)
2025/01/03 12:23:10,stdout, - Web server. Web root: /usr/share/novnc
2025/01/03 12:23:10,stdout, - Listen on :6080
2025/01/03 12:23:10,stdout,WebSocket server settings:
2025/01/03 12:23:08,stdout, vncext: created VNC server for screen 0
2025/01/03 12:23:08,stdout," vncext: Listening for VNC connections on all interface(s), port 5900 " 2025/01/03 12:23:08,stdout, vncext: VNC extension running!
2025/01/03 12:23:08,stdout,Fri Jan 3 11:23:08 2025
2025/01/03 12:23:08,stdout,
2025/01/03 12:23:08,stdout,
2025/01/03 12:23:08,stdout,Underlying X server release 12101011
2025/01/03 12:23:08,stdout,See https://www.tigervnc.org for information on TigerVNC.
2025/01/03 12:23:08,stdout,Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
2025/01/03 12:23:08,stdout,Xvnc TigerVNC 1.13.1 - built 2024-04-01 08:26
2025/01/03 12:23:08,stdout,
2025/01/03 12:23:08,stdout,s6-rc: info: service legacy-services successfully started
2025/01/03 12:23:08,stdout,
2025/01/03 12:23:08,stdout,
2025/01/03 12:23:08,stdout,Press Ctrl-C to exit
2025/01/03 12:23:08,stdout,
2025/01/03 12:23:08,stdout, http://soulseek-debug:6080/vnc.html?host=soulseek-debug&port=6080
2025/01/03 12:23:08,stdout,
2025/01/03 12:23:08,stdout,Navigate to this URL:
2025/01/03 12:23:08,stdout,
2025/01/03 12:23:08,stdout,
2025/01/03 12:23:08,stdout,s6-rc: info: service legacy-services: starting
2025/01/03 12:23:08,stdout,s6-rc: info: service init-setup successfully started
2025/01/03 12:23:08,stdout,usermod: no changes
2025/01/03 12:23:08,stdout,Starting webserver and WebSockets proxy on port 6080
2025/01/03 12:23:08,stdout,Using local websockify at /usr/share/novnc/utils/websockify/run
2025/01/03 12:23:07,stdout,Warning: could not find self.pem
2025/01/03 12:23:07,stdout,s6-setuidgid soulseek /usr/share/novnc/utils/novnc_proxy --vnc localhost:5900 --listen 6080 --web /usr/share/novnc
2025/01/03 12:23:07,stdout,Full command that will be executed:
2025/01/03 12:23:07,stdout,id -nu 1000 = soulseek
2025/01/03 12:23:07,stdout,User resolution:
2025/01/03 12:23:07,stdout,PUID=1000
2025/01/03 12:23:07,stdout,NOVNC_PORT=6080
2025/01/03 12:23:07,stdout,VNC_PORT=5900
2025/01/03 12:23:07,stdout,Environment variables:
2025/01/03 12:23:06,stdout,s6-rc: info: service legacy-cont-init successfully started
2025/01/03 12:23:06,stdout,s6-rc: info: service legacy-cont-init: starting
2025/01/03 12:23:06,stdout,s6-rc: info: service fix-attrs successfully started
2025/01/03 12:23:06,stdout,s6-rc: info: service init-setup: starting
2025/01/03 12:23:06,stdout,s6-rc: info: service fix-attrs: starting
2025/01/03 12:23:06,stdout,s6-rc: info: service s6rc-oneshot-runner successfully started
2025/01/03 12:23:06,stdout,s6-rc: info: service svc-novnc successfully started
2025/01/03 12:23:06,stdout,s6-rc: info: service svc-tigervnc successfully started
2025/01/03 12:23:06,stdout,s6-rc: info: service svc-soulseek successfully started
2025/01/03 12:23:06,stdout,s6-rc: info: service svc-openbox successfully started
2025/01/03 12:23:06,stdout,s6-rc: info: service s6rc-oneshot-runner: starting
2025/01/03 12:23:06,stdout,s6-rc: info: service svc-novnc: starting
2025/01/03 12:23:06,stdout,s6-rc: info: service svc-openbox: starting
2025/01/03 12:23:06,stdout,s6-rc: info: service svc-soulseek: starting
2025/01/03 12:23:06,stdout,s6-rc: info: service svc-tigervnc: starting
I tried reaching the UI on port 6080 (and 5900) but was unable to connect.
Are you able to connect after a forced reload (dropping cache) or through an incognito window? If not, what's the error?
My apologies, in my rush to test this I hadn't set up the port config settings yet. After setting everything up properly, I was able to access the UI and everything is now working. Nice!
Just curious, what changed?
This is the diff for the debug image: https://github.com/realies/soulseek-docker/commit/55b887936bea3017abf8b50b47d8e48b9df32cf1. The main difference is that it uses static port values instead of using the VNC_PORT and NOVNC_PORT environment variables for them.
It makes me wonder if the latest tag instead of debug works fine too after you did the port configuration.
No, I was just lazy when I did the first debug test so please disregard that test. Before then, I always had the port configuration set up and if you remember it was an update (via Container Manager) which bricked the application, and that update inherited the port config settings.
This is strange because in appears that the other scripts that use environment variables work fine.
But not the one that starts noVNC. Can you try the latest tag once again after this finishes building? https://github.com/realies/soulseek-docker/actions/runs/12672831245/job/35317741604
Same issue with DS920+ running DSM 7.2.2-72806 Update 2.
Soulseek was running fine, but updated to latest image via Container Manager and can no longer connect to noVNC.
Installed debug image and am able to connect normally.
