aptalca

Well, I couldn't get nat reflection to work on pfsense even without double nat, so maybe that's some consolation for you. I am also using split dns. With that, we have no choice but to run letsencrypt on at least port 443. You'll have to change unraid's https port to something else. I kept unraid on port 80 for http, so when I hit my addresses inside my lan, I use the https endpoint and all is well.

Doesn't unraid default the appdata location to /mnt/user/appdata ? Is that share created as a cache only share by default? I don't remember because I manually set all of mine a long time ago

The folder is not remembered, but if you open the folder again, the open files are remembered

Did you look at the config files? https://github.com/linuxserver/docker-letsencrypt/blob/master/root/defaults/default#L43 https://github.com/linuxserver/reverse-proxy-confs/blob/master/bazarr.subdomain.conf.sample#L17

There is a docker argument for setting the hostname

Every night at 2:08. On container start it only tries to renew if it's expired or expiring within 24 hours

Why don't you take 1 step at a time? Start with reading the docs, because they tell you to put your top duckdns address you have control over as the url, which would include your subdomain. Then you can enter whatever you like into the subdomains field and they'll cover your sub-subdomains. Then check the logs to make sure the cert was created successfully. Then check to make sure your main homepage is working (or try the www version if you did wildcard). Only then attempt the reverse proxy. Don't try to set up 5 things at once and then get confused because it didn't work.

That's the point I'm trying to make. We don't use .htaccess, that's an apache thing. Just create the htpasswd file as it says and uncomment the relevant auth lines in the confs

Read the instructions in the readme on how to use htpasswd

No, letsencrypt allows multiple certs for the same domains (with some limits)

That's an upstream thing. In earlier versions it was stored, including the last opened folder. Newer versions don't store anything. I don't like it either

Sounds like you're having networking issues or some other unraid issue

I don't quite understand the last question, but you can add multiple names to the server name directive http://nginx.org/en/docs/http/server_names.html

The three lines above that proxy_pass line set the variables. Edit those instead to point to the ip and port instead of the container name and port

To start with, we recommend turning it off. Once you get everything working, you can then experiment with it. I believe with http validation it outright doesn't work because letsencrypt acme server's validation request goes to cloudflare instead of the letsencrypt container (not too sure about it). With dns validation you can get it to work if set correctly. But we don't provide support for that. There are quite a few different settings on cloudflare for proxy and they can be confusing.

Look, I'm not trying to be rude and I don't claim to have all the answers. In fact, I asked you if you googled it because that's the first thing I do when I have an issue. I posted the picture of the first Google result (highlighted answer) because it tells you exactly what the issue is. I suggest you focus on that rather than get worked up about my post. It tells you "Error 522 indicates that Cloudflare is unable to reach the origin web server and the request times out", which means cloudflare can't connect to your server. I honestly don't know how to word it any clearer. It looks like you turned on caching on cloudflare (which we recommend against), and your server is not accessible. Check your ip, port forwarding, etc.

That's what I do for a couple of things as well. But I also make sure there is additional auth (like http auth) for good measure. I did a bunch of tests on different networks and it seemed to work as intended.

That one is a special one because heimdall was designed to be the main homepage

Did you Google it? It tells you exactly what the issue is

Check out the preset heimdall subdolder proxy conf. It does exactly that

Sounds like port 80 forwarding issue

Looks like you set the version variable to "stable", which is not a supported value

Also, we don't really know how the app determines idle state. On desktops, they often look at things like mouse and keyboard input among other things (same as screensaver kicking in) but as you can imagine those things are not the same for a server

Check the client logs?