mattie112

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.

I am currently on holiday and I can't really go through a zip on mobile . I want to suggest to open the docker logs of NPM and see if it logs anything when you open your site. Can you check and paste a bit of log here if that's the case?

You can create your own config file and "overwrite" that with a docker volume. I do the same and it works perfectly.

Or run it on a different IP all together. That should also work (so bridge network)

The logs?

You cannot put a file in a SMB share? Or your paperless has problems accessing a folder? The first one is not a paperless issue so perhaps worth a separate post? In the Unraid Tools menu there is a "(docker safe) new permissions" option that might fix your issue.

Try to renew it via de CLI (see elsewhere in this topic posted it numerous times). There is a --dry-run or a --force-renew flag for certbot. Then see what errors you are getting.

Just needed to reboot my server to do some electrical work and ofc this is still an issue. Dear Unraid staff: please at least acknowledge this issue!

Yeah, some response would be great, at least so that we know this is being worked on / even known by the devs!