# SHS on reverse proxy

**URL:** https://community.homey.app/t/shs-on-reverse-proxy/149551
**Category:** Questions & Help
**Tags:** homey-shs
**Created:** [January 19, 2026, 9:00am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551 "2026-01-19T09:00:23Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 19, 2026, 9:00am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/1 "2026-01-19T09:00:23Z")

</div>

Hi there,

There is something we don’t understand. We have Caddy correctly configured, including the necessary port forwarding rules on the modem/router, capable of routing requests for http:// mydomain. example. com to services within our LAN. If we configure something very simple, like:

`mydomain.example.com { `  
` reverse_proxy HOMEY_LAN_IP:4859`  
`}`

we can reach Homey remotely at https:// mydomain. example. com.  
Instead, if we try to use a configuration with a specific high port:

`mydomain.example.com:9000 { `  
` reverse_proxy HOMEY_LAN_IP:4859`  
`}`

the address https:// mydomain. example. com:9000 does **not** respond.

According to this article: [https://support.homey.app/hc/en-us/articles/24060221985436- **Setting-up-a-Custom-Domain-for-Homey-Self-Hosted-Server**](https://setting%20up%20a%20custom%20domain%20for%20homey%20self-hosted%20server) it seems that Homey SHS can only respond on port 443.

Is that correct?

---

<div class="post-metadata">

### Author: ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)
#### Post date: [January 19, 2026, 9:03am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/2 "2026-01-19T09:03:34Z")

</div>

> [@inDomus\_Crew](#):
>
> HOMEY\_LAN\_IP:4869

The SHS port is 4859, not 4869.

---

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 19, 2026, 9:37am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/3 "2026-01-19T09:37:57Z")

</div>

just a typo, now corrected.

---

<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 19, 2026, 9:40am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/4 "2026-01-19T09:40:48Z")

</div>

Is port 9000 being forwarded correctly? Can you access port 9000 on the server running Caddy from your internal network?

---

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 19, 2026, 9:42am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/5 "2026-01-19T09:42:21Z")

</div>

of course, once you configure :9000 @caddy, 9000 is listening.

---

<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 19, 2026, 9:44am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/6 "2026-01-19T09:44:07Z")

</div>

That leaves my first question: is port 9000 being forwarded correctly?

---

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 19, 2026, 9:54am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/7 "2026-01-19T09:54:39Z")

</div>

yes

---

<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 19, 2026, 10:05am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/8 "2026-01-19T10:05:32Z")

</div>

So what happens exactly when you try to access the server?

---

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 19, 2026, 10:17am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/9 "2026-01-19T10:17:26Z")

</div>

This site can’t be reached  
mydomain. example. com refused to connect.

ERR\_CONNECTION\_REFUSED

---

<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 19, 2026, 10:18am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/10 "2026-01-19T10:18:01Z")

</div>

Sounds like a configuration issue in your router then.

---

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 19, 2026, 10:22am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/11 "2026-01-19T10:22:27Z")

</div>

no way, it’s not a router side problem. same config perfectly works with home assistant.

---

<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 19, 2026, 10:25am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/12 "2026-01-19T10:25:29Z")

</div>

But you said that port 9000 is accessible from inside your network, just not outside. And the only thing in between the outside and the inside is your router.

---

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 19, 2026, 10:40am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/13 "2026-01-19T10:40:08Z")

</div>

port forwarding of port 9000 is ok, let’s forget it.

can you answer the question I asked in my first post?

---

<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 19, 2026, 10:42am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/14 "2026-01-19T10:42:47Z")

</div>

> [@inDomus\_Crew](#):
>
> Is that correct?

No.

---

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 19, 2026, 10:56am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/15 "2026-01-19T10:56:16Z")

</div>

so, why: “In your reverse proxy, point to `http://<ip-of-homey>:4859`. Please refer to your reverse proxy’s manual on how to configure this.

Make sure that the reverse proxy issues a certificate, that it listens on port 443 (HTTPS), and that WebSocket support is enabled.”

---

<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 19, 2026, 11:04am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/16 "2026-01-19T11:04:06Z")

</div>

You asked “_it seems that **Homey SHS** can only respond on port 443_”, and I answered: that’s not correct. Homey SHS only responds to ports 4859 (HTTP) and 4860 (HTTPS).

You’re now asking about the _reverse proxy_ listening on port 443, which is something else.

That’s why I asked if port 9000 worked in your local network, because if it does, it’s not an issue with the reverse proxy setup.

ERR\_CONNECTION\_REFUSED is a sign that either your router or your reverse proxy aren’t set up correctly. Even if, for some reason, Homey SHS depends on being accessed through a reverse proxy on port 443, you should not get that specific error if port forwarding and reverse proxy are set up properly.

---

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 19, 2026, 11:20am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/17 "2026-01-19T11:20:46Z")

</div>

Solved. The problem was about caddy’s docker container, port 9000 wasn’t added in the list.

Thanks

---

<div class="post-metadata">

### Author: ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)
#### Post date: [January 20, 2026, 7:49am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/18 "2026-01-20T07:49:35Z")

</div>

I’m also using the reverse proxy configuration.

The Homey app will check this setting and use the own domain directly instead of cloud access.

But as written it’s using port 443. So you have to use port 443 for accessing your router from the www. If you are already using this port for something else, use a subdomain like [shs.mydomain.com](http://shs.mydomain.com) in your provider/domain settings and forward this subdomain to your router.

Then add port forwarding for port 443 to your reverse proxy.

In reverse proxy, forward the specific subdomain to your SHS.

I’m using Nginx reverse proxy this way.

---

<div class="post-metadata">

### Author: ![inDomus\_Crew](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/indomus_crew/32/152256_2.png) [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 20, 2026, 8:24am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/19 "2026-01-20T08:24:03Z")

</div>

> [@RonnyW](#):
>
> So you have to use port 443 for accessing your router from the www.

Wrong, as a matter of fact you can use the port you desire, when using a reverse proxy.

---

<div class="post-metadata">

### Author: ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)
#### Post date: [January 20, 2026, 12:03pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/20 "2026-01-20T12:03:56Z")

</div>

![Screenshot_20260120_130315_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/9/c9e4067c7e718f47a70c87f1d4991daf6fb46bf8.jpeg)

[Next page](https://community.homey.app/t/shs-on-reverse-proxy/149551.md?page=2)
