mattie112

O wow that is strange, it should fetch https://ip-ranges.amazonaws.com/ip-ranges.json if I'm correct and that URL works fine here. Can you access that URL from your browser?

Open console Then do: And check if anything is "corrupted" in that file. The first number is the line number (your error lists 300 so look around that). You can also delete and reinstall the container if you have only a single site you can easily reconfigure.

You can try to open a shell for that container and then check that file to see what is wrong. Did you create any custom config? Or perhaps a whitelist of IP addresses? Perhaps a typo or something.

Did you try running it manually to see if you get a different error? (see also the other 100 people that found things when running manually perhaps your issue is the same)

Can you access your domain from a remote connection? It seems that it cannot access your domain and then it won't supply a certificate.

So your apps already have SSL? Why do you want NPM then? A bad gateway error is that NPM cannot access your application.

And there is no more logging? Try to run it manually: https://forums.unraid.net/topic/76460-support-djoss-nginx-proxy-manager/page/56/?tab=comments#comment-1000941

You should only forward external ports 80 and 443 to your container. Is what you list the port forward in your router or the container ports? The 8181 port is just for management and should not be forwarded (in my opinion) So: external 80 -> container 1880 external 443 -> container 18443

Please just use the search.... https://forums.unraid.net/search/?q=reset password&quick=1&type=forums_topic&item=76460 But in case you cant find it:

Is this not an setting/issue with nextcloud? Does that have a redirect / force domain option?

There should be an option to redirect traffic to HTTPS ('force https' or something like that). I can't currently check how it is called exactly as I am having some PSU issues so my server is offline

Perhaps /data/letsencrypt-acme-challenge (in the container) ?

No that is not normal, it seems to be in a restart loop. Did you make any custom config? Perhaps a IP list with no entries or something not sure. You can check the config file listed to see what is wrong exactly.

And what if you create a script? Does it execute in that case? Perhaps https://github.com/the-paperless-project/paperless/issues/637 helps?

Did you mount the correct folders (please share a screenshot of your container config). Perhaps you are filling-up your docker image?

Allright, the reason why I am asking is if you can reach your NPM you shoud at least get somekind of error from NPM/nginx (like a gateway timeout). So that is why I am thinking that the problem lies before your NPM. (For example the port-forward in your router). You could try to run https://hub.docker.com/r/hashicorp/http-echo/ on port 80 or 443 to see if you get that output in your browser. Just to eliminate NPM from the testing to make sure where the problem lies.

If you get a "site cannot be reached" it probably not an issue with NPM but with your domain not resolving or your port not forwarded correctly. I assume you go to the NPM control panel through a local IP but your overseer domain resolves to an external IP. So just for sanity: Ping overseer.yourdomain Confirm it matches "whatismyip.com" Check your port forwards are they correct? If it all checks out you can change your hosts file to add something like "192.168.*.* overseer.domain.com" to force your PC to use a local ip. Just to verify NPM works that way. Oh and also check the NPM logs for any errors of course

Hm... what error are you getting exactly? If you can reach NPM (but NPM not overseer) you should get a 502 - gateway timeout. Can you confirm you can reach your NPM? Does your domian resolve correctly, is the 80/443 port forward in your router correct?

Is your NPM container in the same 'proxynet'? If not use 192.168.1.216:5055

Does running 'createsuperuser' again perhaps work? (https://github.com/the-paperless-project/paperless/blob/master/docs/setup.rst)

For reference: 127.0.0.1 IN A container refers to the container itself. So that will only work if you have a single container with for example paperless AND redis.

Yes Simpy forward to ip.of.your.vm:portofyourapp does not need to be on the same host

@Linguafoeda 502 is a problem between NPM and the endpoint. Usally you let NPM handle SSL so: internet -> SSL -> yourdomain -> non-SSL -> your-internal-service (like plex, apache, bitwarden, whatever) Can you share some screenshots? I find it hard to understand exactly what your setup is.

The volumes mounted in your Docker container so the details/config in the Docker tab

You can "print" your email to PDF and then store it. Perhaps the most simple solution for a few reciepts?