search

Brandawg93 / homebridge-fordpass

Control your Ford vehicle in HomeKit using Homebridge.
GNU General Public License v3.0
61 stars 15 forks source link

[Bug]: Status failed with error: ENOTFOUND #167

Closed tornenen closed 2 years ago

tornenen commented 2 years ago

2022-01-12 14_24_35-Homebridge 975E und 12 weitere Seiten - Persönlich – Microsoft​ Edge

Describe the bug

2022-01-12 14_24_35-Homebridge 975E und 12 weitere Seiten - Persönlich – Microsoft​ Edge

Debug Output

2022-01-12 14_24_35-Homebridge 975E und 12 weitere Seiten - Persönlich – Microsoft​ Edge

Steps to reproduce

Device Type

Rapsberry Pi

iOS Version

15.2

Bug Persistence

Consistently

Last Working Version

No response

Brandawg93 commented 2 years ago

A few more questions:

  1. Just to confirm, this has never worked for you?
  2. Are you in the US?
  3. ENOTFOUND is typically a DNS issue. Are you able to ping https://sso.ci.ford.com/?
tornenen commented 2 years ago
  1. Just to confirm, this has never worked for you?
    • It still worked yesterday
  2. Are you in the US?
    • No, Germany
  3. ENOTFOUND is typically a DNS issue. Are you able to ping https://sso.ci.ford.com/?
    • Ive switched DNS 2 Days ago from 1.1.1.1 to 9.9.9.9, but i can ping this, and my homeassistant can still reach everything at ford.. Using this: itchannel/fordpass-ha: Fordpass integration for Home Assistant (github.com)https://github.com/itchannel/fordpass-ha

Von: Brandon McFarlin @.> Gesendet: Mittwoch, 12. Januar 2022 14:47 An: Brandawg93/homebridge-fordpass @.> Cc: Banko, Kenneth @.>; Author @.> Betreff: Re: [Brandawg93/homebridge-fordpass] [Bug]: Status failed with error: ENOTFOUND (Issue #167)

A few more questions:

  1. Just to confirm, this has never worked for you?
  2. Are you in the US?
  3. ENOTFOUND is typically a DNS issue. Are you able to ping https://sso.ci.ford.com/?

— Reply to this email directly, view it on GitHubhttps://github.com/Brandawg93/homebridge-fordpass/issues/167#issuecomment-1011062266, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASIL3CL32W63B5A7VEIXRK3UVWA3XANCNFSM5LY7GDRA. You are receiving this because you authored the thread.Message ID: @.**@.>>

Brandawg93 commented 2 years ago

If it worked yesterday, I'm not sure what could have changed on the plugin side to affect the functionality. There may be different urls for different regions, but it sounds like yours was already working.

rulerofthenight commented 2 years ago

Even mine was working yesterday, after the update that fixed 401 error, but today it won't work. As soon as I come back home I'll check if I have this error or the 401 error again. P.s. I'm in Europe (Italy)

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 3 days