# Cannot access https://my.homey.app/login

**URL:** <https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356>\
**Category:** Questions & Help\
**Tags:** homey-pro\
**Created:** [January 26, 2024, 1:49pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356 "2024-01-26T13:49:10Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc\_Jurriens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_jurriens/32/11951_2.png) [@Marc\_Jurriens](https://community.homey.app/u/Marc_Jurriens)\
**Post date:** [January 26, 2024, 1:49pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/1 "2024-01-26T13:49:10Z")

</div>

For some reason it appears that I cannot access my Homey via the web anymore..

I am used to going to [My Homey](https://my.homey.app/login) to get to my flows ..

Am getting a privac warning now:

# Your connection isn’t private

Attackers might be trying to steal your information from **my.homey.app** (for example, passwords, messages or credit cards).

NET::ERR\_CERT\_COMMON\_NAME\_INVALID

What could be wrong ?

---

<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 26, 2024, 1:51pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/2 "2024-01-26T13:51:24Z")

</div>

Antivirus software, corporate firewall, etc.

---

<div class="post-metadata">

**Author:** ![Marc\_Jurriens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_jurriens/32/11951_2.png) [@Marc\_Jurriens](https://community.homey.app/u/Marc_Jurriens)\
**Post date:** [January 26, 2024, 1:53pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/3 "2024-01-26T13:53:38Z")

</div>

At home, pihole, also when disabled. Webroot. no indication from there.

Same issue off safari using my iphone (indicates SSL error), so not related to windows/microsoft.

---

<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 26, 2024, 2:21pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/4 "2024-01-26T14:21:15Z")

</div>

Check the certificate to see who issued it:

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

Also, did you try from your iPhone through a mobile network (not on your home network)?

---

<div class="post-metadata">

**Author:** ![Marc\_Jurriens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_jurriens/32/11951_2.png) [@Marc\_Jurriens](https://community.homey.app/u/Marc_Jurriens)\
**Post date:** [January 26, 2024, 2:33pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/5 "2024-01-26T14:33:56Z")

</div>

That last one… great catch…

From mobile to my.homey.app works … !

No idea what could be in between though… This worked like last week…

---

<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 26, 2024, 2:35pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/6 "2024-01-26T14:35:06Z")

</div>

The actual certificate that’s being returned might provide a clue.

---

<div class="post-metadata">

**Author:** ![Marc\_Jurriens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_jurriens/32/11951_2.png) [@Marc\_Jurriens](https://community.homey.app/u/Marc_Jurriens)\
**Post date:** [January 26, 2024, 2:36pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/7 "2024-01-26T14:36:27Z")

</div>

Can you make sense of this maybe ?

Subject: \*.homey.homeylocal.com

Issuer: R3

Expires on: 21 Mar 2024

Current date: 26 Jan 2024

PEM encoded chain:  
-----BEGIN CERTIFICATE-----

bla

-----END CERTIFICATE-----

Certificate Transparency:

SCT Google ‘Argon2024’ log (Embedded in certificate, Verified)

SCT Let’s Encrypt ‘Oak2024H1’ log (Embedded in certificate, Verified)

---

<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 26, 2024, 2:46pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/8 "2024-01-26T14:46:53Z")

</div>

> [@Marc\_Jurriens](#):
>
> Subject: \*.homey.homeylocal.com

And that’s the certificate you get for `my.homey.app`? Can you check what IP address `my.homey.app` resolves to?

---

<div class="post-metadata">

**Author:** ![Marc\_Jurriens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_jurriens/32/11951_2.png) [@Marc\_Jurriens](https://community.homey.app/u/Marc_Jurriens)\
**Post date:** [January 26, 2024, 2:51pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/9 "2024-01-26T14:51:04Z")

</div>

that is 192.168.2.67 which is the ip of my homeypro…

But that triggered me…

I had a local DNS record to get to my.homey.app … It has been there for ages… Do not quite remember why I needed it times ago… But I just removed it and it works now 🙂

---

<div class="post-metadata">

**Author:** ![Marc\_Jurriens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_jurriens/32/11951_2.png) [@Marc\_Jurriens](https://community.homey.app/u/Marc_Jurriens)\
**Post date:** [January 26, 2024, 2:51pm UTC](https://community.homey.app/t/cannot-access-https-my-homey-app-login/102356/10 "2024-01-26T14:51:15Z")

</div>

Thanks !!!
