manrw

Hi, this is not an issue with the template: https://forums.unraid.net/topic/141336-cant-pull-or-update-docker-containers-dns-issue/

Sounds good 👍. If you still have any trouble after that I would suggest that you open an slskd issue.

Hi, I'd like to emphasize that I'm not the image author but only created the template. This means I generally can't help with any modifications that do not exist in my default template that I provide. That being said, I think you have multiple options to fix the container permissions: Ensure that the directories are owned by the docker user. This is usually "nobody". You can also add this user to a group on your host machine and permit write & read to this user. The application shouldn't need execute. It seems that the container runs on root via default: https://github.com/slskd/slskd/blob/master/docs/docker.md . You could ensure that root can write & read on these directories. In the worst case, you could permit all users to write & read. This is considered bad practice and is not recommended. However, it might not be too bad if no parts of your server are exposed. If you still have trouble, I would suggest reaching out to the author of slskd. Keep in mind that they usually don't know "Unraid" or other distributions and they expect you to provide the docker run command (you can obtain this from Unraid). I hope this helps.

Hi, you need to have a list instead of a single string: https://github.com/slskd/slskd/blob/master/docs/config.md#directories. shares: directories: - "/musique"

Hi, I recommend you to read the configuration for the shared: https://github.com/slskd/slskd/blob/master/docs/config.md#shares . Please note that you must mount your directories to inside the container using a path mode (prefer read-only if possible). Then reference this path using the config. So when you're editing the config file, you're unable to edit it? Have you read https://github.com/slskd/slskd/blob/master/docs/docker.md ? As far as I can see, you should edit this on the mounted directory while the application is stopped, save it and then restart the application.

You'll see an update button in Unraid when it get's updated. We publish updates here and you can subscribe on the repository to get notified by GitHub for new releases: https://github.com/ajnart/homarr/releases

Hi, Dash. does not offer any mount points: https://getdashdot.com/. This is why you don't see any in Unraid.

Hi, Homarr requires you to set an administrator account for security. Once you've created this account, it will no longer ask you for it. However, to make any changes to the boards or settings, you must relogin to your administrator account. If you're having troubles with the account or forgot your password, you can use the CLI to recover your account or start from scratch: https://homarr.dev/docs/advanced/command-line/ Sorry, I don't get your question. How may I help you?

Although I wasn't able to 100% confirm, because I had to wait days to get it to crash, I suspect that it was any of the following containers: - GitLab - Postgres14 - Postgres15 - pgAdmin4 I'd assume that deleting the database would be enough to get rid of the errror. Although it should be noted, that the crash could be caused by a different error that we don't see in the log. The Postgres error is just the last entry and makes it quite likely that it's the reason for the crash. Furthermore, I can confirm that no plugin or Unraid itself was causing the crash.

After debugging multiple weeks, I can confirm that one of the Docker containers caused the crashes. However, I migrated to a different OS due to the frustration and other problems I had. Thanks for your help 👍

Thanks, I'll let it run in safe mode. But without Docker, it's useless to me. I see a Call trace mentioning Postgres and "php-fpm" in the log. I assume php-fpm is from Unraid itself but Postgres is not. Could a Docker container be crashing Unraid? I do run two instances of Postgres. "Corrupted page table at address 55b437033b50" sounds to me that there could be corrupted data in one of the databases. If one container accesses said data only periodically or upon requests, this would explain the seemingly random behavior of the crash.

Finally crashed now. I removed some IPs from the syslog and attached it. unraid-syslog.log

Hi, thanks for the reply. I just set up a rsyslog on my Raspberry Pi and will wait for the next crash. This may take a few hours to days, since I don't have reproduction steps for it. I actually turned on the cloning of the syslog to the flash drive a few days ago - would you want that? Syslog file on Raspberry Pi looks like this: I assume that's ok? EDIT: Can confirm that Remote Syslog is working: It just updated with some messages from a plugin. I'll let you know once I see another crash.

