# API gateway not responding

**URL:** https://community.homey.app/t/api-gateway-not-responding/148918
**Category:** Homey Self-Hosted Server
**Created:** [January 9, 2026, 4:39pm UTC](https://community.homey.app/t/api-gateway-not-responding/148918 "2026-01-09T16:39:30Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Garrett\_Gauthier](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/garrett_gauthier/32/121867_2.png) [@Garrett\_Gauthier](https://community.homey.app/u/Garrett_Gauthier)
#### Post date: [January 9, 2026, 4:39pm UTC](https://community.homey.app/t/api-gateway-not-responding/148918/1 "2026-01-09T16:39:30Z")

</div>

I migrated from HomeyPro to SHS and everthing seemed fine except the api gateway is not responding. I used node-red and I get this error:  
failed, reason: connect ECONNREFUSED x.x.x.x (Valid IP address just masked for this note)

Repoint to HomeyPro and chnage to the API key for it fine. CHange back to SHS and change to the new API key same error. In postman when I do a simple get devices the SHS just times out. I am using the script from Homey for RaspberryPi 5 to start the container so no docker compose file, just their open systemd daemon to start ShS.

---

<div class="post-metadata">

### Author: ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [January 9, 2026, 4:47pm UTC](https://community.homey.app/t/api-gateway-not-responding/148918/2 "2026-01-09T16:47:22Z")

</div>

You know SHS is not listening on the default 80 and 443 ports?

---

<div class="post-metadata">

### Author: ![Garrett\_Gauthier](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/garrett_gauthier/32/121867_2.png) [@Garrett\_Gauthier](https://community.homey.app/u/Garrett_Gauthier)
#### Post date: [January 9, 2026, 10:17pm UTC](https://community.homey.app/t/api-gateway-not-responding/148918/3 "2026-01-09T22:17:27Z")

</div>

Ok so I just fiqured out yes Homey SHS is not listening on the normal ports that HomeyPro did, so I found out its port 4859. So using postman I now can connect and get status. But the Nodered library seems to have an issue with the new path. Somehow I did not see this in the SHS docuemntation that API access is a differnet port.

---

<div class="post-metadata">

### Author: ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [January 10, 2026, 6:01am UTC](https://community.homey.app/t/api-gateway-not-responding/148918/4 "2026-01-10T06:01:01Z")

</div>

All the ports are documented here:  
[https://support.homey.app/hc/en-us/articles/24010537261980-How-to-install-Homey-Self-Hosted-Server-with-Docker-on-Linux](https://support.homey.app/hc/en-us/articles/24010537261980-How-to-install-Homey-Self-Hosted-Server-with-Docker-on-Linux)
