We are having sudden issues to do any request to nuki servers using the API.
Running the same request locally results with 200 OK, while from our servers we are getting "connect ECONNREFUSED 57.129.72.249 443 "
We got even to wireshark to check whats going on, but this is all we can see from our side.
your chat support basically hanged the chat in my face.
We have about 9 nuki accounts in our company and have over 1000 locks that we cannot use.
Can you please assist?
Thanks for the info @alex-oiqia .
As for now, I asked our DevOps to make a change in our managed cluster on AWS and override the default DNS result to the second one only (which works), But its a “bad” workaround to have.
Someone from Nuki team, must take a look at this soon.
I also tried a workaround by directly using the secondary IP, but it didn’t work and It’s too risky without HTTPS, and Error: Couldn’t connect to server
So, we have no choice but to wait for Nuki support. In the meantime, data inconsistency in my system keeps increasing, making recovery after the fix even more difficult.
I’ve opened three tickets with Nuki, including escalations, but still no response on this major issue!
We’re stuck waiting while the problem persists…
We are currently working on a resolution to this problem. Our status page reflects the current outage, but I will also post here once a resolution has been found.