mike-grant / haaska

Home Assistant Alexa Skill Adapter that supports v3 of the Alexa Smart Home Skill API
MIT License
533 stars 114 forks source link

Getting Error 401 Client Error: Unauthorized for url #170

Open aryedevops opened 4 years ago

aryedevops commented 4 years ago

Hi,

First I want to thank you for the hasskaskill and the well explained wikifor installing it!

My setup: Home Assistant Docker using : image: homeassistant/qemux86-64-homeassistant:0.111.4 Haaska: latest zip Traefik docker as my Reverse Proxy to https://hass.mydomain.duckdns.org to the above docker on port 8123 using rules.tomel.

I have created a Long Lived Access Token on my HA (several times with no luck on each) Everything looks OK and setting were checked a couple of times. I have added the config json with my url https://hassio.aryeduino.duckdns.org and edit my Long Lived Access Token as well. Saved it and created a test with the same example given in the wiki. with NO luck!!

I have followed everything in the wiki till the end and I am trying to test and getting the following error:

{
  "errorMessage": "401 Client Error: Unauthorized for url: https://hassio.aryeduino.duckdns.org/api/alexa/smart_home",
  "errorType": "HTTPError",
  "stackTrace": [
    [
      "/var/task/haaska.py",
      111,
      "event_handler",
      "return ha.post('alexa/smart_home', event, wait=True)"
    ],
    [
      "/var/task/haaska.py",
      66,
      "post",
      "r.raise_for_status()"
    ],
    [
      "/var/task/requests/models.py",
      940,
      "raise_for_status",
      "raise HTTPError(http_error_msg, response=self)"
    ]
  ]
}

Please assist me understand what i am doing wrong? or am I missing something? Would be happy to get reply soon.

Thank you. Arye

tal2420 commented 3 years ago

I know that it's an old issue but for future cases - I had the same problem and found out that HA had added the origin IP (ip_bans.yaml) so it wasn't able to access HA API's.

tekstein commented 2 years ago

I know that it's an old issue but for future cases - I had the same problem and found out that HA had added the origin IP (ip_bans.yaml) so it wasn't able to access HA API's.

Where did HA add the IP address? I'm having the issue and I can't find the ip_bans.yaml