mattie112

You could try to write your config to the appdata folder of the importer to see if that works? The inporter expects a filename but does not get anything (for whatever reason)

Is this the log of the importer or firefly itself? It seems to give an error at `convertConfigFile` so you might want to doublecheck your config.

(not in my Version: 6.9.2) Docker version: 20.10.5 Docker vDisk location: /mnt/user/system/docker/docker.img Default appdata storage location: /mnt/user/appdata/

Yeah I don't know. Any problems with other docker containers? Perhaps remove your entire docker.img? The commands I posted should work (and do work on my Unraid, Windows desktop and Linux desktop). So there must be something with your setup. You could also try some basic containers like alpine or something.

What device do you use for your Unraid? It works fine here: root@Tower:~# docker pull jlesage/nginx-proxy-manager Using default tag: latest latest: Pulling from jlesage/nginx-proxy-manager Digest: sha256:488bd69104c9b88ae6a9f7ee6cb3413f8ec63da118034919616bb462c84f61ed Status: Image is up to date for jlesage/nginx-proxy-manager:latest docker.io/jlesage/nginx-proxy-manager:latest root@Tower:~# docker run -it jlesage/nginx-proxy-manager bash bash-5.1# I know that trying to run a x64 image for example on ARM does not work. But yeah I don't know....

Try something like: docker pull jlesage/nginx-proxy-manager docker run -it jlesage/nginx-proxy-manager bash (and then in the container:) cd / ./init Than you have a 100% clean fresh image/copy with NO mounted directories (so anything you do in here is NOT saved). If this does not work there is something really wrong with your server (or you are using an 32-bit system while NPM is for 64-bit, or ARM or something).

Yeah exactly, if you have a VM that has a different IP so you could host something om 80/443. Or you can also choose to do a different port. (btw you only need port 80, your NPM uses 80/443 but the thing you proxy to just uses http)

You just provide NPM with the IP and port you want to proxy. Doesn't matter if it's the same host or not.

There is a `default-host_access.log` file in the appdata folder for NPM. That is the logfile for the web UI, you could check that.

And what if you dont click on add? So enter the credentials then click save? (or first click add n amount of times to get all the fields you need and then enter details)

Is this with somekind of backup restored? Might be that you have different users now then previously? You can try to delete your NginxProxyManager folders from AppData (but that will delete all your domaints). Or simply rename the folder just to see if it works or not with a clean state.

Good one, it seems https://github.com/paperless-ngx/paperless-ngx was chosen

Can you access your domain externally on port 80? (unsecured http)

Is there perhaps anything in the log regarding the plugin? I know there is an 'plugin-error' directory of some kinds on flash but I don't know if something gets logged.

Hm, I have rebooted my server a couple of weeks ago and I just confirmed that it listed as installed (and working). So at least I don't have issues here. Plugin version: 2021.05.21 Unraid: 6.9.2 (so perhaps there are changes in the 6.10 ?)

Sure, NPM uses a docker volume (/mnt/user/appdata/NginxProxyManager) by default so you can just `cp` files from the Unraid CLI. You need to check the exact folders / locations not 100% sure about that.

I would suggest to get cloudflare out of the equation just to see where the problem might be. I personally don't use cloudflare but I would do something in my pc's host file to force it to your external instead of cloudflare. Assuming windows: C:\Windows\System32\drivers\etc\hosts (or /etc/hosts on linx) Add your.domain.name.tlc 1.2.3.4 where 1.2.3.4 is either your external ip or your internal npm ip (try both) If that works, then cloudflare (connection) is to blame (somehow) if that doesntwork first debug your own setup.

Perhaps your "congratulations" page is cached by Cloudflare? I believe it can do that for static websites. You could for example check the port forwarding on your router, disable that and if the page still loads then you are 100% not serving that page. Also in the commandline you can do "docker ps" to see all containers running, this includes all the ports they listen on so perhaps that might give some insight.

Yes you can use a reverse proxy as Nginx (or the NginxProxyManager docker container). However if you want a SSL certificate you will need to at least expose your proxy to the internet (for letsencrypt to work, self-signed or other certs can work without internet access). You can however add an ACL so only certain IP's can access your container. The communication between your proxy and paperless is indeed unencrypted. You can't really avoid that. There must be some place that decrypts the traffic. However in order to MTM traffic from container A to container B attackers need to have access to your server. And be honest if they have server access why would they care to snoop your data? They can just download the database or something like that. So: I would suggest to try out the NginxProxyManager container, it is listed in the CA appstore

So what exactly is the problem? When using custom certificate you need to supply your own certificate/key. Is that cert not working? Are you unable to upload? You can also get a letsencrypt certificate just to get your stuff working again or is there a reason why you cannot do that?

Can you still access the (sqlite) database? Are the config files and certs still present?

And what about "See the logfile /tmp/tmpy2mllf8d/log or re-run Certbot with -v for more details." ? Or perhaps try running it manually please see a couple of posts back.

Well that looks like certbot does not see any certificates that might be due for renew. So I guess it never created a certificate. Perhaps you can try to manually request a certificate and see if that works? https://www.digitalocean.com/community/tutorials/how-to-use-certbot-standalone-mode-to-retrieve-let-s-encrypt-ssl-certificates-on-ubuntu-16-04 Also make sure you can access unsecured port 80 (for the .well-known directory) from the public internet as that is requried.

Can you try to do it manually? See a couple of posts back, this might give a bit more output. Usually this is somekind of DNS/port forward issue as letsencrypt cannot access your host correctly

So what is the first part that doesn't work. You have a domain and that shows a site from Godaddy? The something is wrong there (or on cloudflare) as it never gets to your NPM. You can also try a website without SSL just to exclude that from your problems.