Nextcloud AIO keeps going to the AIO setup/container overview (even without the reverse proxy)

Hi! I deployed a fresh install of Ubuntu 22.04 with docker and installed NextCloud AIO 5.0.0 behind a reverse proxy, but with the skip domain validation turned on, because it was telling me it was a self-signed certificate, which is not true…
Anyway, after the installation was finished i pressed the Open Nextcloud button, but it keeps sending/redirecting me to the /containers.

The button: https://i.imgur.com/WwXewQL.png
Sends me to : https://i.imgur.com/IeRdaEj.png

Im expecting it sends me to the ‘normal’ Nextcloud login page. Not the AIO one.
Also with the internal IP address its the same issue/behavior.

I followed the documentation on Github.
Anyone who has experience with this redirection issue? Or are there some logs needed?

Kind regards,
Robin

Hi, see all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub

I did… like i said in my post, also without the reverse proxy the issue is there.
I think the issue is that my reverse proxy doesn’t run on the same host. I got a central reverse proxy running.

The outcome of: nc -z localhost 11000; echo $?
Is also 0, even if i use the internal ip, its also 0.

In the logging i also see:
“{“level”:“info”,“ts”:1683628898.3584466,“msg”:“using provided configuration”,“config_file”:”/Caddyfile",“config_adapter”:“”}"

But i dont use Caddy… not on this host or as a reverse proxy somewhere else.

It keeps crying that the certificate is bad/self-signed. But it isnt…
2023-05-09T11:20:58.679429989Z [2023-05-09 13:20:58.679173 +02:00] ERROR [notify_push] src/main.rs:77: Self test failed: Error while communicating with nextcloud instance

2023-05-09T11:20:58.712593984Z [09-May-2023 13:20:58] NOTICE: fpm is running, pid 382

2023-05-09T11:20:58.712610155Z [09-May-2023 13:20:58] NOTICE: ready to handle connections

2023-05-09T11:21:08.674687949Z Activating collabora config…

2023-05-09T11:21:09.039683867Z Failed to activate any config changes

2023-05-09T11:21:09.039704348Z cURL error 60: SSL certificate problem: self signed certificate (see libcurl - Error Codes) for https://<URL/hosting/discovery

Can you post the docker run command or docker-compose file here that you used to create the mastercontainer?

Sure, here it is.

version: "3.8"

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer # This line is not allowed to be changed as otherwise the built-in backup solution will not work

services:
  nextcloud:
    image: nextcloud/all-in-one:latest
    restart: always
    container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work
      - /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don't forget to also set 'WATCHTOWER_DOCKER_SOCKET_PATH'!
    ports:
      - "8080:8080"
    environment: # Is needed when using any of the options below
#       - AIO_DISABLE_BACKUP_SECTION=false # Setting this to true allows to hide the backup section in the AIO interface.
      - APACHE_PORT=11000 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      - APACHE_IP_BINDING=0.0.0.0 # Should be set when running behind a web server or reverse proxy (like Apache, Nginx and else) that is running on the same host. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      # - COLLABORA_SECCOMP_DISABLED=false # Setting this to true allows to disable Collabora's Seccomp feature. See https://github.com/nextcloud/all-in-one#how-to-disable-collaboras-seccomp-feature
      - NEXTCLOUD_DATADIR=/mnt/ncdata # Allows to set the host directory for Nextcloud's datadir. See https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir
      # - NEXTCLOUD_MOUNT=/mnt/ # Allows the Nextcloud container to access the chosen directory on the host. See https://github.com/nextcloud/all-in-one#how-to-allow-the-nextcloud-container-to-access-directories-on-the-host
      - NEXTCLOUD_UPLOAD_LIMIT=500G # Can be adjusted if you need more. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-upload-limit-for-nextcloud
      - NEXTCLOUD_MAX_TIME=84600 # Can be adjusted if you need more. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-max-execution-time-for-nextcloud
      - NEXTCLOUD_MEMORY_LIMIT=512M # Can be adjusted if you need more. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-php-memory-limit-for-nextcloud
      #- NEXTCLOUD_TRUSTED_CACERTS_DIR=/path/to/my/cacerts # CA certificates in this directory will be trusted by the OS of the nexcloud container (Useful e.g. for LDAPS) See See https://github.com/nextcloud/all-in-one#how-to-trust-user-defiend-certification-authorities-ca
      #- NEXTCLOUD_STARTUP_APPS=deck twofactor_totp tasks calendar contacts # Allows to modify the Nextcloud apps that are installed on starting AIO the first time. See https://github.com/nextcloud/all-in-one#how-to-change-the-nextcloud-apps-that-are-installed-on-the-first-startup
      - NEXTCLOUD_ADDITIONAL_APKS=imagemagick # This allows to add additional packages to the Nextcloud container permanently. Default is imagemagick but can be overwritten by modifying this value. See https://github.com/nextcloud/all-in-one#how-to-add-os-packages-permanently-to-the-nextcloud-container
      - NEXTCLOUD_ADDITIONAL_PHP_EXTENSIONS=imagick # This allows to add additional php extensions to the Nextcloud container permanently. Default is imagick but can be overwritten by modifying this value. See https://github.com/nextcloud/all-in-one#how-to-add-php-extensions-permanently-to-the-nextcloud-container
      # - NEXTCLOUD_ENABLE_DRI_DEVICE=true # This allows to enable the /dev/dri device in the Nextcloud container which is needed for hardware-transcoding. See https://github.com/nextcloud/all-in-one#how-to-enable-hardware-transcoding-for-nextcloud
      - TALK_PORT=3478 # This allows to adjust the port that the talk container is using.
      # - WATCHTOWER_DOCKER_SOCKET_PATH=/var/run/docker.sock # Needs to be specified if the docker socket on the host is not located in the default '/var/run/docker.sock'. Otherwise mastercontainer updates will fail. For macos it needs to be '/var/run/docker.sock'
      - SKIP_DOMAIN_VALIDATION=true
 #   networks: # Is needed when you want to create the nextcloud-aio network with ipv6-support using this file, see the network config at the bottom of the file
 #      - nextcloud-aio # Is needed when you want to create the nextcloud-aio network with ipv6-support using this file, see the network config at the bottom of the file

# # Optional: If you need ipv6, follow step 1 and 2 of https://github.com/nextcloud/all-in-one/blob/main/docker-ipv6-support.md first and then uncomment the below config in order to activate ipv6 for the internal nextcloud-aio network.
# # Please make sure to uncomment also the networking lines of the mastercontainer above in order to actually create the network with docker-compose
# # Inspired by https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml
# networks:
#   nextcloud-aio:
#     name: nextcloud-aio # This line is not allowed to be changed as otherwise the created network will not be used by the other containers of AIO
#     driver: bridge
#     enable_ipv6: true
#     ipam:
#       driver: default
#       config:
#         - subnet: fd12:3456:789a:2::/64 # IPv6 subnet to use

This is the CURL error code: CURLE_PEER_FAILED_VERIFICATION (60)
The remote server’s SSL certificate or SSH fingerprint was deemed not OK. This error code has been unified with CURLE_SSL_CACERT since 7.62.0. Its previous value was 51.

On https://www.ssllabs.com/ i get a A+ on my domain.

I see and you pointed your reverse proxy at http://ip.address.of.docker.host:11000 ?

Hi,

No to, :8080. 11000 doesnt work, then i get a 502 error.

But http://ip.address.of.docker.host:11000 is correct as written in the documentation. Note http vs https…

My issue was NAT Reflection in my firewall. It was Disabled for the network the docker host was in, Looks like its working now, now the performance tests can begin.