CHBMB

I'm probably not the best person to ask as I don't use Windows I'm afraid......

It's a remnant of that, no idea how to fix it, might be worth asking the Radarr guys.....

Why don't you just add it manually? It has just about as easy a docker run command as I've ever seen..... docker run -p <port>:80 uping/embystat:latest-linux

Unraid isn't designed to have an outward facing webui, it's not hardened for it and although it's possible (at least with nginx - I played around to see how to do it on a VM) it's very much not recommended. Whilst the advice you have received may not be what you hoped to hear and obviously hasn't been well received, it is pretty sound advice nonetheless. Got no experience with Caddy myself, so can't help you with your query, but I can only echo what others have said, which is that it isn't a great idea. If someone does get access to your Unraid webui they essentially have root access on a server on your LAN. Not a situation you'd want to find yourself in to be honest.

Don't worry, I'll ping you @gridrunner

Odds are it's the windows pc. I think ransomware has been described in Linux, but it's very very rare.

I don't know if anyone has ever recovered anything, but iirc the method of infection has been from other pcs on the LAN encrypting the smb shares on Unraid rather than direct infection of Unraid itself. Sorry to hear about it, that really does suck....

No, it's Linux permissions, and it's heavily dependent on which containers you use. Unraid by default uses the user nobody in group users. Not all containers will have their file permissions as nobody:users Then throw into the mix issues with permissions over smb or nfs and it's no wonder you struggle. Running new permissions will change all the file permissions in your appdata to nobody:users but the side effect of this is that this may break the container which is expecting a completely different set of file permissions.

Me too..

Logs and docker run command from a fresh install. Sent from my Mi A1 using Tapatalk

If you're not using Unraid then use our Discord channel for support.

That to me looks like a docker engine error. Things to try 1. Reboot 2. Delete docker.img and recreate it

What's the path that's not accessible to Radarr?

Firstly never use new permissions on appdata, it breaks stuff. It's a permissions problem. But you don't say what containers you're using nor which operating system.

Post your docker run commands for both containers and screenshots of your sabnzbd and radarr configurations.

Did you use @binhex's version at some point? he uses /media by default.

http://$IP-ADDRESS:9981/tvh Still need to specify the port. Sent from my Mi A1 using Tapatalk

How did you tackle it on Debian? The firmware that is loaded is meant to be specified by the driver as I understand it.

This forum is for Unraid support, use our Discord if you're not using Unraid.

Try docker exec -it letsencrypt bash ls -la /etc/nginx/ Not that that matters as it's not involved in the Ombi config

@RockDawg server { listen 443 ssl default_server; server_name server.com; root /config/www; index index.html index.htm index.php; include /config/nginx/ssl.conf; client_max_body_size 0; location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; # With php7-cgi alone: fastcgi_pass 127.0.0.1:9000; # With php7-fpm: #fastcgi_pass unix:/var/run/php7-fpm.sock; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } location / { try_files $uri $uri/ /index.php?$query_string; } location /webfont { try_files $uri $uri/; } location /ombi/ { proxy_pass http://192.168.0.1:3579; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 90; proxy_redirect http://192.168.0.1:3579 https://$host; } }

So I just cleared Ombi off my phone and reinstalled it. Went to https://server.com/ombi and logged in, pressed the burger menu then clicked Open Mobile App and hey presto, just worked.

Personally I'd try it and see if it works before looking for a solution to a problem we're not sure exists, we're on a pretty modern kernel on v6.5.3, so previous issues may have been ironed out.

All of the above firmware is included. What USB device do you have? Why not try and see what it loads by default

@RockDawg Am I missing something? There's no Ombi configuration in either of those server blocks....