Tuetenk0pp

@Mika@MobileDude I have a working setup: PAPERLESS_APPS=allauth.socialaccount.providers.openid_connect PAPERLESS_SOCIALACCOUNT_PROVIDERS='{"openid_connect": {"APPS": [{"provider_id": "authentik", "name": "Authentik", "client_id": "YOUR_CLIENT_ID", "secret": "YOUR_CLIENT_SECRET", "settings":{ "server_url": "https://auth.domain.tld/application/o/paperless/.well-known/openid-configuration"}}], "OAUTH_PKCE_ENABLED": "True"}}' Be sure to name the Authentik Outpost "paperless". In addition, you can set the following variables, once the basics work: # hide the default login form PAPERLESS_DISABLE_REGULAR_LOGIN=true # sign up new users from authentik automatically PAPERLESS_SOCIAL_AUTO_SIGNUP=true # redirect to authentik after logout PAPERLESS_LOGOUT_REDIRECT_URL=https://auth.domain.tld/application/o/paperless/end-session/logout # trust authentik to provide valid email addresses PAPERLESS_ACCOUNT_EMAIL_VERIFICATION=none I hope this helps

Actually not, BUT: Since the measured Powerdraw from the wall was lower with the VM on than off, I leave it running all the time. And I never had the issue again. Obviously, this does not work if you use the same HW in different VMs and you need to switch them on and off.

Have you checked the permissions on this file? Use `ls -l /mnt/user/share_paperless_ngx/scripts/`for that. It should look like this: -rw-rw-rw- I have had these kinds of errors in the past and was able to fix it with LF line endings. pikepdf comes installed in the paperless image so no need to worry about that.

it depends: if the package is already installed in the paperless container, import is the only thing you need. If its not installed, python would give an error like this: Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'pikepdf'

Did some german youtuber recently do a video on paperless? The amount of posts in this topic is kinda suspicious

How did you save the script? Maybe it's the line endings.

Is it the only thing you changed? Yes! Did you also change the TZ setting? Possible.

Timezone should be 'Europe/Berlin' You could try that

Can we have a look at the logs? Both paperless and redis. Also, did you create the paperless folders over smb like shown in the video? This could have messed up the file permissions. Better to let unraid create those folders on container creation.

Maybe something to do with the file format (line endings) or perhaps missing shebang? I'm curious, what do you want to achieve with a pre-consumption script? I was always aware of that functionality but found no use for it.

I have a problem with my VM setup. Every now and then, my previously working VM fails to start. When I try to solve the issue with a restart of libvirt via the VM Manager, libvirt fails to start. Once I fully reboot the server, everything works fine until a few days later, the problem reoccurs. How can I solve that issue? I attached two diagnostics: one before I tried to restart libvirt and the other one just after it in case some log gets overwritten. I noticed these issues in the libvirt log: virNetSocketReadWire:1791 : End of file while reading data: Input/output error this appears every 10 minutes qemuDomainGetBlockInfo:11099 : invalid argument: invalid path Endeavouros_Cassini_Nova-03-2023_R2.iso not assigned to domain this appears every now and then and is related to a VM that I never started. I will remove the VM and see if that changes anything warning : qemuDomainObjBeginJobInternal:858 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain Windows 11; current job is (modify, none, none) owned by (15916 remoteDispatchDomainAttachDevice, 0 <null>, 0 <null> (flags=0x0)) for (1777s, 0s, 0s) error : qemuDomainObjBeginJobInternal:893 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainAttachDevice) this is probably the most relevant section because it is related to the VM I am trying to start. error : qemuMonitorIORead:423 : Unable to read from monitor: Connection reset by peer and this is the first line in the libvirt log after I tried to restart the libvirt service. The VMs Tab reads 'Libvirt Service failed to start.' I will now restart the server and hope for somebody to help me unraid-server-diagnostics-20230829-0859.zip unraid-server-diagnostics-20230829-0920.zip

My bad, paperless uses an SQLite database by default, although not recommended. So your setup should work. Did you create a superuser with this command? docker run --rm PAPERLESS_CONTAINER_NAME createsuperuser

Redis is only in ram

Have a look at this: https://github.com/paperless-ngx/paperless-ngx/tree/main/docker/compose Also, the paperless-ngx template from community apps in Unraid should have some guidelines for you to follow.

You also need a database server eg Postgres.