Open jamesblonde007 opened 1 month ago
Same issue, must be the latest update. Waiting for fix :)
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
Hi Will there be a fix for the issue you think? @realies
@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
Any updates about this issue?
I got a bad feeling about this
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 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?