-
-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Extended Paperless-ngx docs #40012
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: current
Are you sure you want to change the base?
Extended Paperless-ngx docs #40012
Conversation
…a updates, known limitations
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
{% endraw %} | ||
{% enddetails %} | ||
|
||
## Data Updates |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Data Updates | |
## Data updates |
|
||
## Troubleshooting | ||
|
||
{% details "Invalid hostname or IP address" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a message I see? or the cause of an issue?
|
||
{% enddetails %} | ||
|
||
{% details "The token does not have permission to access the API" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here. Is this an error messsage that comes up or the cause of an issue?
In this case, verify whether the token is still valid and correctly assigned to the user. | ||
|
||
You can also test the token using the Swagger interface available at | ||
`https://paperless.example.com/api/schema/view/` | ||
|
||
Click on **"Authorize"** in the Swagger UI to enter your token at **tokenAuth (apiKey)**, then try accessing the relevant endpoints like `/api/statistics/` to ensure they respond as expected. | ||
|
||
If everything works correctly in Swagger but the integration still fails, check whether a reverse proxy (e.g., NGINX) is returning an **HTTP 403 error**. If so, the integration may also report this as a permission issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, verify whether the token is still valid and correctly assigned to the user. | |
You can also test the token using the Swagger interface available at | |
`https://paperless.example.com/api/schema/view/` | |
Click on **"Authorize"** in the Swagger UI to enter your token at **tokenAuth (apiKey)**, then try accessing the relevant endpoints like `/api/statistics/` to ensure they respond as expected. | |
If everything works correctly in Swagger but the integration still fails, check whether a reverse proxy (e.g., NGINX) is returning an **HTTP 403 error**. If so, the integration may also report this as a permission issue. | |
1. Verify whether the token is still valid and correctly assigned to the user. | |
2. You can also test the token using the Swagger interface available at | |
`https://paperless.example.com/api/schema/view/` | |
- In the Swagger UI, select **Authorize** to enter your token at **tokenAuth (apiKey)**. | |
- Then, try accessing the relevant endpoints like `/api/statistics/` to ensure they respond as expected. | |
3. If everything works correctly in Swagger but the integration still fails, check whether a reverse proxy (for example, NGINX) is returning an **HTTP 403 error**. | |
- If so, the integration may also report this as a permission issue. |
I think this could be a step-by-step procedure
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Proposed change
Added some documentation for Paperless-ngx
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.