Hello, for the last 3 months I have been having issues with random crashes on my Unraid server. It has been running well before. First, I suspected a hardware failure - so I checked the disk devices and the logs for errors. I noticed that there were PCIe errors for one of my SATA controllers which stated that an error was corrected. Other than that, there was nothing unusual. Every time the server "crashes", USB power on the chasis goes out and I'm unable to establish any connection via IPv4 (ICMP , HTTP and SSH). Pressing the power button once did not shut down the server gracefully (even after 15 minutes) and I always had to press for 5 seconds to restart. After that, the server booted back up and worked normally. Since I didn't have much time due to Christmas and moving to a new apartment, I was unable to further investigate it - it still crashed every 2 hours - 3 days. There is no pattern between the crashes and they seem random to me. Now I finished moving and replaced the SATA controller with a better one. I no longer see the PCIe errors but the server is still crashing. Since I was using an old Z170A board (almost no settings, unable to change C states, ...) with an I7 7600k before, I switched to a Gigabyte B760 Gaming with I3 12100 for much lower idle consumption. This configuration has been working well but the crashes are still happening randomly. Due to the replacements and upgrades, I suspect that this isn't a hardware failure. I am at the end of my troubleshooting steps and would appreciate if you could help me with the next steps. Further context: My server never had a power loss I'm running Ubiquiti DM & multiple switches for my network Power is controlled over multiple NETIO 4C PDUs - but they never turned off according to the history HDMI does not give any output on the screen anymore when I try to look after the crash UniFi controller shows the device as offline after crashing tower-diagnostics-20231217-1909.zip

Hi, this is an issue of the application itself - not the template. Please report any application issues to the author: https://github.com/slskd/slskd/issues . This support thread is only for template related issues. The template uses the official Docker image as well.

Please refer to the official documentation for information regarding permissions & configuration: https://github.com/slskd/slskd/blob/master/docs/docker.md https://github.com/slskd/slskd/blob/master/docs/config.md You can contribute missing properties or environment variables on the template when necessary: https://github.com/manuel-rw/unraid-templates

Great, thanks for confirming. Sadly we have zero control over what they do or which domains are added.

Do you use PiHole or AdGuard? There was an issue caused by their Blocklist: https://github.com/ajnart/homarr/issues/1712

Ok, that's weird. But I'm not going to complain then. If you like the app make sure to let the authors know. As a reminder, I am only the creator of the Unraid template and did therefore not write any of the applications code (except Homarr and the Discord bot).

What port are you using to expose it? Unraid's implementation expects either the default value I set or the configured in the template. If you remove the port, this won't work anymore. See: https://github.com/manuel-rw/unraid-templates/blob/0e10a06b6a2c36604ce57faafe7b5e9f6b987dcc/templates/slskd/slskd.xml#L30 https://github.com/manuel-rw/unraid-templates/blob/0e10a06b6a2c36604ce57faafe7b5e9f6b987dcc/templates/slskd/slskd.xml#L14 You can enter advanced mode (I think it's not visible in standard) and manually change Web UI to the desired value.

Hi, please use the new thread fur any future questions: Regarding the password reset: We are currently working on a feature to reset by console and also enable administrators to reset other users passwords: https://github.com/ajnart/homarr/issues/1616 . In the meantime, you can reset the data by deleting the db.sqlite database. Note that you shouldn't do this in future versions as it will remove your boards in upcoming versions of Homarr. However, it's fine to do in 0.14.0 and 0.14.1 as you'll be prompted with the onboarding process again. Best regards 👋

Notice regarding breaking changes in Homarr version 0.14 Version 0.14 has introduced breaking changes. They are documented here: https://homarr.dev/blog/2023/11/10/authentication#breaking-changes The template has already been updated. You manually need to adjust your existing container if you installed before the update. The required mounting path is /data in the container. New installations with the template require no manual steps.

I updated the template: https://github.com/manuel-rw/unraid-templates/pull/9 It may take multiple hours to update on your server. To update, you must completely remove the container and add it again from the app store. Let me know if this resolves your issue. What does the log show? The latest log should still be available, even after the container stopped. Alternatively, you can view the log using the CLI and the command "docker container logs <container-id>". You can change the DNS in multiple ways in Docker. But let's see what the log says first and then we can troubleshoot more precise. Warning: The log may contain information, that you don't want to show. Make sure to remove any information you don't want to post. Binding other containers to a container's network can be a bit finicky in Unraid sometimes. So just try out and see what sticks

Hi, thanks for the question. This is out of scope of the template - but I'll try to help you. Ensure that you configured the YAML with the appropriate paths: shares: directories: - /music Note: This path must be the inner mountpoint of your container.

Hi, thanks for the question. Using a VPN should be a viable solution with Soulseek - it is P2P after all. However, the trolls seem to be much less of a problem compared to Torrent. Ultimately, it's up to you if you want to use a VPN. You should also take into account that your VPN provider might not allow P2P for certain plans or prohibit it. Less reputable providers will also often keep logs and records of your traffic - so using a VPN doesn't necessarily "hide" you. Ensure, that you selected the network mode "none" in the dropdown and "--net=container:GluetunVPN" in the extra arguments. The log you posted indicates, that it can't connect to api.github.com nor to Soulseek. I'd suggest you to use ping, wget, curl different hostnames to check your connectivity. You can also try to use a different DNS server - like Quad9, Cloudflare or others that are less censored.