Dont see apache port

[Jory_S]

When setting up the nextcloud docker container i noticed that i dont see the apache port that i left on the standard port which is 11000 with netstat -tulpn on either the docker image or the pi host, what could cause this. This is my docker-compose.yml for nextcloud. I also tried to reset the docker container with GitHub - nextcloud/all-in-one: The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance. which did not work unfortunately. Would really appreciate if someone can help me

nextcloud:
image: nextcloud/all-in-one:latest
restart: unless-stopped
container_name: nextcloud-aio-mastercontainer
ports:
- “8080:8080”
environment:
- APACHE_PORT=11000
- APACHE_IP_BINDING=127.0.0.1
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config
- /var/run/docker.sock:/var/run/docker.sock:ro
depends_on:
- caddy

volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer

[jtr]

• What do the Docker logs indicate from your nexdtcloud-aio-mastercontainer container? Did it start up okay?
• Are you able to access the AIO interface?[1]

I also tried to reset the docker container with GitHub - nextcloud/all-in-one: The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance. which did not work unfortunately.

Can you elaborate on “did not work”?

[1] all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub

[CloudyFH]

Hi @Jory_S

seems we’re having a similar issue.

Please check my post:

AIO - connect to apache in mastercontainer

Hello everybody, APACHE_PORT is 11000. I’ve tried both setting APACHE_IP_BINDING to 127.0.0.1 or 0.0.0.0 The AIO mastercontainer seems not being able to connect to the apache container through localhost or 127.0.0.1. But my host PC is able to connect. In my Caddyfile, I have tried these: reverse_proxy localhost:{$APACHE_PORT} or reverse_proxy 127.0.0.1:{$APACHE_PORT} both with no success. Running nc -z localhost 11000; echo $? in the AIO mastercontainer, returns 1 (=failed). Running t…

I’m using " nextcloud-aio-apache" as “host name” to connect from mastercontainer to apache, and it works (see bottom of post #1). That may help you eventually.

reverse_proxy nextcloud-aio-apache:{$APACHE_PORT}

I don’t know if such an approach is ok, hope someone can elaborate.

[Jory_S]

The docker logs for the nextcloud docker container seems to have startup correctly. I am not home right now but ssh with portforwarding either port 80 or 8443 does not work. I dont see 80 or 8443 for nextcloud on the pi itself when running ss -tulpn, however i do see it in the docker container itself.

/var/www/docker-aio # netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      105/httpd
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      105/httpd
tcp        0      0 127.0.0.1:9876          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:2019          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.11:32891        0.0.0.0:*               LISTEN      -
tcp        0      0 :::9000                 :::*                    LISTEN      111/php-fpm.conf)
tcp        0      0 :::80                   :::*                    LISTEN      -
tcp        0      0 :::8443                 :::*                    LISTEN      -
udp        0      0 127.0.0.11:54377        0.0.0.0:*                           -

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
{"level":"info","ts":1707213915.8289025,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""}
[06-Feb-2024 10:05:16] NOTICE: fpm is running, pid 111
[06-Feb-2024 10:05:16] NOTICE: ready to handle connections
[Tue Feb 06 10:05:16.419054 2024] [mpm_event:notice] [pid 105:tid 281473796702304] AH00489: Apache/2.4.58 (Unix) OpenSSL/3.1.4 configured -- resuming normal operations
[Tue Feb 06 10:05:16.419285 2024] [core:notice] [pid 105:tid 281473796702304] AH00094: Command line: 'httpd -D FOREGROUND'
Total reclaimed space: 0B

[Jory_S]

Okay so i also tried @CloudyFH solution which also did not work for me when setting either the host name or with the ip and same for {$APACHE_PORT}
or the actual port which is 11000 in my case. And with did not work i mean when i try to go to the url i only get a blank screen. If i try to forward the port 8080 i get

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
 Instead use the HTTPS scheme to access this URL, please.<br />
</p>
<hr>
<address>Apache/2.4.58 (Unix) Server at localhost Port 8080</address>
</body></html>

[CloudyFH]

Did you try this:

reverse_proxy host.docker.internal:{$APACHE_PORT}

Try checking “1. Configure the reverse proxy” point 3), “on same server” resp. “on different server” to match exactly your setup here: all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub

You may post your full compose.yaml and Caddyfile for an exact view on your setup.

You may add

{
   debug
}

on top of your Caddyfile, to get full logs.

And you may use the “curl” command to check the connections, instead of a browser, to get more specific output. Clear the docker logs before each connection check to get only the related ones.