version: '3.8'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '443:443'
- '81:81'
environment:
PUID: 1001
PGID: 100
X_FRAME_OPTIONS: "sameorigin"
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencryptthat's the code i uesed
that's the code i uesed
ok, that should work if your user 1001 has sufficient permissions and ports 80, 443 and 81 are available. Those are the checks you should do.
If everything is in order, access the npm GUI on port 81.
"Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker compose --file '/srv/dev-disk-by-uuid-66a94461-19db-4367-8d1f-d5ee373d1cea/Docker/npm/npm.yml' --env-file '/srv/dev-disk-by-uuid-66a94461-19db-4367-8d1f-d5ee373d1cea/Docker/npm/npm.env' --env-file '/srv/dev-disk-by-uuid-66a94461-19db-4367-8d1f-d5ee373d1cea/Docker/global.env' up -d 2>&1': Container npm-app-1 Starting
Error response from daemon: driver failed programming external connectivity on endpoint npm-app-1 (b2fe71035a2014c441552a3a8de6a8f8dbbc0a2ad58d1ce42ccc991bd0b04da9): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use"
getting this error
listen tcp4 0.0.0.0:443: bind: address already in use
As I already told you, you must find out what or who is occupying port 443. As long as that port is busy you will not be able to start that container.
Check the OMV GUI and the rest of the containers or any other service that may have that port busy.
i tried to check, can not find, is there any window command or omv command to find out
i tried to check, can not find, is there any window command or omv command to find out
What addons/Docker containers do you use
Look in the GUI in System>Workbench. If the GUI is using it change it from there.
Stop all containers you have running. Try starting npm. If it starts it is one of the ones you have.
Look in the GUI in System>Workbench. If the GUI is using it change it from there.
Stop all containers you have running. Try starting npm. If it starts it is one of the ones you have.
thanks, it omv
what is recommended port for this please
i disabled ssl, now it says port 80 in use
i disabled ssl, now it says port 80 in use
Change 80 to 88 or any other none in use port than try what you did before again.
NGINX PROXY MANAGER, its up.
One less thing.
No getting this error
No getting this error
What are you talking about? What's that?
after installing npm, trying to configure, npm to divert traffic to nextcloud. I was following the instruction on the images
manged it to work, if using duckdns, need to tick dns challenge and enter duckdns token
Hi,
I have managed to install and run the nextcloud.
I have added data directory as below:
- NEXTCLOUD_DATADIR=/srv/dev-disk-by-uuid-66a94461-19db-4367-8d1f-d5ee373d1cea/Docker/nextcloud_data
I have another hard drive remote mounted, I wanted to add it as data drive, I added up below line:
environment:
- APACHE_PORT=11000
- NEXTCLOUD_DATADIR=/srv/dev-disk-by-uuid-66a94461-19db-4367-8d1f-d5ee373d1cea/Docker/nextcloud_data
- NEXTCLOUD_DATADIR=/srv/remotemount/data/nextcloud_data
is it the right way, becuase the 2nd drive is not showing up. Please advise.
Thanks
Display MoreI have another hard drive remote mounted, I wanted to add it as data drive, I added up below line:
environment:- APACHE_PORT=11000
- NEXTCLOUD_DATADIR=/srv/dev-disk-by-uuid-66a94461-19db-4367-8d1f-d5ee373d1cea/Docker/nextcloud_data
- NEXTCLOUD_DATADIR=/srv/remotemount/data/nextcloud_data
is it the right way, becuase the 2nd drive is not showing up. Please advise.
It does not work like that. Read here how to do it. https://github.com/nextcloud/all-in-one
Don’t have an account yet? Register yourself now and be a part of our community!
