aptalca

Use only lowercase in container names otherwise nginx can't resolve them

No alpine package for the module

It seems to be an apache module? So no plans

That's a dns hostname resolution thing. Not nginx's fault. Use all lowercase in container names or define a network alias for the container

First set it to the regular bridge and set up your port forwards if you like. Save and exit. Go into the container settings one more time, change it to proxynet, don't enter an ip and hit save. Unraid doesn't recognize your proxynet as a custom bridge network (assumes it is macvlan) so if you try to change port mappings after selecting proxynet, unraid won't do it properly.

Not sure how duo works but ldap auth is already included. For radius, there is no alpine package in the repo.

No, you can reverse proxy anything through the ip address.

Sure, you just use the ip of the vm in the proxy_pass directive

Reverse proxy it and then use your domain name in that field

Glad to hear it works now

It sounds like your duckdns.conf is messed up somehow. It is only supposed to contain two lines, and two items each, separated by an equal sign, no spaces. Check to see if it's the correct format. You can also pm me the contents (I believe duckdns lets you recreate the token) Also, are there any special characters in your token other than hyphen?

We don't support that

Actually, it was something you did within the last 2-3 months. The update only caused a forced validation due to expiring certs, and that process failed. Check your port forwarding on your router

Either your ip on duckdns is wrong, or your port forwarding for 80 is wrong (or your isp blocks port 80)

What does that mean? Did you set it on the duckdns website? Check the container log. What does that say?

No need for a tutorial. Download the wordpress files into the www folder and navigate to the configuration page. Follow the steps on the wordpress website

That url looks like an internal docker network ip. Are you sure it's still accurate? They are dynamic and can change

You're not using the linuxserver image

You can pull different tags: https://hub.docker.com/r/linuxserver/ombi/tags/

Looks like an ombi error. You should contact them

Very common issue with plex lately. I reverse proxied mine and no longer have any issues

Do we get a prize if we guess right?

Not aware of a gui based management system. It's unlikely that one would work for our image since we changed the locations of a lot of the config files so they are in the appdata folder. You don't really have to use terminal or Linux since all the necessary files are in the appdata folder. You can edit them with notepad++ on windows or any decent file editor on mac. Restart the container for changes to take effect.

That was accurate until yesterday 😉 We just pushed a new build that supports dns validated wildcard certs with duckdns. It requires VALIDATION set to duckdns and a new environment variable added for the duckdns token. There is one big limitation though. The cert will only cover the sub-subdomains such as *.yoursubdomain.duckdns.org but it won't cover yoursubdomain.duckdns.org So if you want to use reverse proxies with the subfolder method, you would do it with a sub-subdomain like www.yoursubdomain.duckdns.org/nextcloud Details are also included in the image description on both github and docker hub

Symlink to the array won't work because inside the container, nginx won't be able to follow that link to the array. Easiest way is to map another location to the container, one that resides on the array, and use that location in the root directive in the nginx site config