After possible update Apache no more reachable #5291
Answered
by
alessandriniluca
alessandriniluca
asked this question in
Questions
-
|
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 ProblemMy 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. SetupThe setup comprises: 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 containerTo 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: MastercontainerTo 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: Caddythrough `journalctl -u cady --since today', logs from last caddy restart: Other tests:
So I am assuming the URL correctly redirects to it. Could it be possibly related to #5269?
|
Beta Was this translation helpful? Give feedback.
Answered by
alessandriniluca
Oct 25, 2024
Replies: 1 comment 17 replies
-
okay this proff thst AIO works correctly.
This looks like a bug in your your network or reverse proxy then (outside aio) |
Beta Was this translation helpful? Give feedback.
17 replies
-
|
No, there is no additional config needed. Have you already tried to do |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot again for your patience. |
Beta Was this translation helpful? Give feedback.
-
|
If your reverse peoxy uses the http acme challenge you also need port 80. but yes the mentioned ports should be sufficient |
Beta Was this translation helpful? Give feedback.
-
|
I solved it, thanks for the patience, and apologize for the inconvenience. |
Beta Was this translation helpful? Give feedback.
Answer selected by
alessandriniluca
-
|
Great that you figured it out :) |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I solved it, thanks for the patience, and apologize for the inconvenience.
After having excluded all the variables, I called the service provider of my internet connection, they actually told me they reserved port 443 some weeks ago for their needs. They activated it back, and everything re-started working normally.