Having trouble running LinkAce with Caddy

[blipdrifter]

Hi! I just found out about LinkAce not too long ago and decided to try installing it on my Caddy server. Just one small problem: I can't figure out how to get it working with either the Docker or non-Docker install methods.

Whenever I tried to use Docker, it just gave me an error that the port was already in use (by Caddy -- I have a seperate web server I want to use alongside LinkAce because I have a static site on the same VPS), and as a result the nginx container failed to start. So I tried installing it manually via PHP and my Caddyfile, but I've futzed around with it for over an hour at this point and I can't get any further than a blank page when I try to visit the subdomain that's supposed to point to LinkAce.

Can anyone help me get LinkAce working with Caddy? I'd really appreciate it!

[Kovah]

I have not tested LinkAce together with Caddy in any setup without Docker, but with Docker there should be no problems running it. If you are using Caddy in front of LinkAce, change the port of the LinkAce container to any other port than 80 or 443:

  app:
    image: linkace/linkace:simple
    restart: unless-stopped
    depends_on:
      - db
    ports:
      - "127.0.0.1:8080:80"

and then point Caddy to that new port, 8080 in this case.

[blipdrifter]

Just tried that, got stuck on ** Starting NGINX ** again. Checked the Caddy access logs for the subdomain and apparently it's spitting out 502 errors? Here's where the Docker logs stop for me:

Also tried switching between port 8080 and port 9080 in both the Caddyfile and docker-compose.yml, no such luck. Is it supposed to be set to [port]:80 in the compose file?

[Kovah]

Starting NGINX as the last line is not wrong.
But if you use the LinkAce simple image, why is there a separate nginx container? You can either use the advanced image with a separate nginx, or the simple image that doesn't need anything else. Did you switch images while trying to get everything running?

[Kovah]

This is what a docker compose file should look like. You can change the port of the app container to something else than 80 to run behind a load balancer, but anything else should stay as it is.

version: "3"
services:
  db:
    image: mariadb:10.7
    restart: unless-stopped
    command: mysqld --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
    environment:
      - MYSQL_ROOT_PASSWORD=${DB_PASSWORD}
      - MYSQL_USER=${DB_USERNAME}
      - MYSQL_PASSWORD=${DB_PASSWORD}
      - MYSQL_DATABASE=${DB_DATABASE}
    volumes:
      - db:/var/lib/mysql
     
  app:
    image: linkace/linkace:simple
    restart: unless-stopped
    depends_on:
      - db
    ports:
      - "0.0.0.0:80:80" # <<< you may change this line to `0.0.0.0:8080:80`
    volumes:
      - ./.env:/app/.env
      - ./backups:/app/storage/app/backups
      - linkace_logs:/app/storage/logs

volumes:
  linkace_logs:
  db:
    driver: local

[blipdrifter]

Oh. I completely forgot that I was using the advanced setup 😅 Thought I would use the advanced setup since I have a cloud VPS, but apparently I don't quite understand how things work with that image so I changed to the simple one and now it launches fine and I can access it through my site -- however when I try to complete setup (yes I did change my db and redis passwords in .env beforehand), I get this error:

Database could not be configured. Please check your connection details. Details: SQLSTATE[HY000] [1045] Access denied for user 'linkace'@'[internal ip]' (using password: YES) (SQL: SHOW FULL TABLES WHERE table_type = 'BASE TABLE')

Any ideas?

[blipdrifter]

Never mind -- just pruned the container's volumes with Docker and made sure the password was entered properly during Setup and it all looks fine now. Thanks for helping, and sorry for the trouble!

[Kovah]

Glad to hear it's working!