Host 127.0.0.1 was not connected to because it violates local access rules

[irjb]

Im trying to have an installation compose file:

version: "3.8"

services:
  db:
    image: mariadb:10.6
    restart: always
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
    volumes:
      - ./db:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=1234
      - MYSQL_PASSWORD=1234
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
  app:
    image: nextcloud:fpm
    restart: always
    volumes:
      - ./nextcloud:/var/www/html
    environment:
      - MYSQL_PASSWORD=1234
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=db
  static:
    image: nginx
    restart: always
    ports:
      - 8080:80
      - 8443:443
    volumes:
      - ./nginx:/etc/nginx/
      - ./nextcloud:/var/www/html:ro
  php:
    build:
      dockerfile: ./php.Dockerfile
    volumes:
      - ./nextcloud:/var/www/html

Im having an http 500 after installing it. I have this message displayed:

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

and the logs shows: “Host 127.0.0.1 was not connected to because it violates local access rules”

How can I proceed to debug this error and get the installation done?

PD: I have already tried to add the config: ‘allow_local_remote_servers’ => true,
without success.

Any help appreciated

[wwe]

hi @irjb welcome to the forum

I would recommend you start from official Docker .examples and add complexity like custom dockerfiles later once you understand what you are doing.

@irjb

PD: I have already tried to add the config: ‘allow_local_remote_servers’ => true,
without success.

sometimes config files get overwritten when you run docker-compose down/up - please double check your config was applied right…

[irjb]

thx for having me.

Examples are way too complicated

I have both of my instances, nextcloud and collabora running with a wildcard ssl cert, both answering HTTPS.

I cant make them connect since settings/admin/richdocuments expects to query the server before saving the URL but collabora runs behind a proxy, outside the internal compose network so it can check for availability even though the wss connection and everything works against the user browser (OUTSIDE OF THE NETWORK)

this is bad

[irjb]

this is my docker-compose file

version: "3.8"
services:
  proxy:
    image: "jc21/nginx-proxy-manager:latest"
    restart: unless-stopped
    ports:
      - "80:80"
      - "81:81"
      - "443:443"
    volumes:
      - ./npmdata:/data
      - ./letsencrypt:/etc/letsencrypt
  app:
    image: nextcloud
    restart: always
    expose:
      - "80"
    volumes:
      - ./nextcloud:/var/www/html
  datab:
    image: mariadb
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: 1234
      MYSQL_PASSWORD: 1234
      MYSQL_DATABASE: nextcloud
      MYSQL_USER: nextcloud
    volumes:
      - ./mysqldir:/var/lib/mysql
  editor:
    image: collabora/code
    restart: unless-stopped
    environment:
      extra_params: "--o:ssl.enable=false"

both apps are available behind a proxy.

But the program expects these URLs to be available inside and outside the private docker network

[irjb]

proof:

[wwe]

@irjb

But the program expects these URLs to be available inside and outside the private docker network

this is exactly how the protocol works. take a look at

Nextcloud Collabora integration