CHBMB

OK, here's the deal, the container is working perfectly, it's grabbed the certs and started nginx, but I think somewhere you've configured Nginx wrong and now it's not working, there's no easy fix for this, what I'd recommend, is reinstalling the container, with new appdata and then editing the nginx default file and try to work out where you've introduced the error.

So it's not working on LAN either?

You say it doesn't work on WAN, have you tried using your mobile phone on mobile data? Could be a problem with your router settings And to confirm, it's working on LAN?

nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default - Copy:13 That needs fixing. Look at line 13 in that file You now need to post your default file.

Link me to where you've posted your logs and docker run command (look in the docker FAQ for how to get those)

6 hours is not a huge amount of time, not in the grand scheme of things, and it's a drop in the ocean compared to how long@aptalca has spent optimising this process to make it as easy as possible. But one thing to ponder, this is a community, but it presents a skewed view of things, only those with a problem post, those that get it working first time, do not. As this is an open source project, anybody can write a tutorial, not just the devs, so maybe when you've finished, you might like to write it up to help others and act as a personal aide memoire to yourself. We are quite happy to publish decent articles on our website. Please remember that we all do this in our spare time, and it does tend to irk a little when people suggest we do even more work because their time is so valuable. Docker and Unraid already take the vast majority of the leg work away from server admin and bring it to the masses in my opinion and it's wonderful, but their still needs to be some personal learning that goes on, this is a fully fledged webserver, you're going to be responsible to maintain it and keep it secure, so a degree of understanding about the process is required. Things break, that's computing, to all intents and purposes you're the sysadmin of this system.

Passport showed up then?

Also rtfm https://github.com/Novik/ruTorrent/wiki/Config#configphp

Default user perms of Unraid are nobody:users

If you're not using Unraid, then Discord or Github for support.

You're right, forgot that, thanks!

OK I admit, I'm feeling some sympathy for you.......

There's got to be a great story behind this that I very much am looking forward to chuckling about..... Not me.... gfywap Let me know if there's anything I can do remotely to help though.....

Dunno where you're looking but Pi Zero does have wifi

But you're not getting certificates, it's failing the validation stage, it's trying to hit your domain name and instead getting redirected to the unraid webui. I'll let @aptalca comment further on this as he's the expert, but I'm pretty sure (almost certain) the issue is with your local setup rather than the container and my money is on your port forwarding. Did come across someone recently with similar issues who needed to restart his router before it worked. Everything I see in those logs looks like 443 externally is getting forwarded to 443 on your Unraid server. EDIT: Also bear in mind Unraid's webui is running on Nginx as well.

That's not the case as Nginx in the container isn't started until after the certificate process has occured

There's only really a Pi Zero or Pi 3 depends on how much you want to spend. All the enclosures are pretty similar.

You need to port forward 443 externally to 1443 on your Unraid server

There's a way to do so, but it's unsupported, so once you do so, you're on your own. Scripts in this directory are run at startup So you could map like this -v '/mnt/cache/appdata/letsencrypt/60-customscript:'/etc/cont.init.d/60-customscript' Scripts in that directory are run in numerical/alphabetical order.

Nope

Try using it with a different email provider to check. I know Gmail you have to turn off secure settings to enable things like Nextcloud to utilise the SMTP servers and wondering if it's a similar issue

Also fwiw Heimdall container is Nginx based not Apache

Because the container is setup to use host mode. That's why it's set as host mode in the template.

I use Nginx as the frontend reverse proxy and Heimdall container is behind, use a .htpasswd file to restrict access from WAN

Post your docker run command. Docker FAQ for instructions how to do so.