You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have my own Live server that is hosting multiple services in sub-domains.
Like -
ha.xx-cloud.ga for my Home Assistant
next.xx-cloud.ga for my Nextcloud
etc.
i have the same issue with a .casa tld.
I get it to work by changing line 46 in haaska.py from return f'{self.config.url}/api/{endpoint}'
to return f'https://ha.myurl.casa/api/{endpoint}'.
So you could try to change it to return f'https://ha.my-cloud.ga/api/{endpoint}'.
Hi all, I can confirm the same problem and the "solution" proposed by @TheEric0802 "fixed" the test. Hope there is a way to fix it in a more definitive way in the future
Hello,
I have my own Live server that is hosting multiple services in sub-domains.
Like -
ha.xx-cloud.ga for my Home Assistant
next.xx-cloud.ga for my Nextcloud
etc.
In the config.jason, I have this setting -
But, when I run the Lambda Test, it is giving this error all the time -
Pls note that 1st line, instate of ha.xx-cloud.ga, it is trying to connect ha.xx-cloud.g! .g instate of .ga!
No code modification is done at my end.
Pls suggest.
The text was updated successfully, but these errors were encountered: