linuxserver / docker-healthchecks

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

Exception Value: no such table: django_session #88

Closed Whisper40 closed 1 year ago

Whisper40 commented 2 years ago

linuxserver.io


Expected Behavior

I should be able to connect to the interface

Current Behavior

I was registering my account after the first init, then it throws no such table: django_session

Steps to Reproduce

  1. Fresh install with this docker-compose
  2. Try to register
  3. It fails

Environment

OS: Docker CPU architecture: x86_64 How docker service was installed:

Command used to create docker container (run/create/compose/screenshot)

healthchecksio:
    image: linuxserver/healthchecks:2.0.1
    container_name: pprod_healthchecksio
    restart: unless-stopped
    environment:
      - SITE_ROOT=healthchecksio.fr
      - SITE_NAME=Monitoring CronTab
      - SUPERUSER_EMAIL=toto@titi.com
      - SUPERUSER_PASSWORD=INeedToGenerateAPasswordHere
      - REGENERATE_SETTINGS=True
      - PUID=1000
      - PGID=1000
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.healthchecksio-pprod-router.entrypoints=websecure"
      - "traefik.http.routers.healthchecksio-pprod-router.rule=Host(`healthchecksio-dependencies-scan...`,`healthchecksio-dependencies-scan-..`)"
      - "traefik.http.routers.healthchecksio-pprod-router.service=healthchecksio-pprod-service"
      - "traefik.http.routers.healthchecksio-pprod-router.tls=true"
      - "traefik.http.services.healthchecksio-pprod-service.loadbalancer.server.port=8000"
    volumes:
      - ./healthchecksio:/config
    networks:
      - proxy

Docker logs

github-actions[bot] commented 2 years ago

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

github-actions[bot] commented 2 years ago

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

PepinoGz commented 1 year ago

I am writing this here in case it happens to anyone. It seems there is a problem and if you fill in the "SUPERUSER_EMAIL" or "SUPERUSER_PASSWORD" fields, the application will not start. Simply leave them blank and then create an account (you must configure an smtp server).

github-actions[bot] commented 1 year ago

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

besendorf commented 1 year ago

This is still an issue. I just had the same problem

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.

besendorf commented 1 year ago

Still an issue

j0nnymoe commented 1 year ago

As this issue is nearly a year old and you aren't the original poster @besendorf - please can you provide compose info + container logs + hardware info? Thanks

DonMercedesMoped commented 1 year ago

@besendorf I ran into that issue myself and was able to resolve it.

Attached the container: docker exec -it healthchecks /bin/bash Changed into settings directory: /app/healthchecks/hc Opened local_settings.py

Changed CSRF_TRUSTED_ORIGINS = [ ""]

to

CSRF_TRUSTED_ORIGINS = [ 'http://localhost','http://192.168.1.0/24',]

Restarted the container.

Hope that also works for you.

besendorf commented 1 year ago

This seemed to do the trick for me. Could this be incorporated in the image directly? @j0nnymoe ?

thespad commented 1 year ago

It's prominently displayed in the readme https://github.com/linuxserver/docker-healthchecks#note-on-csrf_trusted_origins

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