alexandru360

I am looking at the same thing and found here on the forum this thread: solved-how-to-create-a-virtual-nic-for-internalisolated-use-only

yep ... that was the problem forgot to switch to the custom docker network

I uninstalled Nerd Tools ... deleted completely SWAG and reinstalled made all the configurations again and still Bad Gateway ... but the main domain works ... I am confused ... I think I have to investigate what Bad Gateway means for Nginx

Nope ... I backed up all my configs, reset everything to default, cloned only deluge[...].conf and restarted swag and for subdomains I get Bad Gateway ... If someone has an idea I'll be all eyes ... Just a thought: I saw on another thread here a response from 2019 that Nerd Pack might interfere with swag "mojo" ... is this still the case ?

After some further investigation I had this lines in my swag log: **** The following reverse proxy confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare them to the samples in the same folder to make sure you have the latest updates. **** /config/nginx/proxy-confs/sonarr.subdomain.conf /config/nginx/proxy-confs/plex.subdomain.conf /config/nginx/proxy-confs/openvpn-as.subdomain.conf /config/nginx/proxy-confs/nextcloud.subdomain.conf /config/nginx/proxy-con

Same with me ... I had my server down like for 3 weeks(I had my mainboard in the warenty) and everything worked plex, gitea, sonarr, deluge, nextcloud ... finally I had all of them working and now all are down again Funny thing now as an exception for other not working dates(misconfiguration of swag/pipeline until swag) is that swag is validating the certificate for everything domain and the above mentioned subdomains but am still getting Bad Gateway ...

Well ... I do not know what to say about that.

Fortunately for me I was stupid enough to leave my mysql-nextcloud docker offline and that was causing my server error but ... in the logs there was no hint whatsoever that this was the case ... now I have a different problem regarding swag and dynamic dns updating for namecheap (works for 15-30 minutes then my ip changes and it doesn't work from web but from inside my lan works well ) I'll bang my head against the scripts some more ...

That also looks like my log unfortunately ... guess in the future I will not rush into an update

/mnt/user/appdata/nextcloud/log This is the path to the log but for me it was not much help ... And yes it happened to me as well after the docker update

I'm using your script, thanks it really helps me

try this:

Hello, I would like to thank the unraid team that created the product For me it is simply awesome I'm a one year Unraid user and I want to share, a little, my thoughts about the server. I had some prior experience with linux(debian/ubuntu based mostly) but I always wanted something like Unraid that has both the liberty for creating scripts/custom stuff from linux console and to have predefined stuff in an interface to get repetitive things done fast (here I'm thinking dockers and community applications). Intentionally I left out the