Ich habe mich auf Paperless ausgeloggt.
Nun kommt beim einloggen die Meldung „Benutzernamen oder Passwort ungültig“. Leider funktioniert die Email auch nicht (Server Error 500).
Wie kann ich das Passwort zurück setzen?
Du kannst über das Management-Command „createsuperuser“ einen neuen Admin anlegen und von dem aus dann das andere Passwort neu setzen.
sudo docker-compose run --rm webserver createsuperuser
Hallo @Stefan,
ist das Managrement-Command für die Version 2.15.1 richtig ? Ich bekomme immer eine Fehlermeldung.
Vor 2.15 lief dieser Befehl fehlerfrei durch
Creating config_webserver_run … done
[init-start] paperless-ngx docker container starting…
[init-start] paperless-ngx docker container starting init as root
[env-init] Checking for environment from files
[env-init] No *_FILE environment found
[init-redis-wait] Waiting for Redis to report ready
[init-db-wait] Waiting for postgresql to report ready
[init-db-wait] Waiting for PostgreSQL to start…
[init-tesseract-langs] Checking if additional teseract languages needed
[init-tesseract-langs] No additional installs requested
[init-user] Mapping UID for paperless to 0
Waiting for Redis…
Connected to Redis broker.
[init-redis-wait] Redis ready
Connected to PostgreSQL
[init-db-wait] Database is ready
[init-user] Mapping GID for paperless to 0
[init-folders] Checking for folder existence
mkdir: created directory ‚/tmp/paperless‘
[init-folders] Adjusting file and folder permissions
[init-migrations] Apply database migrations…
Operations to perform:
Apply all migrations: account, admin, auditlog, auth, authtoken, contenttypes, django_celery_results, documents, guardian, mfa, paperless, paperless_mail, sessions, socialaccount
Running migrations:
No migrations to apply.
[init-superuser] Not creating superuser
[init-checks] Running Django checks
System check identified no issues (0 silenced).
[custom-init] /custom-cont-init.d doesn’t exist, nothing to do
[init-complete] paperless-ngx docker container init completed in 16 seconds
[init-complete] Starting services
[svc-flower] Checking if we should start flower…
[svc-flower] Not starting flower
[INFO] Starting granian (main PID: 204)
[INFO] Listening at: http://:::8000
[INFO] Spawning worker-1 with PID: 235
celery beat v5.4.0 (opalescent) is starting.
[2025-04-11 07:12:36,034] [INFO] [paperless.management.consumer] Using inotify to watch directory for changes: /usr/src/paperless/consume
Username (leave blank to use ‚root‘): /usr/local/lib/python3.12/site-packages/celery/platforms.py:829: SecurityWarning: You’re running the worker with superuser privileges: this is
absolutely not recommended!
Please specify a different user using the --uid option.
User information: uid=0 euid=0 gid=0 egid=0
warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format(
-------------- celery@8f9018ffc956 v5.4.0 (opalescent)
— ***** -----
– ******* ---- Linux-6.8.12-9-pve-x86_64-with-glibc2.36 2025-04-11 07:12:36
- *** — * —
- ** ---------- [config]
- ** ---------- .> app: paperless:0x7229ddf1e540
- ** ---------- .> transport: redis://broker:6379//
- ** ---------- .> results:
- *** — * — .> concurrency: 1 (prefork)
– ******* ---- .> task events: ON
— ***** -----
-------------- [queues]
.> celery exchange=celery(direct) key=celery
[tasks]
. documents.bulk_edit.delete
. documents.signals.handlers.send_webhook
. documents.tasks.bulk_update_documents
. documents.tasks.check_scheduled_workflows
. documents.tasks.consume_file
. documents.tasks.empty_trash
. documents.tasks.index_optimize
. documents.tasks.sanity_check
. documents.tasks.train_classifier
. documents.tasks.update_document_content_maybe_archive_file
. paperless_mail.mail.apply_mail_action
. paperless_mail.mail.error_callback
. paperless_mail.tasks.process_mail_accounts
[2025-04-11 07:12:36,643] [INFO] [celery.worker.consumer.connection] Connected to redis://broker:6379//
[2025-04-11 07:12:36,664] [INFO] [celery.apps.worker] celery@8f9018ffc956 ready.
__ - … __ - _
LocalTime → 2025-04-11 07:12:36
Configuration →
. broker → redis://broker:6379//
. loader → celery.loaders.app.AppLoader
. scheduler → celery.beat.PersistentScheduler
. db → /usr/src/paperless/data/celerybeat-schedule.db
. logfile → [stderr]@%INFO
. maxinterval → 5.00 minutes (300s)
[2025-04-11 07:12:36,963] [INFO] [celery.beat] beat: Starting…
[2025-04-11 07:12:36,982] [ERROR] [celery.beat] Removing corrupted schedule file ‚/usr/src/paperless/data/celerybeat-schedule.db‘: error(11, ‚Resource temporarily unavailable‘)
Traceback (most recent call last):
File „/usr/local/lib/python3.12/site-packages/celery/beat.py“, line 531, in setup_schedule
self._store = self._open_schedule()
^^^^^^^^^^^^^^^^^^^^^
File „/usr/local/lib/python3.12/site-packages/celery/beat.py“, line 521, in _open_schedule
return self.persistence.open(self.schedule_filename, writeback=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File „/usr/local/lib/python3.12/shelve.py“, line 243, in open
return DbfilenameShelf(filename, flag, protocol, writeback)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File „/usr/local/lib/python3.12/shelve.py“, line 227, in init
Shelf.init(self, dbm.open(filename, flag), protocol, writeback)
^^^^^^^^^^^^^^^^^^^^^^^^
File „/usr/local/lib/python3.12/dbm/init.py“, line 95, in open
return mod.open(file, flag, mode)
^^^^^^^^^^^^^^^^^^^^^^^^^^
_gdbm.error: [Errno 11] Resource temporarily unavailable: ‚/usr/src/paperless/data/celerybeat-schedule.db‘
[2025-04-11 07:13:00,003] [INFO] [celery.beat] Scheduler: Sending due task Check all e-mail accounts (paperless_mail.tasks.process_mail_accounts)
[2025-04-11 07:13:00,010] [INFO] [celery.worker.strategy] Task paperless_mail.tasks.process_mail_accounts[d233aa71-0912-4531-acb8-934edc110bb8] received
[2025-04-11 07:13:00,046] [INFO] [celery.app.trace] Task paperless_mail.tasks.process_mail_accounts[d233aa71-0912-4531-acb8-934edc110bb8] succeeded in 0.03470177898998372s: ‚No new documents were added.‘
[2025-04-11 07:14:00,000] [INFO] [celery.beat] Scheduler: Sending due task Check all e-mail accounts (paperless_mail.tasks.process_mail_accounts)
[2025-04-11 07:14:00,005] [INFO] [celery.worker.strategy] Task paperless_mail.tasks.process_mail_accounts[5b6ff590-b413-4e3e-a54c-85109d680428] received
[2025-04-11 07:14:00,041] [INFO] [celery.app.trace] Task paperless_mail.tasks.process_mail_accounts[5b6ff590-b413-4e3e-a54c-85109d680428] succeeded in 0.03357766800036188s: ‚No new documents were added.‘
[2025-04-11 07:15:00,000] [INFO] [celery.beat] Scheduler: Sending due task Check all e-mail accounts (paperless_mail.tasks.process_mail_accounts)
[2025-04-11 07:15:00,004] [INFO] [celery.worker.strategy] Task paperless_mail.tasks.process_mail_accounts[4740444d-92ff-4fa0-a4f1-fe8b550e8051] received
[2025-04-11 07:15:00,046] [INFO] [celery.app.trace] Task paperless_mail.tasks.process_mail_accounts[4740444d-92ff-4fa0-a4f1-fe8b550e8051] succeeded in 0.04057887000089977s: ‚No new documents were added.‘
[2025-04-11 07:16:00,000] [INFO] [celery.beat] Scheduler: Sending due task Check all e-mail accounts (paperless_mail.tasks.process_mail_accounts)
[2025-04-11 07:16:00,003] [INFO] [celery.worker.strategy] Task paperless_mail.tasks.process_mail_accounts[292de92a-bfc5-4a3a-88dd-3852720ed904] received
[2025-04-11 07:16:00,045] [INFO] [celery.app.trace] Task paperless_mail.tasks.process_mail_accounts[292de92a-bfc5-4a3a-88dd-3852720ed904] succeeded in 0.039719111009617336s: ‚No new documents were added.‘
[2025-04-11 07:17:00,000] [INFO] [celery.beat] Scheduler: Sending due task Check all e-mail accounts (paperless_mail.tasks.process_mail_accounts)
[2025-04-11 07:17:00,004] [INFO] [celery.worker.strategy] Task paperless_mail.tasks.process_mail_accounts[d4e44c16-6e5d-42d5-b7ed-fe7b3d714186] received
[2025-04-11 07:17:00,046] [INFO] [celery.app.trace] Task paperless_mail.tasks.process_mail_accounts[d4e44c16-6e5d-42d5-b7ed-fe7b3d714186] succeeded in 0.040138654003385454s: ‚No new documents were added.‘
Danke @Stefan für deine rasche Hilfestellung! Halt alles gut funktioniert. Ist mir immer noch ein Rätsel wie das passieren konnte, habe doch das Passwort im Passwort-Manager gespeichert.
Bin wieder so weit, kann mich mit meinem Passwort wieder nicht anmelden… Zum glück weiss ich jetzt wie lösen ;o)