linuxserver / docker-healthchecks

GNU General Public License v3.0
177 stars 38 forks source link

[HELP] App served from subdirectory (ex https://domain.tld/hc) #106

Closed deurk closed 1 year ago

deurk commented 1 year ago

Is there an existing issue for this?

Current Behavior

I have not been able to set up the docker image to work on a subdirectory of a given FQDN. The intented goal is to have several instances of Healthchecks running under the same FQDN like:

I feel like it's related to Healthchecks directly (the way Django is set up) but I might be missing something, hence the question here. Has anybody succeeded ?

I am running it behind a Traefik and can provide any configurations needed.

Thanks a lot.

Expected Behavior

No response

Steps To Reproduce

Tried setting FORCE_SCRIPT_NAME = "/xxxx" in the local_settings.py file without success.

Environment

- OS: Rocky Linux 9.1
- Docker: installed from Docker repo, latest version (Docker version 23.0.4, build f480fb1)
- Using traefik, configured correctly for plenty other services

CPU architecture

x86-64

Docker creation

version: "3"
name: ${APP_NAME}

networks:
  traefik:
    external: true

services:
  app:
    image: docker.io/linuxserver/healthchecks:v2.8.1-ls166
    restart: unless-stopped
    logging:
      options:
        max-size: 10m
        max-file: 3
    env_file:
      - .env
    volumes:
      - ${APP_VOLUMES}/config:/config
    networks:
      - traefik
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.${APP_NAME}-router.entrypoints=https"
      - "traefik.http.routers.${APP_NAME}-router.rule=Host(`${APP_FQDN}`) && Path(`/${APP_NAME}`)"
      - "traefik.http.services.${APP_NAME}-service.loadbalancer.server.port=8000"

...

### Container logs

```bash
No error or warning in the container logs
github-actions[bot] commented 1 year ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 1 year ago

This issue is locked due to inactivity