Benoît Viguier

Skip version 5 all together. Go directly to version 6. I see that you are using traefik, you need to forward the proto. As follow is part of my docker...

BTW looking at your traefik setup: This is bad practice: ``` - /var/run/docker.sock:/var/run/docker.sock:ro ``` If traefik is compromised your all server is F***. Here is some reading material : https://github.com/wollomatic/socket-proxy...

Also there is a change in the volumes. Here is some details (I think you can infer what needs changing): ``` volumes: - ${PATH_TO_FILES:-.}/lychee/conf:/conf - ${PATH_TO_FILES:-.}/lychee/uploads:/uploads - ${PATH_TO_FILES:-.}/lychee/sym:/sym - ${PATH_TO_FILES:-.}/lychee/logs:/logs...

I would also suggest to use doozle https://dozzle.dev/ It is very very nice to get the logs of your container in real time.

> traefik is my edge TLS termination so this is unnecessary? This still necessary for Lychee to know which kind of prefix to use: http or https in the links....

I see, go to your **lychee** `.env` file (in the config folder), look for the `APP_URL` and set to empty string: `APP_URL=` that will fix it. Or in your docker-compose:...

I would supply it :) PS: if you edit directly the `.env` file in `config/` you do not need to redeploy, the changes are pretty much immediate.

Yes, that is why the proto forwarding is needed. See here: https://github.com/LycheeOrg/Lychee-Docker/issues/214#issuecomment-2568119521 So that Lychee knows that you are using https. They may be unnecessary for basic setup, but are...

Interesting. That should not be the case.

Unfortunately, due to the lack of fonts, I'm going to close this one.