Oliver22

Hi Djoss, many thanks for the answer. I tried several times and waited up to 3 hours. I would assume that any update does not take that long. One time, I saw a red bar at the top stating 'connection refused' for some seconds. Do you have any idea, what I am doing wrong?

It would be great if you could help me! Sorry, if this is something obvious. I just installed the docker and I only get a black screen and nothing happens. My log: [cont-init ] 10-check-app-niceness.sh: executing... [cont-init ] 10-check-app-niceness.sh: terminated successfully. [cont-init ] 10-clean-logmonitor-states.sh: executing... [cont-init ] 10-clean-logmonitor-states.sh: terminated successfully. [cont-init ] 10-clean-tmp-dir.sh: executing... [cont-init ] 10-clean-tmp-dir.sh: terminated successfully. [cont-init ] 10-fontconfig-cache-dir.sh: executing... [cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully. [cont-init ] 10-init-users.sh: executing... [cont-init ] 10-init-users.sh: terminated successfully. [cont-init ] 10-nginx.sh: executing... [cont-init ] 10-nginx.sh: terminated successfully. [cont-init ] 10-openbox.sh: executing... [cont-init ] 10-openbox.sh: terminated successfully. [cont-init ] 10-pkgs-mirror.sh: executing... [cont-init ] 10-pkgs-mirror.sh: terminated successfully. [cont-init ] 10-pulse.sh: executing... [cont-init ] 10-pulse.sh: terminated successfully. [cont-init ] 10-set-tmp-dir-perms.sh: executing... [cont-init ] 10-set-tmp-dir-perms.sh: terminated successfully. [cont-init ] 10-vnc-password.sh: executing... [cont-init ] 10-vnc-password.sh: terminated successfully. [cont-init ] 10-web-data.sh: executing... [cont-init ] 10-web-data.sh: terminated successfully. [cont-init ] 10-webauth.sh: executing... [cont-init ] 10-webauth.sh: terminated successfully. [cont-init ] 10-x11-unix.sh: executing... [cont-init ] 10-x11-unix.sh: terminated successfully. [cont-init ] 10-xdg-runtime-dir.sh: executing... [cont-init ] 10-xdg-runtime-dir.sh: terminated successfully. [cont-init ] 15-cjk-font.sh: executing... [cont-init ] 15-cjk-font.sh: terminated successfully. [cont-init ] 15-install-pkgs.sh: executing... [cont-init ] 15-install-pkgs.sh: terminated successfully. [cont-init ] 55-jdownloader2.sh: executing... [cont-init ] 55-jdownloader2.sh: terminated successfully. [cont-init ] 85-take-config-ownership.sh: executing... [cont-init ] 85-take-config-ownership.sh: terminated successfully. [cont-init ] 89-info.sh: executing... ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮ │ │ │ Application: JDownloader 2 │ │ Application Version: n/a │ │ Docker Image Version: 24.12.1 │ │ Docker Image Platform: linux/amd64 │ │ │ ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯ [cont-init ] 89-info.sh: terminated successfully. [cont-init ] all container initialization scripts executed. [init ] giving control to process supervisor. [supervisor ] loading services... [supervisor ] loading service 'default'... [supervisor ] loading service 'app'... [supervisor ] loading service 'gui'... [supervisor ] loading service 'audiorecorder'... [supervisor ] service 'audiorecorder' is disabled. [supervisor ] loading service 'certsmonitor'... [supervisor ] service 'certsmonitor' is disabled. [supervisor ] loading service 'nginx'... [supervisor ] loading service 'webauth'... [supervisor ] service 'webauth' is disabled. [supervisor ] loading service 'xvnc'... [supervisor ] loading service 'openbox'... [supervisor ] loading service 'pulseaudio'... [supervisor ] service 'pulseaudio' is disabled. [supervisor ] loading service 'xcompmgr'... [supervisor ] loading service 'logmonitor'... [supervisor ] service 'logmonitor' is disabled. [supervisor ] loading service 'logrotate'... [supervisor ] all services loaded. [supervisor ] starting services... [supervisor ] starting service 'xvnc'... [xvnc ] Xvnc TigerVNC 1.14.1 - built Dec 6 2024 15:14:58 [xvnc ] Copyright (C) 1999-2024 TigerVNC Team and many others (see README.rst) [xvnc ] See https://www.tigervnc.org for information on TigerVNC. [xvnc ] Underlying X server release 12014000 [xvnc ] Fri Jan 17 19:15:10 2025 [xvnc ] vncext: VNC extension running! [xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660) [xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900 [xvnc ] vncext: created VNC server for screen 0 [supervisor ] starting service 'nginx'... [nginx ] Listening for HTTP connections on port 5800. [supervisor ] starting service 'openbox'... [supervisor ] starting service 'xcompmgr'... [supervisor ] starting service 'app'... [supervisor ] all services started. [xvnc ] Fri Jan 17 19:15:24 2025 [xvnc ] Connections: accepted: /tmp/vnc.sock [xvnc ] SConnection: Client needs protocol version 3.8 How do I get this protocol version 3.8 which seems to be necessary? Many thanks!

Vielen Dank! Das war es!

Hi Alturismo, vielen Dank für Deine schnelle Antwort. Das AutoTweak-plugin habe ich entfernt. docker run (paperless-ngx): [2024-11-16 17:30:44 +0100] [197] [INFO] Starting gunicorn 23.0.0 [2024-11-16 17:30:44 +0100] [197] [INFO] Listening at: http://[::]:8000 (197) [2024-11-16 17:30:44 +0100] [197] [INFO] Using worker: paperless.workers.ConfigurableWorker [2024-11-16 17:30:44 +0100] [197] [INFO] Server is ready. Spawning workers [2024-11-16 17:30:44,274] [INFO] [paperless.management.consumer] Using inotify to watch directory for changes: /usr/src/paperless/consume [2024-11-16 17:30:44,462] [INFO] [celery.beat] beat: Starting... [2024-11-16 17:30:44,530] [INFO] [celery.worker.consumer.connection] Connected to redis://192.168.178.175:6379// [2024-11-16 17:30:44,536] [INFO] [celery.apps.worker] celery@ea13495a0633 ready. Applying documents.1045_alter_customfieldinstance_value_monetary_squashed_1049_document_deleted_at_document_restored_at... OK Applying documents.1050_customfield_extra_data_and_more... OK Applying documents.1051_alter_correspondent_owner_alter_document_owner_and_more... OK Applying documents.1052_document_transaction_id... OK Applying documents.1053_document_page_count... OK Applying documents.1054_customfieldinstance_value_monetary_amount_and_more... OK Applying documents.1055_alter_storagepath_path... OK Applying documents.1056_customfieldinstance_deleted_at_and_more... OK Applying guardian.0001_initial... OK Applying guardian.0002_generic_permissions_index... OK Applying paperless.0001_initial... OK Applying paperless.0002_applicationconfiguration_app_logo_and_more... OK Applying paperless.0003_alter_applicationconfiguration_max_image_pixels... OK Applying paperless_mail.0025_alter_mailaccount_owner_alter_mailrule_owner_and_more... OK Applying paperless_mail.0026_mailrule_enabled... OK Applying paperless_mail.0027_mailaccount_expiration_mailaccount_account_type_and_more... OK Applying paperless_mail.0028_alter_mailaccount_password_and_more... OK Applying sessions.0001_initial... OK Applying socialaccount.0001_initial... OK Applying socialaccount.0002_token_max_lengths... OK Applying socialaccount.0003_extra_data_default_dict... OK Applying socialaccount.0004_app_provider_id_settings... OK Applying socialaccount.0005_socialtoken_nullable_app... OK Applying socialaccount.0006_alter_socialaccount_extra_data... OK Running Django checks System check identified no issues (0 silenced). Search index out of date. Updating... Executing /usr/local/bin/paperless_cmd.sh 2024-11-16 17:30:41,439 INFO Set uid to user 0 succeeded 2024-11-16 17:30:41,440 INFO supervisord started with pid 1 2024-11-16 17:30:42,442 INFO spawned: 'gunicorn' with pid 197 2024-11-16 17:30:42,443 INFO spawned: 'celery' with pid 198 2024-11-16 17:30:42,444 INFO spawned: 'celery-beat' with pid 199 2024-11-16 17:30:42,444 INFO spawned: 'consumer' with pid 200 2024-11-16 17:30:42,445 INFO spawned: 'celery-flower' with pid 201 Checking if we should start flower... Not starting flower 2024-11-16 17:30:42,448 INFO success: celery-flower entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-11-16 17:30:42,448 INFO exited: celery-flower (exit status 0; expected) celery beat v5.4.0 (opalescent) is starting. 2024-11-16 17:30:44,266 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-11-16 17:30:44,266 INFO success: celery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-11-16 17:30:44,266 INFO success: celery-beat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-11-16 17:30:44,266 INFO success: consumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) __ - ... __ - _ LocalTime -> 2024-11-16 17:30:44 Configuration -> . broker -> redis://192.168.178.175: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) -------------- celery@ea13495a0633 v5.4.0 (opalescent) --- ***** ----- -- ******* ---- Linux-6.1.106-Unraid-x86_64-with-glibc2.36 2024-11-16 17:30:44 - *** --- * --- - ** ---------- [config] - ** ---------- .> app: paperless:0x14c7a052f6b0 - ** ---------- .> transport: redis://192.168.178.175:6379// - ** ---------- .> results: - *** --- * --- .> concurrency: 1 (prefork) -- ******* ---- .> task events: ON --- ***** ----- -------------- [queues] .> celery exchange=celery(direct) key=celery [tasks] . documents.bulk_edit.delete . documents.tasks.bulk_update_documents . documents.tasks.consume_file . documents.tasks.empty_trash . documents.tasks.index_optimize . documents.tasks.sanity_check . documents.tasks.train_classifier . documents.tasks.update_document_archive_file . paperless_mail.mail.apply_mail_action . paperless_mail.mail.error_callback . paperless_mail.tasks.process_mail_accounts Screenshot share setting system Screenshot share appdata Screenshot Main: Ich hoffe, das ist alles, was Du brauchst. Bin gespannt, welchen Fehler ich gemacht habe. Vielen Dank!

Liebe Community, ich bin in der Mitte meiner Unraid-Testphase und frage mich so langsam, ob Unraid nicht viel zu kompliziert für mich ist.... Konkret habe ich große Probleme, apps wie Paperless-ngx zum Laufen zu bringen. Mittlerweile glaube ich, dass ein Grund dafür ist, dass ich außer NginxProxManager und filebrowser (hatte ich schon wieder deinstalliert) keine Ordner unter appdata habe, obwohl ich paperless-ngx, cloudfare-DDNS und Redis installiert habe. Deswegen muss ich vermutlich jedes Mal den superuser in paperless neu anlegen, wenn ich etwas im Template ändere. Ich habe das diagnostics.zip beigefügt. Vielleicht wisst Ihr ja, welchen Fehler ich gemacht habe und wie ich ihn wieder korrigieren kann? Das wäre super toll! Vielen Dank! unraid22-diagnostics-20241116-1557.zip

Vielen Dank für Deine schnelle Antwort! docker run: Und hier ist das log der Applikation (die redis-Adresse habe ich ausgeixxxt): [2024-11-15 13:51:01,187] [INFO] [paperless.management.consumer] Using inotify to watch directory for changes: /usr/src/paperless/consume [2024-11-15 13:51:01 +0100] [197] [INFO] Starting gunicorn 23.0.0 [2024-11-15 13:51:01 +0100] [197] [INFO] Listening at: http://[::]:8000 (197) [2024-11-15 13:51:01 +0100] [197] [INFO] Using worker: paperless.workers.ConfigurableWorker [2024-11-15 13:51:01 +0100] [197] [INFO] Server is ready. Spawning workers [2024-11-15 13:51:01,464] [INFO] [celery.beat] beat: Starting... [2024-11-15 13:51:01,512] [INFO] [celery.worker.consumer.connection] Connected to redis://xxx.xxx.xxx.xxx:6379// [2024-11-15 13:51:01,519] [INFO] [celery.apps.worker] celery@271d586a8aac ready. Applying documents.1045_alter_customfieldinstance_value_monetary_squashed_1049_document_deleted_at_document_restored_at... OK Applying documents.1050_customfield_extra_data_and_more... OK Applying documents.1051_alter_correspondent_owner_alter_document_owner_and_more... OK Applying documents.1052_document_transaction_id... OK Applying documents.1053_document_page_count... OK Applying documents.1054_customfieldinstance_value_monetary_amount_and_more... OK Applying documents.1055_alter_storagepath_path... OK Applying documents.1056_customfieldinstance_deleted_at_and_more... OK Applying guardian.0001_initial... OK Applying guardian.0002_generic_permissions_index... OK Applying paperless.0001_initial... OK Applying paperless.0002_applicationconfiguration_app_logo_and_more... OK Applying paperless.0003_alter_applicationconfiguration_max_image_pixels... OK Applying paperless_mail.0025_alter_mailaccount_owner_alter_mailrule_owner_and_more... OK Applying paperless_mail.0026_mailrule_enabled... OK Applying paperless_mail.0027_mailaccount_expiration_mailaccount_account_type_and_more... OK Applying paperless_mail.0028_alter_mailaccount_password_and_more... OK Applying sessions.0001_initial... OK Applying socialaccount.0001_initial... OK Applying socialaccount.0002_token_max_lengths... OK Applying socialaccount.0003_extra_data_default_dict... OK Applying socialaccount.0004_app_provider_id_settings... OK Applying socialaccount.0005_socialtoken_nullable_app... OK Applying socialaccount.0006_alter_socialaccount_extra_data... OK Running Django checks System check identified no issues (0 silenced). Search index out of date. Updating... Executing /usr/local/bin/paperless_cmd.sh 2024-11-15 13:50:58,359 INFO Set uid to user 0 succeeded 2024-11-15 13:50:58,360 INFO supervisord started with pid 1 2024-11-15 13:50:59,364 INFO spawned: 'gunicorn' with pid 197 2024-11-15 13:50:59,366 INFO spawned: 'celery' with pid 198 2024-11-15 13:50:59,367 INFO spawned: 'celery-beat' with pid 199 2024-11-15 13:50:59,368 INFO spawned: 'consumer' with pid 200 2024-11-15 13:50:59,369 INFO spawned: 'celery-flower' with pid 201 Checking if we should start flower... Not starting flower 2024-11-15 13:50:59,373 INFO success: celery-flower entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-11-15 13:50:59,373 INFO exited: celery-flower (exit status 0; expected) celery beat v5.4.0 (opalescent) is starting. 2024-11-15 13:51:01,187 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-11-15 13:51:01,188 INFO success: celery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-11-15 13:51:01,188 INFO success: celery-beat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-11-15 13:51:01,188 INFO success: consumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) -------------- celery@271d586a8aac v5.4.0 (opalescent) --- ***** ----- -- ******* ---- Linux-6.1.106-Unraid-x86_64-with-glibc2.36 2024-11-15 13:51:01 - *** --- * --- - ** ---------- [config] - ** ---------- .> app: paperless:0x1468dafd7530 - ** ---------- .> transport: redis://xxx.xxx.xxx.xxx:6379// - ** ---------- .> results: - *** --- * --- .> concurrency: 1 (prefork) -- ******* ---- .> task events: ON --- ***** ----- -------------- [queues] .> celery exchange=celery(direct) key=celery [tasks] . documents.bulk_edit.delete . documents.tasks.bulk_update_documents . documents.tasks.consume_file . documents.tasks.empty_trash . documents.tasks.index_optimize . documents.tasks.sanity_check . documents.tasks.train_classifier . documents.tasks.update_document_archive_file . paperless_mail.mail.apply_mail_action . paperless_mail.mail.error_callback . paperless_mail.tasks.process_mail_accounts __ - ... __ - _ LocalTime -> 2024-11-15 13:51:01 Configuration -> . broker -> redis://xxx.xxx.xxx.xxx: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) Ich hoffe, Du findest etwas... Nochmals danke schön!

Ich habe den Pfad jetzt aktualisiert. Danach musste ich einen neuen superuser erstellen. Mein bisheriger Login funktionierte nicht mehr. Ich habe dann noch eine weitere Variable erstellt. Auch danach war der superuser weg. Mache ich noch etwas falsch? Es wäre toll, wenn Du mir noch einmal helfen könntest. Vielen Dank!

Vielen lieben Dank für die schnelle Hilfe. Ich war richtig blöd. Nur um ganz sicher zu sein. Ich habe Deinen Befehl eingegeben und jetzt sehe ich die Dateien im Ordner user/paperless-ngx_data/media/media/documents. Das ist ein media zu viel, oder?

Liebes Forum, ich habe vor 2 Wochen Unraid installiert, seitdem viel gelernt und scheitere gerade an paperless-ngx. Ich habe die Installationsanleitung unter https://flemmingss.com/how-to-set-up-paperless-ngx-on-unraid/ befolgt. So sehen meine Ordner aus: Die consume und export-Ordner funktionieren. Der media-Ordner ist aber leer. Wo sind meine Dokumente? Sie müssen irgendwo sein, da ich sie exportieren kann. Bei der Docker-Übersicht ist mir aufgefallen, dass dort für media nicht /usr/src/paperless/media steht, sondern 2x /mnt/user/paperless-ngx_data/media. Kann das der Grund sein? Und falls ja, wie kann ich das verändern? Ich hoffe, Ihr könnt mir helfen und die Frage ist nicht zu blöd. Vielen Dank im voraus!