saarg

Oh, yeah. ddclient doesn't need any port mappings, so unraids webui can't extract any info about the ports and therefor doesn't show anything. So nothing to worry about.

Where do you see this? Every container get an ip from the docker network when it's using a bridge. If you look at the unraid docker tab you will see the unraid and the docker ip mapping.

Not much we can help with since you haven't supplied any info other than plex have open files and killing the process restart the process.

Try following this https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

If the plex container is stopped, plex is not running. Where do you see a plex process? Have you installed plex as a plugin at one point and forgot about it?

There are no port mapping in host mode. If you look at the docker run command you will see that all ports mappings are turned into variables.

It's better to go ask Nextcloud why they chose to add an ubuntu only binary. There is nothing we can do about it.

Then it's probably because the web update already moved the nextcloud folder. Check the www folder to see if there are any other folders and if there is on, you can move on to next step. The web updater already turned on the maintenance mode I guess.

The topic says Grocy 😇

I'm pretty sure. https://github.com/linuxserver/reverse-proxy-confs/blob/master/grocy.subdomain.conf.sample Haven't you updated your letsencrypt container for a while?

You probably did this in the unraid console and not in the container. Do this first: exec -it nextcloud bash

You need to stub them before they appear in the list. Install the VFIO PCI Config plugin and stub the devices there. You can also append the ID to the syslinux.conf file, but the plugin is probably easier.

We already have a proxy-conf for it in our letsencrypt container.

You can already do this using the extra parameters field.

You can start with this. https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

The template is correct. You are supposed to use the variables in the template and there is nothing in the template that suggest adding the port in the db host variable. Not sure why it didn't work for you, but I think you might have had multiple errors in your template that led to this.

You do not have http:// in the proxy_pass. Also, remove the domain name from your post 😉

What exactly is misleading? I don't see anything misleading and they are pretty clear in my opinion. You can specify the database port as a variable and set it that way. Most people use the standard port. We don't add every option available in the application in the template as we can't foresee all the different options. Usually there are documentation that the user can look up themselves, as now. A quick Google search will find the way to set the database port. Neither me or the template told you to set the port in the DB_HOST variable.

It seems you are a little confused about how docker works. The path you see in the log is the path inside the container, not on unraid. The container doesn't know which path on unraid you set in the template. It's the same with the ports. Port 80 and 443 are the ports used inside the container. Which ports you mapped those ports to on the unraid side is irrelevant for the container. At the top of this file there is a date. If it's not the one below, you should delete the file and restart the container to get the newest. If you have made any changes to the file, you would have to redo them. ## Version 2020/03/05 - Changelog: https://github.com/linuxserver/docker-letsencrypt/commits/master/root/defaults/default

What do you mean with the parameters need some attention?

There is already support for it. All you have to do is stub them.

The default bridge doesn't support DNS resolving, so you can't use the name of the container as the host for the database. This has nothing to do with the containers. So you have to use the unraid IP in DB_HOST. You can make a custom bridge to use the container name in DB_HOST, but it doesn't really matter if you use the name or the IP as it works both ways. Is 192.168.1.254 the IP of unraid?

1. Something unrelated to the container, so probably better to ask for help in general help area. 2. That means you have an error in the file mentioned on line 19.

By top level up, you mean your wan IP? Post the run command for both containers.

notification:generate John Doe hola