1.1" 200 11144 spamming logs #632

New issue

Closed

opened 2026-03-01 14:45:10 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 14:45:10 +03:00

Owner

Originally created by @eytschjey on GitHub (Jul 28, 2022).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1007

Please excuse me if this has already been discussed or is a total noob question.

I've set up archivebox as a docker container in an effort to have a simple daily backup of a static website.
I can reach the web GUI and managed to create an account and back up the page. But when looking in the logs, it keeps saying "GET /admin/login/ HTTP/1.1" 200 11144 every few minutes.

Here's my docker-compose:

version: '2.4'

services:
    archivebox:
        # build: .                              
        image: ${DOCKER_IMAGE:-archivebox/archivebox:master}
        command: server --quick-init 0.0.0.0:8000
        ports:
            - 6969:8000
        environment:
            - ALLOWED_HOSTS=*                  
            - MEDIA_MAX_SIZE=750m
            - PUID=1000
            - PGID=1000

        volumes:
            - /home/{myuseraccount}/docker/archivebox:/data

Am i doing something wrong?

Originally created by @eytschjey on GitHub (Jul 28, 2022). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1007 Please excuse me if this has already been discussed or is a total noob question. I've set up archivebox as a docker container in an effort to have a simple daily backup of a static website. I can reach the web GUI and managed to create an account and back up the page. But when looking in the logs, it keeps saying "GET /admin/login/ HTTP/1.1" 200 11144 every few minutes. Here's my docker-compose: ``` version: '2.4' services: archivebox: # build: . image: ${DOCKER_IMAGE:-archivebox/archivebox:master} command: server --quick-init 0.0.0.0:8000 ports: - 6969:8000 environment: - ALLOWED_HOSTS=* - MEDIA_MAX_SIZE=750m - PUID=1000 - PGID=1000 volumes: - /home/{myuseraccount}/docker/archivebox:/data ``` Am i doing something wrong?

kerem closed this issue

2026-03-01 14:45:10 +03:00

kerem commented

2026-03-01 14:45:11 +03:00

Author

Owner

@pirate commented on GitHub (Jul 29, 2022):

That's normal, it's the Docker healthcheck heartbeat making sure the container is running successfully. You can disable it if you need by adding healthcheck: (as an empty entry) to the archivebox: section in your yml.

@pirate commented on GitHub (Jul 29, 2022): That's normal, it's the Docker healthcheck heartbeat making sure the container is running successfully. You can disable it if you need by adding `healthcheck:` (as an empty entry) to the `archivebox:` section in your yml.

kerem referenced this issue

2026-03-01 14:49:03 +03:00

[PR #632] [MERGED] Fix issue #617 by using mark_safe in combination with format_html #1254

kerem referenced this issue

2026-03-01 18:00:41 +03:00

[PR #632] Fix issue #617 by using mark_safe in combination with format_html #2768

kerem referenced this issue

2026-03-15 01:35:32 +03:00

[PR #632] [MERGED] Fix issue #617 by using mark_safe in combination with format_html #4269