Registration problem

[dbunic]

Hi, my guess is, this issue and few previous are maybe related due to possible API change on the Signal server side. In my case first step with request-voice node (and captcha) went OK. I received call to my landline and I got registration code. The problem comes in registration node. After clicking on registration node for the first time I got the following message in Node-RED debug window:

9/8/2021, 1:05:54 PM node: haus registration
msg : string[23]
"Signal client error: {}"
9/8/2021, 1:05:55 PM node: http response
msg : error
"Error: Cannot set headers after they are sent to the client"
9/8/2021, 1:05:55 PM node: http response
msg : error
"Error: Cannot set headers after they are sent to the client"
9/8/2021, 1:05:55 PM node: http response
msg : error
"Error: Cannot set headers after they are sent to the client"
9/8/2021, 1:05:57 PM node: http response
msg : error
"Error: Cannot set headers after they are sent to the client"

Second and every other click on the registration node gives the following answer in debug window:

msg : string[107]
"Signal client error: {"name":"HTTPError","code":403,"response":{"code":403,"message":"HTTP 403 Forbidden"}}"

I also tried with simpler password but the result is the same. Hope this feedback will be helpful to fix Signal client in Node-RED. I can provide more data if needed.

Thank you very much for a such great Node-RED contribution and I hope this issue will be resolves soon.

Kind regards

[cameo69]

You may want to have a look into https://github.com/gausma/nodered-contrib-signal-client/issues/29#issuecomment-916272232. The component seems to have issues right now.

[dbunic]

Thank you @cameo69 for your info. Your solution is very useful in case of bypassing this Node-RED component. In my case with only Raspberry Pi 1 Model B+ (and its limited resources) I can't use dockerized REST API around signal-cli. For my need to send once a while a Signal message is enough to use some free web API and currently I'm testing this setup. Of course this is still a workaround solution until this component will be fixed. Hope @gausma will give us some feedback soon.

Cheers!

[cthompstone]

Hi dbunic, I recommend you test out: node-red-contrib-matrixbot-markdown. I am trying to migrate away from the signal node to this, since it seems better. (although I'd prefer to stay with the signal node, if it was fully working and worked with node-red ver 2.x properly) With this matrix node and using the matrix.org server, it seems to work best with end to end encryption off. Chris

[tuxedo0801]

Instead of switching to other solutions: Why not fix the issue? @gausma Can you pls. have a look at it?

[Carsten3P]

I´m hahaving the same issue with Error 403. @gausma can you please help. Carsten

[JsBergbau]

@gausma: Would be great if you can have a look, since registration is currently not possible and node can't be used.