Closed LeoKlaus closed 1 year ago
HTTP 400 indicates that the server couldn't handle the request, which is weird.
Can you check the logs for your Webserver container? They should contain more information.
Other than that, make sure you've selected the proper protocol (http for local connections). The URL should look like this:
192.168.1.123:8080
(no trailing slash, no protocol)
What port do you use to access the WebUI? Is http://{IP-of-your-server}:{port}/api/
reachable in your browser?
Hey LeoKlaus, thanks for picking this up!
WebUI is "http://192.168.178.74:8010/dashboard"
Log from Webserver:
[2023-10-12 11:42:59,840] [INFO] [paperless.auth] Login failed for user PaperlessAdmin
from private IP 192.168.178.79
.
[2023-10-12 11:42:59,844] [WARNING] [django.request] Bad Request: /api/token/
my credentials are right...
You are referring to port 8080 I am using 8010 for my WebUI... When I look into my compose script:
webserver: ... ports:
Do I have to change here my script to different port setting?
Many thanks
You shouldn't have to change anything in your compose script.
A 400 response from the /api/token/ endpoint usually indicates wrong credentials. Is the user PaperlessAdmin
a superuser on your instance?
Can you try the following command on a Linux machine in your network (for example the server that runs Paperless)? Replace "your-password" with the password for your Paperless user.
curl --request POST \
--url http://192.168.178.74:8010/api/token/ \
--header 'Content-Type: application/json' \
--data '{
"username": "PaperlessAdmin",
"password": "your-password"
}'
If the response doesn't look like this {"token":"4aabxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx84bc"}
, please tell me what it says.
Well, well, well...
superuser -> this was the issue. I was not aware of that missing piece (had some restrictions) -.- shame on me Now it worked at the first go.
Apologies for the circumstances.
Greetings from Rheinhessen -> 15km west from you :-D (just saw the imprint) btw. all features activated just to support your effort!
superuser -> this was the issue. I was not aware of that missing piece (had some restrictions) -.- shame on me Now it worked at the first go.
Glad it worked! Generally, the user you use with Paperparrot doesn't have to be a superuser, but I've been unable to find what permission is needed and the Paperless documentation sadly doesn't have any info on that either.
Vielen Dank für Deine Unterstützung ;)
Discussed in https://github.com/LeoKlaus/Paperparrot/discussions/136