new docker setup doesnt work

[ranrinc]

Shlink version

stable

PHP version

n/a

How do you serve Shlink

Docker image

Database engine

MariaDB

Database version

10.11

Current behavior

Running Debian 12 with the latest docker

all the docker container seems to be workin and no error seems to be shown.

However calling the IP:8080 seems to hit 404 pages and IP:8000 doesnt to find the pages at all. Any idea?

Expected behavior

I expect the system run as shown in many videos.

Minimum steps to reproduce

Setup Debian 12.

Setup Dockers.

Create the docker-compose.yml

services:
  # 1. The Database (MariaDB is standard for Shlink)
  db:
    image: mariadb:10.11
    container_name: shlink-db
    restart: always
    environment:
      - MARIADB_ROOT_PASSWORD=password123
      - MARIADB_DATABASE=shlink
      - MARIADB_USER=shlink_user
      - MARIADB_PASSWORD=shlink_pass
    volumes:
      - ./shlink_db:/var/lib/mysql

  # 2. The Shlink Engine (The "Brain")
  shlink:
    image: shlinkio/shlink:stable
    container_name: shlink-server
    restart: always
    depends_on:
      - db
    environment:
      - DB_DRIVER=mariadb
      - DB_NAME=shlink
      - DB_USER=shlink_user
      - DB_PASSWORD=shlink_pass
      - DB_HOST=db
      - DEFAULT_DOMAIN=192.168.80.204:8181  # Your Server IP and Engine Port
      - IS_HTTPS_ENABLED=false
      - INITIAL_API_KEY=my_secret_api_key    # This sets your key automatically!
    ports:
      - "8080:8080"

  # 3. The Web Dashboard (The "Face")
  shlink-web-client:
    image: shlinkio/shlink-web-client:stable
    container_name: shlink-web-ui
    restart: always
    ports:
      - "8000:80"

run docker compose up -d

[acelaya]

There's a couple problems there:

1. Shlink Web Client does not expose port 80, but 8080, so you need to map 8000:8080 not 8000:80.
2. You are visiting 192.168.80.204:8080, when it should be 192.168.80.204:8181, since that's the port you exposed externally.
3. The 404 when visiting Shlink's base path is the expected behavior. You can change that to configure a base_path special redirect instead, but there's nothing to show there by default.