Gobblerpl

I have exactly the same problem witch VPN as kolofotias. It was working for months and stoped. Any solution? Edit: Works after server restart

Hi, In logs I have a lot of [Info] Radarr.Http.Authentication.BasicAuthenticationHandler: Basic was not authenticated. Failure message: Authorization header missing. Radarr works but I noticed stoped making backups, have some problems with automatic queue refreshing and I can't import any movies. I tried backup but problem still exist. Any ideas? I found solution: I changed authentication required to disabled for local adresses. Is it safe?

Hi, For the past two years of my journey with Unraid, Sonarr has been running without any issues. Last week, I updated to version 7.0. Since then, Sonarr has been having problems with the database. Initially, I had no access to the GUI, and the logs showed: [v4.0.12.2823] NzbDrone.Core.Datastore.CorruptDatabaseException: Sonarr failed to start: Database file: /config/sonarr.db is corrupt, restore from backup if available. See: https://wiki.servarr.com/sonarr/faq#i-am-getting-an-error-database-disk-image-is-malformed I restored from a backup. A day passed. I open Sonarr, I have access to the GUI, I can add series, but I can't use interactive search because a message about a database problem appears. Then I did a restore from a Sonarr settings backup. Today, I open the app and again there's no GUI, and again the logs say: Sonarr failed to start: Database file: /config/sonarr.db is corrupt, restore from backup if available. See: https://wiki.servarr.com/sonarr/faq#i-am-getting-an-error-database-disk-image-is-malformed The backup helps but only temporarily. The database issue keeps returning. Now after another backup in GUI there is a text "disk I/O error disk I/O error" Other apps seem to work like always. What should I do? sowia-diagnostics-20250124-1410.zip

Every few months, I suddenly lose access to my apps. I check Unraid and container isn't running. I assume it crashes for some reason, but I don't see anything in the logs. Is it possible to write a script that would automatically start it?

Hi, After a very long time of seamless usage, I suddenly lost access to the WebUI through Tailscale. Previously, after configuring the VPN, I didn’t have access via local addresses, but it always worked through Tailscale. I’ve tried reboots. Can you help me? Edit1: Also Prowlarr lost conncection with qbit. Solution: I just needed to download new config file from my vpn.

Doesn't work.

Is it possible to configure the mover to move files based on age and when the cache is over 60% full? Currently, when I set it to move files based on age and Move All from Cache-yes shares pool percentage, it only works based on age.

I found serious problem. This plugin cause flash backup every 15 minutes!

Ljm42 thank you very much! It was new plugin DriveStandbyMonitor.

Yes I have but weekly.

Thank you for reply. I checked. No scripts.

I think it's fixed now. Edit: No it's not

Hi, in log I see flash backup every 15 miunutes. How to find the cause? I don't know what could be causing changes so often and regularly. I can't see anything in the file activity plugin. I also tried disabling Docker, but the problem still persists. This has been happening for several days. Can you help me please? diagnostics-20240429-0904.zip

No, directly connected to router

Thank you I will try

I'm echoing what Marino and nmkaufman wrote. The plugin causes high CPU usage 24/7. For some time, I've been wondering what Unraid is doing that keeps my processor always at 70%. It turns out it's this plugin. I'm attaching a screenshot. Is there anything that can be done about this?

On my Unraid 6.12.8 plugin also gone. Moreover I can't install plugin again.

Reinstall worked

Hi, For some time everything was working but my Mullvad subscription ended. I bought Windscribe, downloaded the configuration file, and simply replaced it with the wg0.conf from Windscribe. 1. For a few minutes after starting I can't access the webgui. After several minutes I can. 2. There's no internet connection. I'm attaching the logs. Can you help me please?

Work now. I think fileIO size was too low. When I tried 1000G now everything works. Thank you How does ISCSI perform in terms of data security? If one of the disks in Unraid fails, will I be able to rebuild and remount the ISCSI image?

