Skip to content
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

Closed
bobbolous opened this issue Feb 5, 2024 · 8 comments
Closed

Addon suddenly stopped working, no connection to local server #84

bobbolous opened this issue Feb 5, 2024 · 8 comments

Comments

@bobbolous
Copy link

bobbolous commented Feb 5, 2024

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:

curl -X GET -H "Content-Type: application/json" 'http://127.0.0.1:8080/v1/qrcodelink?device_name=HomeAssistant'
curl: (7) Failed to connect to 127.0.0.1 port 8080 after 0 ms: Couldn't connect to server

Around the same time this issue here appeared:
bbernhard/signal-cli-rest-api#475

and that points to this issue:
AsamK/signal-cli#1439

@alfwro13
Copy link

alfwro13 commented Feb 5, 2024

yep, same problem here

@haberda
Copy link
Owner

haberda commented Feb 6, 2024

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

@haberda
Copy link
Owner

haberda commented Feb 6, 2024

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:

curl -X GET -H "Content-Type: application/json" 'http://127.0.0.1:8080/v1/qrcodelink?device_name=HomeAssistant'
curl: (7) Failed to connect to 127.0.0.1 port 8080 after 0 ms: Couldn't connect to server

Around the same time this issue here appeared: bbernhard/signal-cli-rest-api#475

and that points to this issue: AsamK/signal-cli#1439

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

@bobbolous
Copy link
Author

Thanks for pointing that out.
Just for reference, now I receive this error:

curl -X GET -H "Content-Type: application/json" 'http://homeassistant.local:8080/v1/qrcodelink?device_name=HomeAssistant'
{"error":"Couldn't create QR code: no data to encode"}

@derjoerg
Copy link

derjoerg commented Feb 6, 2024

Hi @haberda,
can you update the signal-messenger addon to the latest release 0.81 to fix the current issues?

@haberda
Copy link
Owner

haberda commented Feb 6, 2024

Fix is published

@derjoerg
Copy link

derjoerg commented Feb 6, 2024

It works!
Thanks a lot!

@bobbolous
Copy link
Author

Works! Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants