You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cannot login with any user which is not a superuser in ngx.
With a non-superuser, there is a little popup window stating something like non authorized user exception
or similar. The popup disappears very fast and then the app continues to try to set something, but it get stuck at this point.
Only thing I can do is to force the app to stop and give the user superuser rights.
There is not mention of this exception in the logs.
The only warining is that the server API is v5 and the app only supports v3.
Is there a special setting in ngx server to make a non-superuser work?
Steps to reproduce
Install ngx 2.7.2 on docker
Create non-superuser
Try to login -> fail
Log output from the app
No response
Screenshots
No response
Paperless-ng*x Version
2.7.2
Paperless-Mobile Version
3.2.1
Device
Pixel 6
Operating System Version
Android 13
Device Locale
german
Selected Locale
German
Additional Context
No response
The text was updated successfully, but these errors were encountered:
What happened?
I cannot login with any user which is not a superuser in ngx.
With a non-superuser, there is a little popup window stating something like
non authorized user exception
or similar. The popup disappears very fast and then the app continues to try to set something, but it get stuck at this point.
Only thing I can do is to force the app to stop and give the user superuser rights.
There is not mention of this exception in the logs.
The only warining is that the server API is v5 and the app only supports v3.
Is there a special setting in ngx server to make a non-superuser work?
Steps to reproduce
Log output from the app
No response
Screenshots
No response
Paperless-ng*x Version
2.7.2
Paperless-Mobile Version
3.2.1
Device
Pixel 6
Operating System Version
Android 13
Device Locale
german
Selected Locale
German
Additional Context
No response
The text was updated successfully, but these errors were encountered: