Dear team,
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?
Dear team,
I was able to resolve the issue for now, but you must look at it.
dig +short api.nuki.io
returns:
57.129.72.249
57.129.55.20
first default 1 returns the error always and the second works.
in node systems it uses the first default address so it fails.
I modified it to use only the second one in order to solve it for now, but i think you should look at it.
Hello,
I have the same problem.
I use 2 Nuki locks in Homey and as of today only one works. When I do a reboot, one of them randomly stays non-functional.
What should I do?
I confirm the issue has been ongoing since 02/04/2025 at 08:30 AM (Paris time).
Our Node.js app is also receiving ECONNREFUSED errors, occurring randomly—possibly due to improper IP switching behind api.nuki.io.
dig +short api.nuki.io
57.129.72.249
57.129.55.20
Thanks for the command! 
Interestingly, requests work fine in Insomnia, but in Node.js, they fail with ECONNREFUSED most of the time.
I tried reaching out to Nuki support yesterday, but the process to access their technical team is a labyrinth. They seem lost… or asleep. 
Meanwhile, our entire Nuki park cannot be monitored as programmed. 
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.
Hi,
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…
Hi there,
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.
Apologies for the inconvenience.
A fix was deployed and the issue has been resolved.
Once again, I apologise for the inconvenience this issue caused.
This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.
