Pydio-cells don't read mariadb in swag network

First of all, I am sorry for my poor English.

I succeeded in creating a container following a document on linuxserver.io to run the pydio-cells on the swag network.
But, during database configuration, pydio-cells failed to read mariadb and could no longer proceed with the installation process.
I tried similar things to the nextcloud installation method, but it was still unsuccessful.
I couldn’t find a log to refer to, so I couldn’t solve it by myself.

Ubuntu 18.04 LTS + Docker lastest version
Pydio-cells is applying swag reverse proxy.
Both mairadb container and pydio-cells container are connected to the swag network.

Here is the docker-compose docs used to create the container.
If there is a log that I can provide, I will.

mariadb docker-compose

---
version: "2"
services:
  mariadb:
    image: linuxserver/mariadb
    container_name: mariadb
    environment:
      - PUID=1000
      - PGID=1000
      - MYSQL_ROOT_PASSWORD=****
      - TZ=Asia/Seoul
      - MYSQL_DATABASE=pydio
      - MYSQL_USER=yapuro
      - MYSQL_PASSWORD=****
    volumes:
      - /home/yapuro/docker/mariadb:/config
    ports:
      - 3306:3306
    restart: unless-stopped

pydio-cells docker-compose

---
version: "2.1"
services:
  pydio-cells:
    image: ghcr.io/linuxserver/pydio-cells
    container_name: pydio-cells
    hostname: pydio-cells
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Asia/Seoul
      - EXTERNALURL=https://yapu.kr
    volumes:
      - /home/yapuro/docker/pydio-cells:/config
    ports:
      - 8080:8080
      - 33060:33060 #optional
    restart: unless-stopped

It looks like they are in two separate compose yaml files, which means they are not in the same custom bridge network, therefore, pydio-cells cannot reach the mariadb container via address mariadb

Put them in the same compose yaml file so they can reach each other via container name as dns hostname

https://docs.linuxserver.io/general/docker-compose#multiple-service-usage

1 Like

Thank you for your response.

I rewritten the docker-compose yaml file following your solution.

---
version: "2.1"
services:
  pydio-cells:
    image: ghcr.io/linuxserver/pydio-cells
    container_name: pydio-cells
    hostname: pydio-cells
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Asia/Seoul
      - EXTERNALURL=https://yapu.kr
    volumes:
      - /home/yapuro/docker/pydio-cells:/config
      - /data:/data
    ports:
      - 8080:8080
      - 33060:33060
    depends_on:
      - mariadb
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb
    container_name: mariadb
    environment:
      - PUID=1000
      - PGID=1000
      - MYSQL_ROOT_PASSWORD=****
      - TZ=Asia/Seoul
      - MYSQL_DATABASE=pydio
      - MYSQL_USER=yapuro
      - MYSQL_PASSWORD=****
    volumes:
      - /home/yapuro/docker/mariadb:/config
    ports:
      - 3306:3306
    restart: unless-stopped
  swag:
    image: linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Asia/Seoul
      - URL=yapu.kr
      - SUBDOMAINS=wildcard
      - VALIDATION=dns
      - EXTRA_DOMAINS=*.yapu.kr
      - DNSPLUGIN=cloudflare
      - EMAIL=****
      - DHLEVEL=2048
      - ONLY_SUBDOMAINS=true
      - STAGING=false
    volumes:
      - /home/yapuro/docker/swag:/config
    ports:
      - 443:443
      - 80:80
    restart: unless-stopped

and connected the 3 containers to the same network.
So I passed the DB configuration. Thank you!

But I can’t access the web ui after the installation is complete.

Here is pydio-cells container log after successful installation
https://pastebin.com/EZnFjBDN

The same error occurs when connecting to IP:PORT and domain with swag reverse proxy.

Thank you very much for your help.

Pydio cells is very picky about how you’re accessing it.

If you set the external url to your domain, you’ll have to access at https://yapu.kr exactly. If you’re reverse proxying at a subdomain, you need to set the external url in pydio cells to the subdomains address.

Don’t access at port 8080 when using the donation as that’s not going through the reverse proxy

1 Like

Thank you! Everything is solved.

The “EXTERNALURL” value was followed by the address stored in the “reverse proxy conf” and consequently the main screen access was successful.

Thank you very much for your help :laughing:

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.