# 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:** 15
**Page:** 2
### Author:  [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 20, 2026, 2:02pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/21 "2026-01-20T14:02:28Z")
This is the inconsistency I pointed out above. I assure you (and it makes sense) that you can use the external port of your choice via reverse proxy. It works.
---
### Author:  [@RonnyW](https://community.homey.app/u/RonnyW)
#### Post date: [January 20, 2026, 8:01pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/22 "2026-01-20T20:01:18Z")
I think the Homey app just uses default port 443 and exchanges the url.
If you are using a simple DynDNS and port forward, then you habe to use a separate port for every internal service on the www side of your router.
But for reverse proxy, you only forward one port (443) to the proxy. Then use single subdomains for each dervice like [shs.mydomain.com:443](http://shs.mydomain.com:443). And the proxy maps the (sub)domain to your internal IP/port.
So it’s not neccessary to use another port than 443. Just use 443 with a Letsencrypt certificate and all is fine.
---
### Author:  [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 20, 2026, 9:02pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/23 "2026-01-20T21:02:53Z")
> [@RonnyW](#):
>
> I think the Homey app just uses default port 443 and exchanges the url.
`I think the Homey app just uses default port 443 and exchanges the url.`
Wrong: you can specify your fqnn+port on homey.app website.
`But for reverse proxy, you only forward one port (443) to the proxy.`
Wrong too. Your fw this for the challenge, for example.
`So it’s not neccessary to use another port than 443. Just use 443 with a Letsencrypt certificate and all is fine.`
Need 443 of other services. As proved, homey supports https on different ports, and that’s all I was solving before.
---
### Author:  [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)
#### Post date: [January 20, 2026, 9:23pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/24 "2026-01-20T21:23:58Z")
Nice, could also explain how to connect the Homey app on your smartphone when not using the default port?
---
### Author:  [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 20, 2026, 9:35pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/25 "2026-01-20T21:35:51Z")
Once you configured [on homey.app](https://support.homey.app/hc/en-us/articles/24060221985436-Setting-up-a-Custom-Domain-for-Homey-Self-Hosted-Server) (fqdn+port), it’s automatic.
---
### Author:  [@RonnyW](https://community.homey.app/u/RonnyW)
#### Post date: [January 21, 2026, 6:54am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/26 "2026-01-21T06:54:55Z")
> [@inDomus\_Crew](#):
>
> Wrong: you can specify your fqnn+port on homey.app website
That’s only your assumption. There is only written about adding a domain name to SHS settings. There is no input field for port and no hint about it. It just says it’s using 443 as default.
So if you add a port to your URL, it will be a wrong URI if Homey app is using 443.
---
### Author:  [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 21, 2026, 7:50am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/27 "2026-01-21T07:50:30Z")
🙄 It’s not my guess. I’m currently using it on port 9000 - as explained [here](https://indomus.it/guide/collegarsi-da-remoto-a-homey-self-hosted-server-via-reverse-proxy/).
---
### Author:  [@RonnyW](https://community.homey.app/u/RonnyW)
#### Post date: [January 21, 2026, 10:05am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/28 "2026-01-21T10:05:23Z")
Ok, so it’s possible although not described 👍
---
### Author:  [@inDomus\_Crew](https://community.homey.app/u/inDomus_Crew)
#### Post date: [January 21, 2026, 10:17am UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/29 "2026-01-21T10:17:00Z")
Right, current official documentation is misleading.
---
### Author:  [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)
#### Post date: [January 21, 2026, 6:44pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/30 "2026-01-21T18:44:08Z")
I’d like to suggest to send your improvement ideas to [https://homey.app/support](https://homey.app/support)
---
### Author:  [@kMikaZu](https://community.homey.app/u/kMikaZu)
#### Post date: [July 20, 2026, 5:05pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/31 "2026-07-20T17:05:17Z")
I have similar problems. Even with the normal function _Port Forwarding_ both interface and manual mingle ports `4859` and `4860`, leaving it unclear what to use.
I’ve setup a NPM with a Proxy for my Homey Self Hosted Server. The dynamic domain hosted by. Infomaniak works perfectly, SSL certificate is ok. When I check my domain with a `curl` command, it reaches my NPM server.
When I change the Proxy to `http` with port `4859`, the Homey Local User login is reachable via the domain. https with `4860` doesn’t work.
Whatever I try, I get an error in My Homey Account, when I try to add the domain. I get a timeout every time.
---
### Author:  [@smarthomesven](https://community.homey.app/u/smarthomesven)
#### Post date: [July 20, 2026, 8:30pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/32 "2026-07-20T20:30:20Z")
Did you know that Homey SHS is also reachable remotely without opening any ports? Using Homey’s built-in server connection is more secure as well
---
### Author:  [@kMikaZu](https://community.homey.app/u/kMikaZu)
#### Post date: [July 20, 2026, 9:36pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/33 "2026-07-20T21:36:07Z")
Can you explain more please?
---
### Author:  [@smarthomesven](https://community.homey.app/u/smarthomesven)
#### Post date: [July 20, 2026, 9:40pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/34 "2026-07-20T21:40:39Z")
For Homey SHS, no port forwarding is required. By default, Homey already has a secure remote connection that you can use. If you switch to a different network, you can still use the my.homey.app webapp and Homey mobile app.
---
### Author:  [@kMikaZu](https://community.homey.app/u/kMikaZu)
#### Post date: [July 20, 2026, 10:13pm UTC](https://community.homey.app/t/shs-on-reverse-proxy/149551/35 "2026-07-20T22:13:28Z")
That default option is extremely slow and unreliable…
[Previous page](https://community.homey.app/t/shs-on-reverse-proxy/149551.md?page=1)