-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addon suddenly stopped working, no connection to local server #84
Comments
yep, same problem here |
Signal changed something that broke the CLI. An update from the upstream project is required. When the upstream fix is available I will issue an update. Also see: 120 |
Also, those curl commands are not failing because the noted issue. Those are failing because you are using the localhost address which will only work inside the container. You need to use your home assistant machine's IP address instead of 127.0.0.1 |
Thanks for pointing that out.
|
Hi @haberda, |
Fix is published |
It works! |
Works! Thank you! |
Today out of nowhere I stopped receiving signal messages.
I did not change anything on the HAss server side or signal side.
I checked if I could send messages directly through the cli I receive the following:
Around the same time this issue here appeared:
bbernhard/signal-cli-rest-api#475
and that points to this issue:
AsamK/signal-cli#1439
The text was updated successfully, but these errors were encountered: