Both, you can also use a proxy with a subdomain for paperless
# 
Breaking Change 
The 2.0.0 release has a breaking change.
The slug is updated, for this update you’ll need to rename the addon_configs folder from paperless-ngx to paperless_ngx.
You will also need to backup your addon configuration from the configuration tab, you’ll need to uninstall the the addon and reinstall it from the repository
The hostname will also be changed.
This change is a requirement to be compliant with HA supervisor backup system.
Update : This change will be avoided since the fix will be in the next HA core update
Do you know when you will be updating your addon repository? And will we be able to update the addon directly from within HA or do we need to reinstall?
Great addon, btw
I’ll try to do that before monday I need to fix others issues such as the paperless.conf file priority.
For the update Home Assistant will see paperless_ngx as a different addon.
There’s still a hope to avoid any breaking changes since there is a PR to fix the Home Assistant issue Support backup of add-ons with hyphens by agners · Pull Request #115274 · home-assistant/core · GitHub
v2.0.0 Update
Enhancements
Load paperless.confwithpython_dotenvbefore running paperless @BenoitAnastay (#136)
Maintenance
Use Uvinstead ofpip@BenoitAnastay (#135)
Dependency updates
- Update paperless-ngx/paperless-ngx to v2.7.2 @renovate (#132)
Can you please explain to me how to do this? I have tried to get my shared network folder linked since I switched over to this add-on and have been unsuccessful. I am also getting the errors showing it’s not writable and that I need to set permissions.
I also tried this suggestion below, but I didn’t understand the samba server instructions. I have this add-on installed to access my file structure in HA from Windows but that’s all I’ve done with it.
Check this :
Apologies, I had my notifications set to “never.”
Did you manage to sort everything out?
Hi Benoit,
I have a new problem:
When I try to access https://paperless.example-server.com/api/documents/?format=api from outside, it works fine to access the Django REST. In the JSON, it says “next”: “http://paperless.example-server.com:7645/api/documents/?format=api&page=2”. Since I’m using Paperparrot, I can’t fully synchronize my documents with the URL because the server always includes the port. It’s not a problem in the browser itself, as it always requests the GET without the port. Do you have any idea how I can change this so that the port is not included in the API for the app?
It’s the intended behaviour if you open a port it goes through an nginx proxy in the add-on.
If you do have a nginx proxy in your home assistant you can set it to point to the internal hostname of the add-on like this
That way you point your proxy directly to Django and pass the correct URL
The internal hostname of an add-on is shown there
I thank you. I use a Cloudflare Tunnel myself, but the whole thing works 1:1.
Do you use an addon for that ?
Yes, I use Cloudflared.
So you can try to use the host and port of the addon in this panel
http://ca5234a0-paperless-ngx:8000
It will use docker virtual network and point directly to Paperless app
With this settings the API link should be correct, if the problem persist it may be caused by cloudflare
This settings are correct. The API link is now without a port. 
You helped me with your first example to fix the problem.
I wasn’t sure.
At least if someone has the same issue, the whole process is now documented
Hello,
maybe someone here can help. Since the Home Assistant update 2024.05, I always get the error “CSRF-Verifizierung fehlgeschlagen. Anfrage abgebrochen.” .
Many people in my YT community have the same problem ( i have already tried an external url, without success). Is there already something known and is there a solution? Thanks and best regards Tobias ( smart home & more )
2 Likes
Same problem as the comment above with the same error here since updating to 2024-05.
I hope for a quick fix.
Please help.
2 Likes