Benoit Anastay

Hard to tell where's the problem I'll try to reproduce your setup in a virtual environment.

@yoyomax80400 I've tested locally with this parameters ``` PAPERLESS_DBENGINE=mariadb PAPERLESS_DBHOST=core-mariadb PAPERLESS_DBPORT=3306 PAPERLESS_DBNAME=homeassistant PAPERLESS_DBUSER=homeassistant PAPERLESS_DBPASS=homeassistant ``` Paperless started correctly, maybe you are concerned by those issues https://docs.paperless-ngx.com/advanced_usage/#mysql-caveats

Hello, This is an issue only if non trusted users are able to upload files to your paperless installation, the updated ghostscript is still in the testing repository of debian,...

The warning persist.

@anwa I guess there's something else wrong. I released the update without trying to consume a document, I'll check that.

I'll probably add this as a toggable feature, You can already update `paperless.conf` manually. Some users are using external auth providers and use direct access to the add-on, so ingress...

@klassm you will just be logged in to the username corresponding to the home assistant one.

There's a nginx proxy https://github.com/BenoitAnastay/paperless-home-assistant-addon/blob/main/paperless-ngx/rootfs/etc/nginx/templates/ingress.gtpl I need to add the header there, my comment wasn't accurate then.

There is something wierd with paperless, it seems that ingress path interfer with remote user header somehow Edit : ingress url start with `/api`, I need to enable API remote...

Implemented in the last release