Reverse proxy on different ip: admin cant login


I am upgrading my nextcloud 16xx to this latest version. I am installing fresh.

I have a reverse proxy on another server using this:

server { #port 80 redirection to 443
    listen 80 ;
    location / {
       # return 301 https://$host$request_uri;

nginx of course. I have no tls working at the moment, since I am locally installing and not in production yet.

After a long search through all the confusing documentation I have this docker-compose working:

version: "3.9"

    name: nextcloud_aio_mastercontainer # This line is not allowed to be changed

    image: nextcloud/all-in-one:latest
    restart: "no"
    container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - 8080:8080 # admin web interface
      - APACHE_PORT=11000
      - TALK_PORT=3478

Now the above configuation is strange, since the traffic should flow from:

client -----> http:url:80 reverseproxy —> ip:11000

But the exposed ports of the docker container are 8080. Is there an overview somewhere of the traffic flow that is supposed to happen between the containers?

Anyway, I can successfully go to

But it does not accept the admin password. Does this have to do with the reverse proxy not using TLS?

The 8080 port of the host itsself with the domainname also gives an login window, that refuses the admin password

and since the docker containers do not log errors there is nowhere to go

Hi, can you follow all-in-one/ at main · nextcloud/all-in-one · GitHub?

There is no drawing available but if you are able to read docker-compose, there is this: all-in-one/manual-install/latest.yml at main · nextcloud/all-in-one · GitHub

will the admin login work if the reverse proxy before it has no tls?

did you follow the guide and what is the outcome? any question errors and logs?

Please answer the questions and exactly describe the issue if you are looking for help.

1 Like

Hi, does this answer your question?

Also see GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

1 Like

Okay then let me answer with more words: AIO requires https and a valid certificate.

Sorry but I hoped that the links I’ve send were clear enough in that regard but maybe they are not. So apparently something to improve.

1 Like

There are multiple Docker images. AIO is meant to be a turnkey deployment.

You might be looking for the micro-services Docker image if you’re looking for flexibility with regards to how you integrate into your network/host topology.

P.S. Alternatively, for AIO, it sounds a bit like the Local Instance instructions would a possible approach for your situation.


I have made a drawing of the working configuration in a mindmap now, So you can add a visual documentation howto make a remote reverse proxy work

1 Like

I did not know that, thank you