Apache Container ignoring environment variable APACHE_PORT #604
-
Still have an issue with the apache container, all else is working ... Setup works fine, all containers running. However when I navigate to the webpage https://nextcloud.mydomain.com I get a 502 error. This makes sense upon examing the logfiles from the apache container, I have several entries like so: (13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80 Port 80 is not available in my setup, and I have set APACHE_PORT=11000. |
Beta Was this translation helpful? Give feedback.
Replies: 11 comments 46 replies
-
Hello, can you post the output of |
Beta Was this translation helpful? Give feedback.
-
sh-4.4$ docker inspect nextcloud-aio-domaincheck |
Beta Was this translation helpful? Give feedback.
-
sh-4.4$ netstat -plnt |
Beta Was this translation helpful? Give feedback.
-
nextcloud-aio-mastercontainer: |
Beta Was this translation helpful? Give feedback.
-
sh-4.4$ cat traefik2/rules/nextcloud.toml [http.services] |
Beta Was this translation helpful? Give feedback.
-
Docker logs from apache container: Executing task: docker logs --tail 1000 -f 07a994846e06d76d97adc303e535c7aa306a78ca19899370ab08b5f6dc1b6472 < nc: getaddrinfo for host "nextcloud-aio-nextcloud" port 9000: No address associated with hostname |
Beta Was this translation helpful? Give feedback.
-
I see. Thanks for the logs! they are helpful! We just released a new beta update. Please try that and report back if it fixes the problem! (there were some improvements to the apache container so it might be already fixed) |
Beta Was this translation helpful? Give feedback.
-
I don’t think so but I will check. It’s running on a Synology FWIW.
…
On May 9, 2022 at 2:21 PM, <Simon L. ***@***.***)> wrote:
After thinking about thid a bit more, it is pretty likely that selinux is indeed blocking apache insidw the container from starting. But I guess we'll see if you actually have selinux installed and enabled
—
Reply to this email directly, view it on GitHub (#604 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/ALKJUX5PH67PXUZTC7N7XBDVJFJUNANCNFSM5VOXDPCQ).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Also, I have a number of nginx containers running without issue on the same host, but this is the only Apache container.
…
On May 9, 2022 at 2:21 PM, <Simon L. ***@***.***)> wrote:
After thinking about thid a bit more, it is pretty likely that selinux is indeed blocking apache insidw the container from starting. But I guess we'll see if you actually have selinux installed and enabled
—
Reply to this email directly, view it on GitHub (#604 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/ALKJUX5PH67PXUZTC7N7XBDVJFJUNANCNFSM5VOXDPCQ).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@robotictacos another idea:
|
Beta Was this translation helpful? Give feedback.
-
Also here is the netstat I think you wanted me to run earlier? (sorry was at doc appointment) sh-4.4$ docker exec --user root -it nextcloud-aio-apache bash apt update | bash install net-tools | netstat -tulpn | grep 80 |
Beta Was this translation helpful? Give feedback.
I see. Thanks for the logs! they are helpful!
We just released a new beta update. Please try that and report back if it fixes the problem! (there were some improvements to the apache container so it might be already fixed)
See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel