Christian Würthner
Christian Würthner
I vote for the second option. But then this endpoint should still return something else than 500, ideally 403 so clients will handle it as if the API key would...
@foosel I think there is another issue with this endpoint. 1.8.2 responds 200 OK for an invalid API key and returns a guest user: ``` { "_is_external_client": false, "needs": {...
Will check the API key stuff, give me 15 minutes
It still seems to behave the same way regarding the wrong API key, but the global one is fine (pointed software update to the `staging/bugfix`). Basically this is my test...
@foosel This seems now to work as expected but now also `/api/currentuser` returns 403 instead of the guest user when provided with an invalid API key. I guess this is...
Perfect :) Then I'll create an update as well to account for that. Thanks a lot for the quick fixes!!
That's the exact issue. Reconnect OctoPrint and when prompted use the "Give Access" button in the webinterface instead of the global API key.
Hard to say without details...can you use main menu > settings > FAQ & help > Report a bug after you saw the 500? Then we can check the app...
Just to illustrate the issue: 
Same issue on Raspberry 3B+ ``` ariang exited with code 139 ariang exited with code 139 ```