dickyasqaelani/1panel-captcha-bypassed repository overview

⁠1Panel Without Captcha

1Panel management panel with the login CAPTCHA permanently disabled, so it never appears again regardless of login attempts.

• Based on: moelin/1panel:latest (community build)
• Change: patched 1panel-core binary — the in-memory IP tracker function (*IPTracker).NeedCaptcha is patched to always return false. CAPTCHA can never be triggered, even after repeated failed logins.
• Volume-based state (DB, config, apps) is fully preserved and compatible with the upstream image.

⁠Why this image exists

Both the upstream moelin/1panel and the official 1panel images include a login CAPTCHA. It is a math-problem CAPTCHA (NewDriverMath) that is only demanded once your IP has been flagged after failed logins. Many users (including automated onboarding) get stuck in a loop: wrong password → IP flagged → CAPTCHA required on every login → CAPTCHA frequently mis-typed or failed.

This image eliminates the CAPTCHA entirely so logins only need the correct username and password.

⁠What was patched

Only those 3 bytes of the binary differ from the base image. Everything else — entrypoint, config, DB, app storage — is identical.

⁠How it was verified

1. 6 consecutive failed logins (ErrAuth) → GET /api/v2/core/auth/setting still returns "needCaptcha":false.
2. Correct login still succeeds: HTTP 200, role ADMIN.
3. Tested on a brand-new container from this image (no volumes) — service starts normally.

⁠Quick Start

docker run -d --name 1panel \
  -e TZ=Asia/Jakarta \
  -e PASSWORD=<your-password> \
  -v /DATA/AppData/1panel/root:/root \
  -v /DATA/AppData/1panel/opt:/opt \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /var/lib/docker/volumes:/var/lib/docker/volumes \
  -p 10086:10086 \
  --restart unless-stopped \
  dickyasqaelani/1panel-captcha-bypassed:latest

⁠Running with long-lived state (recommended)

1Panel data must live on the host so upgrades don't lose your panels, apps and databases:

mkdir -p /DATA/AppData/1panel/root /DATA/AppData/1panel/opt

docker run -d --name 1panel \
  -e TZ=Asia/Jakarta \
  -e PASSWORD=<your-password> \
  -v /DATA/AppData/1panel/root:/root \
  -v /DATA/AppData/1panel/opt:/opt \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /var/lib/docker/volumes:/var/lib/docker/volumes \
  -p 10086:10086 \
  --restart unless-stopped \
  dickyasqaelani/1panel-captcha-bypassed:latest

⁠Ports & volumes

⁠Environment variables

⁠Upgrading / migrating from moelin/1panel

Because state (DB and config) lives on the host volumes, you can switch images without data loss:

# stop & remove old container (volumes are NOT deleted)
docker stop 1panel && docker rm 1panel

# run the patched image with the same mounts
docker run -d --name 1panel \
  -e PASSWORD=<same-password> \
  -v /DATA/AppData/1panel/root:/root \
  -v /DATA/AppData/1panel/opt:/opt \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /var/lib/docker/volumes:/var/lib/docker/volumes \
  -p 10086:10086 \
  --restart unless-stopped \
  dickyasqaelani/1panel-captcha-bypassed:latest

# if the password was randomized before, reset it:
docker exec 1panel /usr/local/bin/1pctl update password

⁠Changing the admin password later

docker exec 1panel /usr/local/bin/1pctl update password

⁠Security notice

Removing the CAPTCHA lowers brute-force resistance slightly. The panel still logs failed login attempts and IP-flagging still exists internally; only the CAPTCHA UI check is bypassed. Use a strong password (the panel warns about weak ones by default).

⁠License & credits

• 1Panel: https://github.com/1Panel-dev/1Panel⁠ (Apache-2.0)
• Base image: https://hub.docker.com/r/moelin/1panel⁠