Hi, I'm worried because from thime to time i see this in logs: Mar 1 19:47:39 Sowia kernel: TCP: request_sock_TCP: Possible SYN flooding on port 3702. Sending cookies. Check SNMP counters. Mar 1 19:34:23 Sowia nginx: 2024/03/01 19:34:23 [error] 18001#18001: *121428 limiting requests, excess: 20.184 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:23 Sowia nginx: 2024/03/01 19:34:23 [error] 18001#18001: *121430 limiting requests, excess: 20.079 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:23 Sowia nginx: 2024/03/01 19:34:23 [error] 18001#18001: *121432 limiting requests, excess: 20.049 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:24 Sowia nginx: 2024/03/01 19:34:24 [error] 18001#18001: *121438 limiting requests, excess: 20.799 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:24 Sowia nginx: 2024/03/01 19:34:24 [error] 18001#18001: *121440 limiting requests, excess: 20.751 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:24 Sowia nginx: 2024/03/01 19:34:24 [error] 18001#18001: *121442 limiting requests, excess: 20.735 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:24 Sowia nginx: 2024/03/01 19:34:24 [error] 18001#18001: *121444 limiting requests, excess: 20.699 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:24 Sowia nginx: 2024/03/01 19:34:24 [error] 18001#18001: *121446 limiting requests, excess: 20.672 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:24 Sowia nginx: 2024/03/01 19:34:24 [error] 18001#18001: *121448 limiting requests, excess: 20.639 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:24 Sowia nginx: 2024/03/01 19:34:24 [error] 18001#18001: *121450 limiting requests, excess: 20.614 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:24 Sowia nginx: 2024/03/01 19:34:24 [error] 18001#18001: *121456 limiting requests, excess: 20.450 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" Mar 1 19:34:24 Sowia nginx: 2024/03/01 19:34:24 [error] 18001#18001: *121458 limiting requests, excess: 20.429 by zone "authlimit", client: 192.168.8.121, server: , request: "PROPFIND /login HTTP/1.1", host: "sowia" I don't understand what is happening. Can you help me? Diagnostics in attachment. sowia-diagnostics-20240301-1955.zip

Hello, I did everything as Asus750 wrote. Few times. The problem is that Windows recognizes the new disk, but it cannot be formatted. A message pops up: The operation could not be completed because the Disk Management console view is out of date. Refresh the view using refresh. If the problem persists, restart the console. Disk Management or restart the computer. Unraid logs: iSCSI Login negotiation failed. Unable to locate Target IQN: cmd exceeds last lba 1 (lba 0, sectors 16) I have no idea what could be wrong. Can you help me? Diagnostics in attachment. sowia-diagnostics-20240229-1556.zip

