Melawen

I've just come across this issue after upgrading to 6.12.1 yesterday. I've never seen it happen before. It turned out to be Jellyfin in my case causing the issue. As soon as I stopped that docker, my CPU usage dropped from maxing out all the cores to a steady 20%.

I'd love to see this too. I've recently started ripping a whole load of my Blu-rays and would love to be able to queue them instead of having to move one, wait (an eternity for rsync to do it's copy/delete operation 😉) then queue the next one ....

Looks like you have your ports the wrong way round on your router. The external ports should be 80 & 443 and the internal ones should be 180 & 1443. You might also want to hide your actual IP address in the images above.

OK, so I've managed to get slightly further with this, but it still doesn't work properly. My VM has a capital M for Mail, so I've changed the server_name to Mail.* and can now get to domain.com or even box.domain.com, but if I try to visit any of the other pages on the website (domain.com/games.html for instance) I get the security error. The same goes for the webmail at box.domain.com/mail. Even worse, if I try www.domain.com it goes straight to the Unraid web frontend. Additionally, Thunderbird keeps popping up with certificate errors asking me to add an exception. I'm not sure what I'm doing wrong. Every place where I see people talk about this, they say all you have to change is the upstream_app to the IP address, and this clearly doesn't seem to be the case. [Edit] Ignore the Unraid web frontend bit. I forgot to change port 80 to the alternate port for SWAG in my router port forwarding. www.domain.com now just gives the same certificate error that all the other pages do.

Does rather seem that way at the moment unfortunately. I'm relatively new to Unraid but notice the group do seem to put out a fair amount of dockers (and probably have real jobs too) so hopefully we'll get some responses when they have time.

Here's mine, with obvious bits edited for privacy <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'myinstanceid', 'passwordsalt' => 'mypasswordsalt, 'secret' => 'mysecret ... shhhh', 'trusted_domains' => array ( 0 => '10.10.0.25', 1 => 'mydomain.com', ), 'dbtype' => 'sqlite3', 'version' => '21.0.2.1', 'overwrite.cli.url' => 'https://mydomain.com', 'overwritehost' => 'mydomain.com', 'overwriteprotocol' => 'https', 'installed' => true, 'maintenance' => false, 'theme' => '', 'loglevel' => 2, );

Hi, I've been tinkering around with SWAG today to set up a couple of Docker instances and a VM. After watching SpaceInvader One's YouTube video I've changed my router to now point to the Unraid server instead of the VM and both the Docker instances work, but I'm really struggling with the VM. I have, for a number of years, been using Mail-in-a-Box (https://mailinabox.email/) as my personal mail server on a Ubuntu VM. It works really well and also has inbuilt letsencrypt to automate certificate renewal. Obviously SWAG does this too, but I don't want to mess around with the VM config and break things. I've been reading through this thread and trying to get it working, but I'm just stumped as nothing I do seems to work (which means I'm obviously not doing something right)! For info, MiaB uses box.domain.com as its default and also manages the webserver at www.domain.com. It also has an inbuilt DNS server which you point to from your registrar. The comments I keep seeing from everyone is to change the app to an IP instead of a server name, so this is what my current config file looks like that I've copied from the _template.subdomain.conf and named mail.subdomain.conf. server { listen 443 ssl; listen [::]:443 ssl; server_name mail.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app 192.168.1.210; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } I haven't added anything to the SWAG Docker settings other than the initial settings to add the subdomains for the Docker instances, and I'm not sure what or where I should change there (if anything) if I don't want SWAG to manage the letsencrypt certificates for the mail server. Help, please