Ok, that database isn't exposed to the internet, at least.
Go for external 80 to internal 80, and same for 443->443.
3 Likes
The internal port doesn't match what your docker-compose.yml says.
3 Likes
theems to be better now sorry, don't understang well english with the technic
Now can't go to HA with hocishome.duckdns.org
1 Like
ok, I see a 500 error on 80
you might try again (tell npm to use the staging system -- if it can do so)
nginx looks like it's running. I don't know where your HA is running.
3 Likes
Yes, I wasn't clear. I was trying to say you could port-forward it locally to a different port not that you could do an http redirect to one. Thanks.
4 Likes
for some reason nginx proxy manager is serving unencrypted http on port 443. this shouldn't happen.
5 Likes
i'm so lucky ... 
it looks like it's going better.
I get a 400 error but ssl/tls is working fine.
3 Likes
Ok so i found in :
If I put 8080 it goes to zigbee2mqtt, not HA.
HA is on 8123. If I put 8123, doesnt work
are you sure that's running?
3 Likes
for some reason nginx is responding with a 400 error.
I am not sure why.
3 Likes
if i put 8080 on NPM interface it's ok to bring me to port 8080 with zigbee2mqtt, but not with 8123
1 Like
HTTP on IPv4 works:
curl -Ii4 hocishome.duckdns.org
HTTP/1.1 301 Moved Permanently
Server: openresty
Date: Fri, 25 Aug 2023 17:56:59 GMT
Content-Type: text/html
Content-Length: 166
Connection: keep-alive
Location: https://hocishome.duckdns.org/
HTTP on IPv6 fails:
curl -Ii6 hocishome.duckdns.org
curl: (56) Recv failure: Connection reset by peer
3 Likes
What shows?:
netstat -pant | grep -i listen
2 Likes
this !
root@raspberrypi:~# netstat -pant | grep -i listen
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 85193/docker-proxy
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 85235/docker-proxy
tcp 0 0 0.0.0.0:8123 0.0.0.0:* LISTEN 2694/python3
tcp6 0 0 :::443 :::* LISTEN 85199/docker-proxy
tcp6 0 0 :::80 :::* LISTEN 85242/docker-proxy
tcp6 0 0 :::8123 :::* LISTEN 2694/python3
That looks good.
What about within the docker instance?
2 Likes
I restarted nginx docker [nginxproxymanager_db_1] :
Version: '10.4.15-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server
2023-08-25 18:09:57 5 [Warning] Aborted connection 5 to db: 'npm' user: 'npm' host: '172.21.0.2' (Got an error reading communication packets)
2023-08-25 18:09:57 3 [Warning] Aborted connection 3 to db: 'npm' user: 'npm' host: '172.21.0.2' (Got an error reading communication packets)
2023-08-25 18:10:03 0 [Note] /usr/bin/mysqld (initiated by: unknown): Normal shutdown
2023-08-25 18:10:03 0 [Note] Event Scheduler: Purging the queue. 0 events
2023-08-25 18:10:03 0 [Note] /usr/bin/mysqld: Shutdown complete
[i] pre-init.d - processing /scripts/pre-init.d/01_secret-init.sh
[i] mysqld already present, skipping creation
[i] MySQL directory already present, skipping creation
2023-08-25 18:10:04 0 [Note] /usr/bin/mysqld (mysqld 10.4.15-MariaDB) starting as process 1 ...
2023-08-25 18:10:04 0 [Note] Plugin 'InnoDB' is disabled.
2023-08-25 18:10:04 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-08-25 18:10:04 0 [Note] Server socket created on IP: '::'.
2023-08-25 18:10:04 0 [Warning] 'user' entry '@817430e417e6' ignored in --skip-name-resolve mode.
2023-08-25 18:10:04 0 [Warning] 'proxies_priv' entry '@% root@817430e417e6' ignored in --skip-name-resolve mode.
2023-08-25 18:10:04 0 [Note] Reading of all Master_info entries succeeded
2023-08-25 18:10:04 0 [Note] Added new Master_info '' to hash table
2023-08-25 18:10:04 0 [Note] /usr/bin/mysqld: ready for connections.
Version: '10.4.15-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server