aptalca

Init file runs during container start. So you can put "apk add --no-cache sslh" in there and it will install if necessary during every container start.

Not willing to route everything through sslh. You can add it yourself via mapping an init file into the /etc/cont-init.d folder

I believe that's a known plex issue. There are a few threads on their forum about it

It looks like there is an invisible/blank character before that return. Did you copy paste from somewhere? Try removing that and restart the container

Not enough info to go on

You can always pull the official php images (whichever version you need) and point the nginx fcgi parameter to the php container's ip address

Config folder path should be "/mnt/cache/blah"

Please pastebin it

You're not supposed to run it in host mode. Either bridge or custom bridge. I recommend "user defined bridge"

Try removing the auth basic lines

Yup, that was my mistake. It's fixed in the next update

Your port forwarding is incorrect. You need to forward outside port 80 to host's 180

Try restarting your router

Post what you have. Either pastebin or screenshots where necessary. And also, are you going to https://ombi.domain.com ?

1) You are running it in host network mode, switch to bridge 2) unraid gui is on port 80, map it to a different port like 81 3) on your router, forward outside port 80 to unraid's port 81

I think you're confused about how webservers and reverse proxy works. You port forwarded 12345 directly to the container's gui. So if you go to domain:12345 you connect directly to the container's gui. It does not go through nginx. With that config, nginx is listening on port 443 so you have to go to https://domain:443 or you can just go to https://domain because 443 is the default https port, meaning if you don't define it, the browser will connect to it by default Then nginx will connect to your container on its internal port and will proxy the connection You may need to read up on how reverse proxy works to learn the basics of the concept. Google is your friend.

Letsencrypt is listening on port 443, the default port for https

Just run letsencrypt on unraid, put in your domain and subdomains, make sure to set "only_subdomains" to true so it doesn't try to validate your main domain with unraid and it will be set up. Then you can do the reverse proxies for transmission and such

Yeah, set the extra domains variable to "domain.com,*.domain.com"

I realize we have a duplicate in there, but it shouldn't cause issues other than a warning in the log. Just so you know, the "include" directive in nginx configs will import an external config. In unifi's conf, line 39 is calling an external file, proxy.conf, which also includes a proxy_http_version directive and that's how you have a duplicate 😉. We'll fix it in the next update, but in the meantime, you can delete line 48 to get rid of that second directive.

yup, I remember running into that issue before with emby where the container was named "EmbyServer" and it wouldn't match as nginx was looking for "embyserver" Good idea to use all lowercase in container names, we do that for all lsio images

Then look for a duplicate directive in your confs

It seems the issue may be uppercase/lowercase related in the container name

I believe the profile files are now hidden, but you can create your own in the config folder somewhere, and those changes will append the default values. There is either a wiki or a forum post on plex about it

You're in the crystal ball territory