Hi, First let me say that I am a very beginner. For a month I've been setting things to Unraid, jellyfin, syncthing, tailscale etc. I noticed some strange logs. Is everything ok or is there something wrong with the network? I turned off all dockers and checked them one by one and it turned out that they all produce such logs, so there is no problem with only one. Jun 15 11:42:53 Sowia kernel: docker0: port 1(veth99ab56e) entered blocking state Jun 15 11:42:53 Sowia kernel: docker0: port 1(veth99ab56e) entered forwarding state Jun 15 11:42:54 Sowia avahi-daemon[29577]: Joining mDNS multicast group on interface veth99ab56e.IPv6 with address fe80::c4f9:1eff:fe48:713. Jun 15 11:42:54 Sowia avahi-daemon[29577]: New relevant interface veth99ab56e.IPv6 for mDNS. Jun 15 11:42:54 Sowia avahi-daemon[29577]: Registering new address record for fe80::c4f9:1eff:fe48:713 on veth99ab56e.*. Jun 15 11:45:11 Sowia kernel: docker0: port 2(veth5ce5067) entered blocking state Jun 15 11:45:11 Sowia kernel: docker0: port 2(veth5ce5067) entered disabled state Jun 15 11:45:11 Sowia kernel: device veth5ce5067 entered promiscuous mode Jun 15 11:45:11 Sowia kernel: docker0: port 2(veth5ce5067) entered blocking state Jun 15 11:45:11 Sowia kernel: docker0: port 2(veth5ce5067) entered forwarding state Jun 15 11:45:11 Sowia kernel: docker0: port 2(veth5ce5067) entered disabled state Jun 15 11:45:11 Sowia kernel: eth0: renamed from veth5fc956d Jun 15 11:45:11 Sowia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5ce5067: link becomes ready Jun 15 11:45:11 Sowia kernel: docker0: port 2(veth5ce5067) entered blocking state Jun 15 11:45:11 Sowia kernel: docker0: port 2(veth5ce5067) entered forwarding state Jun 15 11:45:12 Sowia kernel: docker0: port 3(vethcdb84c9) entered blocking state Jun 15 11:45:12 Sowia kernel: docker0: port 3(vethcdb84c9) entered disabled state Jun 15 11:45:12 Sowia kernel: device vethcdb84c9 entered promiscuous mode Jun 15 11:45:12 Sowia kernel: eth0: renamed from veth58acda7 Jun 15 11:45:12 Sowia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethcdb84c9: link becomes ready Jun 15 11:45:12 Sowia kernel: docker0: port 3(vethcdb84c9) entered blocking state Jun 15 11:45:12 Sowia kernel: docker0: port 3(vethcdb84c9) entered forwarding state Jun 15 11:45:13 Sowia avahi-daemon[29577]: Joining mDNS multicast group on interface veth5ce5067.IPv6 with address fe80::4ae:30ff:feed:f833. Jun 15 11:45:13 Sowia avahi-daemon[29577]: New relevant interface veth5ce5067.IPv6 for mDNS. Jun 15 11:45:13 Sowia avahi-daemon[29577]: Registering new address record for fe80::4ae:30ff:feed:f833 on veth5ce5067.*. Jun 15 11:45:13 Sowia kernel: docker0: port 4(veth1fe1eb0) entered blocking state Jun 15 11:45:13 Sowia kernel: docker0: port 4(veth1fe1eb0) entered disabled state Jun 15 11:45:13 Sowia kernel: device veth1fe1eb0 entered promiscuous mode Jun 15 11:45:13 Sowia kernel: docker0: port 4(veth1fe1eb0) entered blocking state Jun 15 11:45:13 Sowia kernel: docker0: port 4(veth1fe1eb0) entered forwarding state Jun 15 11:45:13 Sowia kernel: docker0: port 4(veth1fe1eb0) entered disabled state Jun 15 11:45:13 Sowia kernel: eth0: renamed from vethdc2398b Jun 15 11:45:14 Sowia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1fe1eb0: link becomes ready Jun 15 11:45:14 Sowia kernel: docker0: port 4(veth1fe1eb0) entered blocking state Jun 15 11:45:14 Sowia kernel: docker0: port 4(veth1fe1eb0) entered forwarding state Jun 15 11:45:14 Sowia avahi-daemon[29577]: Joining mDNS multicast group on interface vethcdb84c9.IPv6 with address fe80::ac37:81ff:fe70:96be. Jun 15 11:45:14 Sowia avahi-daemon[29577]: New relevant interface vethcdb84c9.IPv6 for mDNS. Jun 15 11:45:14 Sowia avahi-daemon[29577]: Registering new address record for fe80::ac37:81ff:fe70:96be on vethcdb84c9.*. Jun 15 11:45:14 Sowia kernel: docker0: port 5(vethe932c95) entered blocking state Jun 15 11:45:14 Sowia kernel: docker0: port 5(vethe932c95) entered disabled state Jun 15 11:45:14 Sowia kernel: device vethe932c95 entered promiscuous mode Jun 15 11:45:14 Sowia kernel: docker0: port 5(vethe932c95) entered blocking state Jun 15 11:45:14 Sowia kernel: docker0: port 5(vethe932c95) entered forwarding state Jun 15 11:45:14 Sowia kernel: docker0: port 5(vethe932c95) entered disabled state Jun 15 11:45:15 Sowia kernel: eth0: renamed from veth8c07c85 Jun 15 11:45:15 Sowia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe932c95: link becomes ready Jun 15 11:45:15 Sowia kernel: docker0: port 5(vethe932c95) entered blocking state Jun 15 11:45:15 Sowia kernel: docker0: port 5(vethe932c95) entered forwarding state Jun 15 11:45:15 Sowia avahi-daemon[29577]: Joining mDNS multicast group on interface veth1fe1eb0.IPv6 with address fe80::f1:3ff:fe7a:5fca. Jun 15 11:45:15 Sowia avahi-daemon[29577]: New relevant interface veth1fe1eb0.IPv6 for mDNS. Jun 15 11:45:15 Sowia avahi-daemon[29577]: Registering new address record for fe80::f1:3ff:fe7a:5fca on veth1fe1eb0.*. Jun 15 11:45:15 Sowia kernel: docker0: port 6(veth54b811f) entered blocking state Jun 15 11:45:15 Sowia kernel: docker0: port 6(veth54b811f) entered disabled state Jun 15 11:45:15 Sowia kernel: device veth54b811f entered promiscuous mode Jun 15 11:45:15 Sowia kernel: docker0: port 6(veth54b811f) entered blocking state Jun 15 11:45:15 Sowia kernel: docker0: port 6(veth54b811f) entered forwarding state Jun 15 11:45:15 Sowia kernel: docker0: port 6(veth54b811f) entered disabled state Jun 15 11:45:16 Sowia avahi-daemon[29577]: Joining mDNS multicast group on interface vethe932c95.IPv6 with address fe80::4888:e7ff:fe7c:7dea. Jun 15 11:45:16 Sowia avahi-daemon[29577]: New relevant interface vethe932c95.IPv6 for mDNS. Jun 15 11:45:16 Sowia avahi-daemon[29577]: Registering new address record for fe80::4888:e7ff:fe7c:7dea on vethe932c95.*. Jun 15 11:45:16 Sowia kernel: eth0: renamed from veth454ebbe Jun 15 11:45:16 Sowia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth54b811f: link becomes ready Jun 15 11:45:16 Sowia kernel: docker0: port 6(veth54b811f) entered blocking state Jun 15 11:45:16 Sowia kernel: docker0: port 6(veth54b811f) entered forwarding state Jun 15 11:45:16 Sowia kernel: docker0: port 7(vethfff24b2) entered blocking state Jun 15 11:45:16 Sowia kernel: docker0: port 7(vethfff24b2) entered disabled state Jun 15 11:45:16 Sowia kernel: device vethfff24b2 entered promiscuous mode Jun 15 11:45:16 Sowia kernel: docker0: port 7(vethfff24b2) entered blocking state Jun 15 11:45:16 Sowia kernel: docker0: port 7(vethfff24b2) entered forwarding state Jun 15 11:45:16 Sowia kernel: docker0: port 7(vethfff24b2) entered disabled state Jun 15 11:45:17 Sowia kernel: eth0: renamed from veth4a07b5c Jun 15 11:45:17 Sowia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfff24b2: link becomes ready Jun 15 11:45:17 Sowia kernel: docker0: port 7(vethfff24b2) entered blocking state Jun 15 11:45:17 Sowia kernel: docker0: port 7(vethfff24b2) entered forwarding state Jun 15 11:45:17 Sowia avahi-daemon[29577]: Joining mDNS multicast group on interface veth54b811f.IPv6 with address fe80::c8b3:49ff:fe46:fe03. Jun 15 11:45:17 Sowia avahi-daemon[29577]: New relevant interface veth54b811f.IPv6 for mDNS. Jun 15 11:45:17 Sowia avahi-daemon[29577]: Registering new address record for fe80::c8b3:49ff:fe46:fe03 on veth54b811f.*. Jun 15 11:45:19 Sowia avahi-daemon[29577]: Joining mDNS multicast group on interface vethfff24b2.IPv6 with address fe80::f052:80ff:fec2:8a34. Jun 15 11:45:19 Sowia avahi-daemon[29577]: New relevant interface vethfff24b2.IPv6 for mDNS. Jun 15 11:45:19 Sowia avahi-daemon[29577]: Registering new address record for fe80::f052:80ff:fec2:8a34 on vethfff24b2.*. Jun 15 11:45:19 Sowia kernel: docker0: port 8(veth1874f93) entered blocking state Jun 15 11:45:19 Sowia kernel: docker0: port 8(veth1874f93) entered disabled state Jun 15 11:45:19 Sowia kernel: device veth1874f93 entered promiscuous mode Jun 15 11:45:20 Sowia kernel: eth0: renamed from vethb83e1b5 Jun 15 11:45:20 Sowia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1874f93: link becomes ready Jun 15 11:45:20 Sowia kernel: docker0: port 8(veth1874f93) entered blocking state Jun 15 11:45:20 Sowia kernel: docker0: port 8(veth1874f93) entered forwarding state Jun 15 11:45:22 Sowia avahi-daemon[29577]: Joining mDNS multicast group on interface veth1874f93.IPv6 with address fe80::f9:3fff:fe36:a378. Jun 15 11:45:22 Sowia avahi-daemon[29577]: New relevant interface veth1874f93.IPv6 for mDNS. Jun 15 11:45:22 Sowia avahi-daemon[29577]: Registering new address record for fe80::f9:3fff:fe36:a378 on veth1874f93.*. diagnostics-20230615-1146.zip

Is it possible to somehow set up a reverse proxy without port forwarding on the router? I am trying to configure vaultwarden. Using the tutorial on yt about reverse proxy I got to the point where you have to forward the ports on the router. Unfortunately, it turned out that for LTE internet this does not work, because me and the internet are several IP addresses. Can I somehow get around this in a safe way and make the app available on the Internet without port forwarding?