mattie112

Is there not an environment variable which has the path to whatever folder it consumes from?

But if you use ipv6 you kinda do need to use it

I made a fork for that: https://github.com/Mattie112/docker-nginx-proxy-manager (I update it a few times a year if I dont forget haha)

Open the console to NPM via the Unraid container page (next to stop/start/restart) and remove it using the shell. OR: delete NPM, then re-'install' it and use the same config/path mapping.

Manually remove the log try again if you already increased the size of the docker image.

The files are not stored in the container but mounted from the /appdata storage share. If you want to start over / clear everything empty-out that folder. Check your docker config to see the exact path of mapped volumes.

And other then what was already suggested: try testing things one by one. Can you access your NPM over IPv6? Does the DNS resolve correctly (perhaps your Unraid machine has a different IP then your NPM container) Does the forwarding work over IPv4?

For quite some time now a docker pull is painfully slow on my Unraid machine. I looked at and already but that seems to be good for me if I understand it correctly. Any ideas on what I can test? tower-diagnostics-20241026-1958.zip

You could try two things. With your phone on 4G try to access both 80 and 443. Are both not working or just one of them? Just to make sure we are looking in the right direction.

Ik strange. You could check in the docker container itself on the filesystem (or in the app data) and manually remove any files that are certificates for your host. Or if you have not a lot of config yet just clear and restart.

Can you chech the certificate view in NPM? Perhaps it did made one and you can just use it. Or chech the drop down where it says 'request new'

You can technically migrate certificates. But: you don't need to, if everything is set up you just get new certificates from letsencrypt. What exactly is the problem? And how is it set up?

Ah, that wasn't so bad Everything has been updated again if someone wants to use it.

I do have a fork that only changes the ports to 80/443 that I have been using for quite some time. (And I think also a couple of other people). Let me update it real quick with all the latest changes as I have not done that in quite some time https://hub.docker.com/repository/docker/mattie112/docker-nginx-proxy-manager I will report here when I updated / tested it, will be somewhere today.

If you mount a file in docker it will always overwrite what is present. (but feel free to create a PR). I did do this way, I think if you search in this topic you should find my post with the file I use.