• Posts

  • Joined

  • Last visited

  • Days Won


mattie112 last won the day on July 18

mattie112 had the most liked content!

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mattie112's Achievements


Explorer (4/14)



  1. Is this not an setting/issue with nextcloud? Does that have a redirect / force domain option?
  2. 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
  3. Perhaps /data/letsencrypt-acme-challenge (in the container) ?
  4. 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.
  5. And what if you create a script? Does it execute in that case? Perhaps helps?
  6. Did you mount the correct folders (please share a screenshot of your container config). Perhaps you are filling-up your docker image?
  7. 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 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.
  8. 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 "" Check your port forwards are they correct? If it all checks out you can change your hosts file to add something like "192.168.*.*" 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
  9. 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?
  10. Is your NPM container in the same 'proxynet'? If not use
  11. Does running 'createsuperuser' again perhaps work? (
  12. For reference: 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.
  13. Yes Simpy forward to ip.of.your.vm:portofyourapp does not need to be on the same host
  14. @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.
  15. The volumes mounted in your Docker container so the details/config in the Docker tab