dakhnod
auth error: response code is not 200: 404 when not using trailing slashes
I kept getting a toast with auth error: response code is not 200: 404. After some fiddling (and resetting my password), I figured out what inputs do seem to make it work right now to authenticate (in order of appearance on the screen):
https://c.fossil.com/v2.1/rpc/auth/
https://c.fossil.com/v2.1/rpc/device/
https://c.fossil.com/v2/users/me/devices/
https://c.fossil.com/v2/users/me/devices/%s/secret-key/
Now, the weird thing, upong trying to fetch the key from the server, these url's now give a 404. This is subsequently fixed by removing the trailing slashes again:
https://c.fossil.com/v2.1/rpc/auth
https://c.fossil.com/v2.1/rpc/device
https://c.fossil.com/v2/users/me/devices
https://c.fossil.com/v2/users/me/devices/%s/secret-key
Pressing authenticate again now gives a 403, however fetching the key like this works.
Not fully sure what is causing this. I assume it's something within the servers changing. I previously used the Python script from the gadgetbridge docs to get my key, however running that now errors with the message [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1000)'.
