Closed joszz closed 1 year ago
HTTP 504 - Verisure's fault.
MFA does seem to work with the app or on verisures own website though... So I'm not 100% convinced it is a verisure problem. Maybe they just sent a 504 but block the request coming from anything other than first party software or something to that extent?
MFA works fine for me.
Error 504 is a gateway timeout error, but the content seems strange I must say.
Do you still get the error?
Have tried to remove the cookie file ~/.verisure-cookie
?
I still get the error. I forgot to mention a crucial detail it seems, my bad; problem only seems to occur inside a docker container and not on the host. Although before it worked perfectly fine in the same container. Something must've changed, unsure of what (not the firewall or anything obvious it seems). must be an issue on my end, but still clueless. Doesn't seem to work with host networking as well, which makes things even stranger...
I did remove the cookie. I get to entering the verification code and then receive the timeout
I'll close this for now since it's most likely an issue somewhere on my end. Will investigate further
I've used this API successfully for some time, but today I noticed it broke doing the MFA verification.
I'm not sure if it's because of the update to version 2.5.3, or something changed @ the verisure API side. After waiting some time I get the error below. If I can provide any more info, or if I have to test in another way, please tell me :)