manrw

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.

Got it. Yes, it is possible. I'll adjust the template then... https://getdashdot.com/docs/config/features#dashdot_port It is not. Other Unraid templates have the same issue. Unraid templates are sadly complex enough to create such behaviour. However, I can add the option to configure the Dash. port.

I assume you're talking about Dash.? 1. As mentioned by @JonathanM, Dash. will always run on the same goal. By using the bridge network mode, you can expose the traffic to a different port outside. Ensure that you've set bridge as network mode and check your port definition (https://github.com/manuel-rw/unraid-templates/blob/af4ed47281c724abf3f0c5358387d58276591e8c/templates/dashdot/dashdot.xml#L36) 2. This support thread is only for issues related to the Docker template. This sounds like an application related issue - therefore please report it to Dash. itself: https://github.com/MauriceNino/dashdot

Hi, please report that to Dash. itself. That is not an issue of the template.

Oh, so you executed the commands on your PC / Laptop instead of Unraid in your first message? If the Unraid machine can't ping the IP, it is pretty clear that something in your network is blocking access. Since this is not related to the template, it is likely that you'll have to figure it out yourself: - Is the IP being resolved from the FQDN the same on your Unraid as on your PC? If not that might be a problem. - Do you have VLans / conditional routing for your devices? - Do you have multiple subnets / DNS in your network?

I think I'm not able to help you with the drives not spinning down. All I know is that modern drives don't need to spin down - this seems to be a relict from the past and modern drives can cope with it. Regarding the template update: Yes, that *should* fix the missing utilization. Please let me know if it does once the template has updated.

Can you do the same from inside the container?

Thanks for posting it. I updated the template and I think this should fix the issue you're having. Unraid Apps refreshes each few hours to the new templates - so please wait a few hours until it updated. To update please remove the entire container and create it again using the "Apps".