szaimen
commented
12 hours ago
- From the caddy VM,
wget <LOCAL_IP_AIO_VM>:11000returns a page,
okay this proff thst AIO works correctly.
- Outside from the local network, on my laptop from the internet,
wget <PUBLIC_URL_NEXTCLOUD>hangs on:--2024-09-18 17:58:18-- <PUBLIC_URL_NEXTCLOUD> Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt' Resolving <PUBLIC_URL_NEXTCLOUD> (<PUBLIC_URL_NEXTCLOUD>)... <STATIC_PUBLIC_ROUTER_IP> Connecting to <PUBLIC_URL_NEXTCLOUD> (<PUBLIC_URL_NEXTCLOUD>)|<STATIC_PUBLIC_ROUTER_IP
This looks like a bug in your your network or reverse proxy then (outside aio)
Hi to everyone, I would like first to apologize for the disturbance, but from a day I noticed a problem I am not able to solve
Problem
My AIO setup worked without problems for almost a year. After what I think was an auto update a couple of days ago (3 or 4, while I was not at home during the weekend and did not access nc), I can no more reach the apache container. Neither caddy, nor NC (apache container / mastercontainer) shows suspicious logs, except for the logs in the mastercontainer which returns some "404". In the following everything (tests I did and log I got) is reported, if more things are needed, I'll be glad to provide more information. Apologize If I did not open an issue immediately, but first I wanted to ensure it was not a problem on my side.
Setup
The setup comprises: a VM running caddy a VM running AIO
Both in the same local network (2 VMs of a proxmox machine)
Port forwarding from the router is enabled, and the public URL correctly points to the static public IP of the network. It has worked correctly for a year, I already rebooted everything included the router.
Caddyfile set up according to the guide for reverse proxies
Stack on portainer for nextcloud aio:
Router forwards the URL chosen for nextcloud to the local IP of the Caddy VM.
Logs:
Apache container
To be able to access the AIO container and see logs, I stopped from bash the apache container, opened aio interface, stopped all containers and restarted. Logs:
Mastercontainer
To be able to access the AIO container and see logs, I stopped from bash the apache container, opened aio interface, stopped all containers and restarted. Logs:
Caddy
through `journalctl -u cady --since today', logs from last caddy restart:
Other tests:
wget <LOCAL_IP_AIO_VM>:11000returns a page,wget <PUBLIC_URL_NEXTCLOUD>hangs on:So I am assuming the URL correctly redirects to it. Could it be possibly related to https://github.com/nextcloud/all-in-one/issues/5269?
netstatisTIME_WAITfor everything inside the apache container.