# Improved api performance with port forwarding **URL:** \ **Category:** Questions & Help\ **Created:** [April 15, 2025, 1:53pm UTC](https://community.homey.app/t/improved-api-performance-with-port-forwarding/134735 "2025-04-15T13:53:54Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [April 15, 2025, 1:53pm UTC](https://community.homey.app/t/improved-api-performance-with-port-forwarding/134735/1 "2025-04-15T13:53:54Z")
A while ago I made my own Homey dashboard (I know about the existing Homey dashboard). Because the api performance with Homey cloud gives varying performance, and my Dashboard app can’t handle local addresses, I think the solution could be via Port forwarding. However, I can’t make a connection with Homey via Port forwarding. What have I already done/tried: - fixed IP address for Homey - port forwarding enabled in modem - firewall authorized for the default Homey port 4859 - Configured port forwarding in Homey, with a message that it is active when saving this; the operation of port forwarding is checked when activating. - requested my IP address with [Whatismyip.com](http://Whatismyip.com). - created an Api key in Homey - with Postman I request the following with GET: https://[[ip-address-from-Whatismyip.com](http://ip-address-from-Whatismyip.com)]:4859/api/manager/devices/device. I also set the Bearer Token with value: Bearer [api key] Postman response: Could not get response. Does anyone have any suggestions to make this work? (I’m not a network hero) ---
**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:** [April 15, 2025, 4:17pm UTC](https://community.homey.app/t/improved-api-performance-with-port-forwarding/134735/3 "2025-04-15T16:17:47Z")
In your firewall local port shall be 443 and external port shall be 4895 ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [April 15, 2025, 5:30pm UTC](https://community.homey.app/t/improved-api-performance-with-port-forwarding/134735/4 "2025-04-15T17:30:48Z")
[https://support.homey.app/hc/en-us/articles/16397583238556-Enabling-Port-Forwarding](https://support.homey.app/hc/en-us/articles/16397583238556-Enabling-Port-Forwarding) ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [April 16, 2025, 7:28am UTC](https://community.homey.app/t/improved-api-performance-with-port-forwarding/134735/5 "2025-04-16T07:28:49Z")
Even after a compete firewall deactivation I get the error in Postman: Could not get response: Error: write EPROTO 1071616:error:10000410:SSL routines:OPENSSL\_internal:SSLV3\_ALERT\_HANDSHAKE\_FAILURE:........\src\third\_party\boringssl\src\ssl\tls\_record.cc:592:SSL alert number 40 Using KPN Box 10 modem (fiber). Any suggestions I could try? ---
**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:** [April 16, 2025, 7:59am UTC](https://community.homey.app/t/improved-api-performance-with-port-forwarding/134735/6 "2025-04-16T07:59:49Z")
You cannot access Homey using your (external) IP address because TLS/SSL certificates are bound to domain names. You can try accessing it via this URL: ```auto https://AA-BB-CC-DD.homey.homeylocal.com:4859/api/manager/devices/device ``` Where AA/BB/CC/DD are the octets of your external IP address (in other words, if your external IP address is `12.34.56.78`, the URL becomes `https://12-34-56-78.homey.homeylocal.com...`)