Init with proxy

[pebl-hank]

So this worked fine for a while. All of the sudden I noticed today, that all nodes show "Init with proxy...". Initialization does not work. Re-authentication seems to be working, but results in the same "Init with proxy". All log entry I get is 28 Oct 18:31:04 - [info] [alexa-remote-account:Amazon xxx] intialising "Amazon xxx" with the PROXY method and saved data... Any ideas?

[cymplecy]

Same issue with me today :(

[mdte123]

Same for me.

On Fri, 28 Oct 2022, 18:54 Simon Walters, @.***> wrote:

Same issue with me today :(

— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/92#issuecomment-1295290416, or unsubscribe https://github.com/notifications/unsubscribe-auth/AULQR2FMTCXSFU6SM4GKJITWFQHMJANCNFSM6AAAAAARRHKK3Y . You are receiving this because you are subscribed to this thread.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/92/1295290416 @github.com>

[obaldius]

Same problem here, connected from Spain

[Amokd0c]

same here, connected from germany Also the same, when i add a 2 behind "auth" in filename. Open IP:3456 in browser works, and I can enter username and password. but Open ... in browser is still visible...

[x-MaxG-x]

same here, connected from germany Also the same, when i add a 2 behind "auth" in filename. Open IP:3456 in browser works, and I can enter username and password. but Open ... in browser is still visible...

Same for me here - the authentication in the browser looks like completed, but no file on disc is writen. Two other accounts, which I use in parallel are still working fine - guess the stored cookie is still valid.

[Amokd0c]

same here, connected from germany Also the same, when i add a 2 behind "auth" in filename. Open IP:3456 in browser works, and I can enter username and password. but Open ... in browser is still visible...

Same for me here - the authentication in the browser looks like completed, but no file on disc is writen. Two other accounts, which I use in parallel are still working fine - guess the stored cookie is still valid.

Maybe it is a problem with the amazon servers? Authentication works, but thats all Is this the correct path of the auth file? /opt/iobroker/node_modules/iobroker.node-red My renamed file wasn´t placed there also

Mehr wie warten wird uns net übrig bleiben! :) Mein 2tes auth file wurde nicht angelegt, deswegen bin ich mir net sicher ob das der richtige Pfad ist. Stimmt der? Das bestehende hab ich auch noch nicht gelöscht...

[Tinbum1]

same for me in UK

[bbindreiter]

Will check tomorrow. Looks like they changed something that we're listening to when authenticating.

[biddster]

I had this. I jumped onto the my node-red box and bumped alexa-remote2 to the latest version and I'm back working.

https://github.com/Apollon77/alexa-remote/releases/tag/v5.8.3

There's a fix in 5.8.3 Fix retry issues for rate limited responses from amazon which looks interesting.

[obaldius]

I had this. I jumped onto the my node-red box and bumped alexa-remote2 to the latest version and I'm back working.

https://github.com/Apollon77/alexa-remote/releases/tag/v5.8.3

There's a fix in 5.8.3 Fix retry issues for rate limited responses from amazon which looks interesting.

Can you be more specific?

Which archives did you replace with the newest version?

[Amokd0c]

the last available release in the palett manager provides the 5.0.21 Version

[brunialti]

So this worked fine for a while. All of the sudden I noticed today, that all nodes show "Init with proxy...". Initialization does not work. Re-authentication seems to be working, but results in the same "Init with proxy". All log entry I get is 28 Oct 18:31:04 - [info] [alexa-remote-account:Amazon xxx] intialising "Amazon xxx" with the PROXY method and saved data... Any ideas?

Same for me in Italy. I created a new alexa server. As usual I get "open xx.xx.xx.xx:3456 in your browser" message. After the new login nothing happens for a while, that is the node is flashing the above mentioned message. At this point if I try again to log in I get the error ERR_CONNECTION_RESET In my nodered 3 the latest version is 5.0.21, same as the one that appears in the NR contrib page https://flows.nodered.org/node/node-red-contrib-alexa-remote2-applestrudel No idea how to update it, should any update be available.

[bbindreiter]

I am unable to reproduce the issue, it does work for me. Emptied my cookie file, Proxy Auth. After logging in the new cookie was written in the file. I am using pitangui.amazon.com

Nevertheless, I am updating to the latest alexa-remote lib (5.8.3) and will publish a new version of applestrudel in a minute, please everyone, report back whether it works -> 5.0.22

[x-MaxG-x]

Thank you for the fast reaction - I can confirm, that the update to 5.0.22 (lib 8.5.3) solved the issue for me.

[brunialti]

The new 5.0.22 version works correctly for me.

[pebl-hank]

Awesome, version bump worked fine. Thanks for the quick response!

[bbindreiter]

Good news, thanks! 👍

[pebl-hank]

Closing the issue.

[cymplecy]

update to 5.0.22 has fixed the issue for me also - thanks for quick response :)

[obaldius]

Working again. @bbindreiter took this project to the next level, before him it used to fail way way more often, Thanks a lot for the lighthing fast response.

[bbindreiter]

Thank you but it's really @Apollon77 who does 99.99% of the work.

[dajuly20]

Had the same issues, also germany. Now soled with updating :)

[FrankGiesecke]

I had the same problem in Germany after leaving DST. After updating from version 5.0.21 to version 5.0.22 everything works fine.

Thanks folks for your support.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.