502 Bad Gateway after successful vault unlock

Help Cryptomator Hub
1

I’ve got the hub finally running self-hosted on a synology. Not locally, as I couldn’t get that to work, but in production mode. It works – it works well – I love it!

After a succesful unlock of any vault, I am being redirected to the hub online. However, this always gives an invalid redirect: 502 Bad Gateway openresty. A similar issue was noted on Github – and fixed in an earlier version. Maybe it is reoccuring?

It doesn’t affect the behavior of Cryptomator. Logins and unlocking are okay – it’s just the redirect, opening a browser tab with the error message. Perhaps you can look into it? Or is it something to adjust in Keycloak perhaps?

Thanks for Cryptomator (long time happy user) and the hub!
Tigo

2

I doubt that, no other hub client ever mentioned this.

My guess ist, that your reverese proxy config contains an error.

Cryptomator Hub uses OAuth2 for native apps to authorize vault access. In the process, a locally started server listening on localhost is spawned. When the authorization answer is recieved from the browser, the local server recieves a redirect response to the unlock-success url inside your vault.cryptomator config file. You can check the unlock-success url by copying the contents of your vault.cryptomator file into the enoded field of https://jwt.io/.