aptalca

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

It looks like you're trying to proxy /web through the root domain, and also /web through subfolder /data or /wss and you only added the websocket bits to the /data or /wss subfolder. Does the app actually serve the websockets at subfolder /data or /wss? From the error message, it looks like it doesn't

See how we handle websocket proxy for unifi, these two lines are key: https://github.com/linuxserver/docker-letsencrypt/blob/master/root/defaults/proxy-confs/unifi.subdomain.conf.sample#L46-L47

What are you trying to proxy?

If a docker container has its own ip, the connection between that and the host will be blocked. That's a security feature of macvlan

?? Working just fine over here, no spikes

Macvlan prevents access to host so your pihole won't be able to connect to your unraid host or any containers running in bridge or host mode (or vice versa)

You can map that file in your container settings, similar to mapping a folder

It doesn't need api keys or password, just the address

Follow the container info on either github or docker hub. All you need is in there

Plex has been having issues with remote access for a while. See their forum, it's full of similar complaints. I reverse proxy plex and have no issues

We need more info on your setup. Describe where and how you're running the container (friend's or yours?) and how you're trying to access. Also post your site config that's giving you issues

Did you enable the preset proxy confs? Did you create the new network as described in the readme in the proxy conf folder?

I would put a different router in there to be honest. Different port should work unless you have incorrect redirects in your site config files