# Port forwarding to avoid cloud, not working

**URL:** <https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470>\
**Category:** Questions & Help\
**Tags:** homey-pro\
**Created:** [August 16, 2024, 9:49am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470 "2024-08-16T09:49:04Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![focus11](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focus11/32/77613_2.png) [@focus11](https://community.homey.app/u/focus11)\
**Post date:** [August 16, 2024, 9:49am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/1 "2024-08-16T09:49:04Z")

</div>

Hi all!  
I did port forwarding exactly as in the instructions on the official web page ([Port Forwarding is now live | Homey News](https://homey.app/en-us/news/port-forwarding-is-now-live/)), but the connection type still shows that it is connected via the cloud, regardless of whether I access homey from an Android smartphone or from a PC (W10+Chrome).  
Does anyone know if I need to do anything extra?!

 ![pfw](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/f/2f2e8153a817791acdda324f12ce698ca0808c37.jpeg)

---

<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:** [August 16, 2024, 10:00am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/2 "2024-08-16T10:00:37Z")

</div>

Are you trying to access Homey from outside your home network?

---

<div class="post-metadata">

**Author:** ![focus11](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focus11/32/77613_2.png) [@focus11](https://community.homey.app/u/focus11)\
**Post date:** [August 16, 2024, 10:01am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/3 "2024-08-16T10:01:34Z")

</div>

Yes, at this moment I am not at home

---

<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:** [August 16, 2024, 10:02am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/4 "2024-08-16T10:02:03Z")

</div>

And does your home internet connection have a (semi-)static external IP address?

---

<div class="post-metadata">

**Author:** ![focus11](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focus11/32/77613_2.png) [@focus11](https://community.homey.app/u/focus11)\
**Post date:** [August 16, 2024, 10:07am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/5 "2024-08-16T10:07:18Z")

</div>

What you mean “(semi-)static external IP address”?  
I opened the ports in my router like in tutorial, and I have DDNS on two servers, but I don’t know if it matters. On LAN Homey device are alocated static IP.

---

<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:** [August 16, 2024, 10:10am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/6 "2024-08-16T10:10:34Z")

</div>

> [@focus11](#):
>
> What you mean “(semi-)static external IP address”?

That your internet provider doesn’t use CGNAT.

Can you access the configured port (4859) from outside of your network? It should be testable in a regular browser (`https://your.external.ip.address:4859/`).

---

<div class="post-metadata">

**Author:** ![focus11](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focus11/32/77613_2.png) [@focus11](https://community.homey.app/u/focus11)\
**Post date:** [August 16, 2024, 10:13am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/7 "2024-08-16T10:13:09Z")

</div>

No it’s not working. In this case I have to try another 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:** [August 16, 2024, 10:14am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/8 "2024-08-16T10:14:55Z")

</div>

You can try, but there’s also a chance that your internet provider simply doesn’t allow this.

---

<div class="post-metadata">

**Author:** ![focus11](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focus11/32/77613_2.png) [@focus11](https://community.homey.app/u/focus11)\
**Post date:** [August 16, 2024, 10:18am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/9 "2024-08-16T10:18:49Z")

</div>

Now I checked on a specialized website if the port is open or not, on that DDNS user and I notice that it is open, but if I try to access it from the browser, the page does not open

---

<div class="post-metadata">

**Author:** ![focus11](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focus11/32/77613_2.png) [@focus11](https://community.homey.app/u/focus11)\
**Post date:** [August 16, 2024, 10:21am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/10 "2024-08-16T10:21:43Z")

</div>

It shows the same on the other DDNS account

---

<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:** [August 16, 2024, 10:30am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/11 "2024-08-16T10:30:44Z")

</div>

It works fine in a browser:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/e/3e885d633497a1156c611c8e39971fa4637d6bc7.png)

But it does give a certificate issue (which is to be expected).

When you said _“No it’s not working”_, what’s the specific error that you got?

> Edit: Removed DDNS name on request Topic Owner. by @Dijker

---

<div class="post-metadata">

**Author:** ![focus11](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focus11/32/77613_2.png) [@focus11](https://community.homey.app/u/focus11)\
**Post date:** [August 16, 2024, 10:37am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/13 "2024-08-16T10:37:35Z")

</div>

The port 443 appears as closed. Maybe that should be opened too or should I use another internal 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:** [August 16, 2024, 10:40am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/14 "2024-08-16T10:40:15Z")

</div>

This seems to be a local (where you are now) issue, because I can connect to _your_ Homey just fine (which means port forwarding _is_ working).

---

<div class="post-metadata">

**Author:** ![focus11](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focus11/32/77613_2.png) [@focus11](https://community.homey.app/u/focus11)\
**Post date:** [August 16, 2024, 10:41am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/15 "2024-08-16T10:41:20Z")

</div>

I am to work and is possible that my company have some restrictions…

---

<div class="post-metadata">

**Author:** ![focus11](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focus11/32/77613_2.png) [@focus11](https://community.homey.app/u/focus11)\
**Post date:** [August 16, 2024, 10:41am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/16 "2024-08-16T10:41:53Z")

</div>

I’m sorry I have to go and won’t be online for a while. I’ll come back later and maybe we can find a solution.  
Thank you for the answers!

---

<div class="post-metadata">

**Author:** ![Rmb](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rmb/32/79135_2.png) [@Rmb](https://community.homey.app/u/Rmb)\
**Post date:** [August 16, 2024, 10:49am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/17 "2024-08-16T10:49:17Z")

</div>

> [@robertklep](#):
>
> That your internet provider doesn’t use CGNAT.

That your external/public ip address is always the same. So you can call home always using the same address. Other wise you have to look up that address en configure that every time you want to call home.

---

<div class="post-metadata">

**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\
**Post date:** [August 16, 2024, 10:51am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/18 "2024-08-16T10:51:58Z")

</div>

Oh, wow, this returns something identified as “homeyId”… is that the real ID or a faux just for this session I wonder…

And also nice to include a firmware version, so ~~hackers~~ , script kiddies, can easily search for unpatched homeys, saves them some work…

---

<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:** [August 16, 2024, 11:00am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/19 "2024-08-16T11:00:06Z")

</div>

> [@DaneedeKruyff](#):
>
> Oh, wow, this returns something identified as “homeyId”… is that the real ID or a faux just for this session I wonder…

That’s the real ID.

Makes it real easy to search for too:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/2/b2d78ca02554d35009e6f24f84cceb4dc068c922.png)

---

<div class="post-metadata">

**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\
**Post date:** [August 16, 2024, 11:07am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/20 "2024-08-16T11:07:35Z")

</div>

Wow…

Imagine how many homey users may have this enabled without fully understanding the implications.

---

<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:** [August 16, 2024, 11:10am UTC](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470/21 "2024-08-16T11:10:24Z")

</div>

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/2/e2a15b7ca85843fb356117c83000899bf3d4a268.png)

[Next page](https://community.homey.app/t/port-forwarding-to-avoid-cloud-not-working/114470.md?page=2)
