as stated on the other forum post, if you go with a proxy software, you need to disable https on your web server hosting nextcloud and you need to change away from port 80 to 81. Your proxy will handle ssl and forward all request to nextcloud. usually it is not needed to have ssl active on any of your apps as all this should be handled by the proxy. Only thing you might need to check of your apps are able to work an a sub folder like
This way you would need a single certificate only. Usually your apps should have a wiki where it should describe how to use sub folder. Another option is to use sub domains. Something like this
You could mix it as well. All depends on your apps and how you could configure them
Hi, Joulinar I think You’re the only one who can help me
Please don’t be mad.
I disable https on my Dietpi:
lighttpd-disable-mod dietpi-https dietpi-hsts dietpi-https_redirect
I uninstall certbot.
I forward ports on router like this:
external port: host/IP internal port: protocol:
80-80 192.168.0.19 8080-8080 TCP
443-443 192.168.0.19 4443-4443 TCP
I install Nginx Proxy Manager like this:
I change port for zigbee2mqtt:
I install Petio:
I remove also from my
that /nextcloud :
'overwrite.cli.url' => 'https://myserver.ddns.net/nextcloud',
The strange situation is my Nextcloud works now on SSL but other apps don’t.
Can You help me with that?
you would need to create a proxy definition for each application in NPM
Thanks, I also get some info that I need to make New Proxy Host for every app in NPM. I need to make subdomains on no-ip for every app like:
you can use sub folder as well on NPM. See my PM. Just search the web on how to use sub folder
But I get info from Home Assistant suppport that I cannot use subfolders for that
in this case you need to use sub domain for HA application
How to manage additional sub domain, maybe contact NoIP directly.
sorry for the necro-bump, but I wanted to give my docker/nginx proxy manager an update now after a year of running good. how to do that and keep the settings?
I am stuck here and noticed that even portainer is old and wants to update.
Not sure how you setup NPM in first place but having a look to vendor docs might give an idea Upgrading | Nginx Proxy Manager at least if you used
I think I followed that tutorial back then to install it. the upgrading command gives me this:
What exactly you are trying to do? These are 2 different errors.
Did you try to install portainer or reinstall?
And docker-compose needs to be executed within the directory where you compose configuration file is located.
Joulinar saved me again. I updated both containers successfully now. Removed portainer using “dietpi-software” and reinstalled it again. That brought portainer to the latest version. Then I could update the NPM container using portainer.
Usually a simple
dietpi-software reinstall <App ID> should have been sufficient to update portainer.
I would also recommend installing watchtower for docker…keep the containers updated with the latest builds automatically
centurylink/watchtower - Docker Image | Docker Hub
that gave me the blue error seen above. it worked manually though.
Originally, did you installed Portainer using