# Node-red-contrib-alexa-remote2-applestrudel - error on amazon login page
**URL:** https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755
**Category:** General
**Tags:** function-node
**Created:** [12 April 2026 10:31 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755 "2026-04-12T10:31:08Z")
**Posts on this page:** 19
**Page:** 2
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [11 July 2026 14:07 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/21 "2026-07-11T14:07:12Z")
When you said automations don't work I did not realise that you meant contributed nodes.
I haven't used any of those nodes. I suspect any issues are more likely to be with nodejs versions rather than NR 5
---
### Author:  [@DiverRich](https://discourse.nodered.org/u/DiverRich)
#### Post date: [11 July 2026 20:24 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/22 "2026-07-11T20:24:24Z")
For what it's worth, I've had no problems since installing the temporary patch almost a month ago. I did eventually downgrade node.js to v22 so I could update other nodes that required it and I did update to the latest Apple Strudel and none of that broke the patch for me.
> Alternatively, there is [a temporary patch listed in the comments there](https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/254#issuecomment-4699587047) that should fix the cookie refresh bug if you don't want to downgrade node.js to v22. I'll report back in about 24 hours to let you know if the patch worked for me.
---
### Author:  [@franz](https://discourse.nodered.org/u/franz)
#### Post date: [19 July 2026 05:44 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/23 "2026-07-19T05:44:24Z")
Node-RED version: v4.1.10; Node.js version: v20.20.2. ; node-red-contrib-alexa-remote2-applestrudel 5.1.1 I’ve been using Applestrudel for a week and everything’s working properly again. Great!!
---
### Author:  [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)
#### Post date: [19 July 2026 07:13 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/24 "2026-07-19T07:13:40Z")
Thanks for the heads-up on v5.1.1
I've just updated to v5.1.1 on a RPi-4B running Node-RED version 4.1.10 with Node.js v18.20.8 and can confirm I can now send "text-to-voice" messages to my Alexa devices (again).
---
### Author:  [@Buckskin](https://discourse.nodered.org/u/Buckskin)
#### Post date: [19 July 2026 14:28 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/25 "2026-07-19T14:28:32Z")
I have all the latest bits & bobs and I can't even get Amazon the accept the [http://xx.xx.xx.xx:3456](http://xx.xx.xx.xx:3456) login
---
### Author:  [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)
#### Post date: [19 July 2026 18:55 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/26 "2026-07-19T18:55:28Z")
I found I had to change the Auth Method to Proxy (I normally use Cookie).
---
### Author:  [@DiverRich](https://discourse.nodered.org/u/DiverRich)
#### Post date: [19 July 2026 20:33 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/27 "2026-07-19T20:33:50Z")
> [@Buckskin](#):
>
> I have all the latest bits & bobs and I can't even get Amazon the accept the [http://xx.xx.xx.xx:3456](http://xx.xx.xx.xx:3456) login
I'm running Node-RED 5.0.1 with the ["temporary" patch](https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/254#issuecomment-4699587047) and it's working great. But seeing that others are still having issues is why I haven't updated to applestrudel 5.1.1 from 5.1.
It's probably worth mentioning that even though the issue was closed on GitHub it was revived as a new issue there. User fkhr79 (who came up with the temporary patch) has been working on figuring this out. Check out this post [here on GitHub](https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/265#issuecomment-4814139922) for more info on the on-going effort to tame this beast.
---
### Author:  [@Buckskin](https://discourse.nodered.org/u/Buckskin)
#### Post date: [20 July 2026 12:59 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/28 "2026-07-20T12:59:31Z")
Tried both proxy & cookie. This has been going on for nearly a year now. Amazon will not authorise the login (also tried [layla.amazon.amazon.co.uk](http://layla.amazon.amazon.co.uk) as well as [alexa.amazon.co.uk](http://alexa.amazon.co.uk))
If I use cookie to initialise the init node says 'success' but all the other nodes are still waiting and give
```auto
TypeError: res.writeHeader is not a function
at accountHttpResponse (/home/pi/.node-red/node_modules/node-red-contrib-alexa-remote2-applestrudel/nodes/alexa-remote-account.js:287:7)
at /home/pi/.node-red/node_modules/node-red-contrib-alexa-remote2-applestrudel/nodes/alexa-remote-account.js:604:118
at Layer.handle [as handle_request] (/usr/lib/node_modules/node-red/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/lib/node_modules/node-red/node_modules/express/lib/router/route.js:149:13)
at /usr/lib/node_modules/node-red/node_modules/@node-red/editor-api/lib/auth/index.js:69:28
at complete (/usr/lib/node_modules/node-red/node_modules/passport/lib/middleware/authenticate.js:280:13)
at /usr/lib/node_modules/node-red/node_modules/passport/lib/middleware/authenticate.js:287:15
at pass (/usr/lib/node_modules/node-red/node_modules/passport/lib/authenticator.js:446:14)
at Authenticator.transformAuthInfo (/usr/lib/node_modules/node-red/node_modules/passport/lib/authenticator.js:468:5)
at /usr/lib/node_modules/node-red/node_modules/passport/lib/middleware/authenticate.js:284:22
```
as an error message.
The Amazon log in sends me a Whatsapp code and then says the page is not available ????
---
### Author:  [@Johnnybegoode](https://discourse.nodered.org/u/Johnnybegoode)
#### Post date: [20 July 2026 15:19 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/29 "2026-07-20T15:19:44Z")
Same here, no way to login
---
### Author:  [@franz](https://discourse.nodered.org/u/franz)
#### Post date: [23 July 2026 13:06 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/30 "2026-07-23T13:06:22Z")
> [@Buckskin](#):
>
> ```auto
> TypeError: res.writeHeader is not a function
> at accountHttpResponse (/home/pi/.node-red/node_modules/node-red-contrib-alexa-remote2-applestrudel/nodes/alexa-remote-account.js:287:7)
> at /home/pi/.node-red/node_modules/node-red-contrib-alexa-remote2-applestrudel/nodes/alexa-remote-account.js:604:118
> at Layer.handle [as handle_request] (/usr/lib/node_modules/node-red/node_modules/express/lib/router/layer.js:95:5)
> at next (/usr/lib/node_modules/node-red/node_modules/express/lib/router/route.js:149:13)
> at /usr/lib/node_modules/node-red/node_modules/@node-red/editor-api/lib/auth/index.js:69:28
> at complete (/usr/lib/node_modules/node-red/node_modules/passport/lib/middleware/authenticate.js:280:13)
> at /usr/lib/node_modules/node-red/node_modules/passport/lib/middleware/authenticate.js:287:15
> at pass (/usr/lib/node_modules/node-red/node_modules/passport/lib/authenticator.js:446:14)
> at Authenticator.transformAuthInfo (/usr/lib/node_modules/node-red/node_modules/passport/lib/authenticator.js:468:5)
> at /usr/lib/node_modules/node-red/node_modules/passport/lib/middleware/authenticate.js:284:22
>
> ```
Firstly you must have applestrudel5.1.1, try clearing your cookies or re-authenticating via port 3456 (or whichever port you’ve set) in your browser’s incognito mode. If you’re using a proxy, do the same and delete the saved file. If it still doesn’t work, then do the following: go to `/home/pi/. node-red/node_modules/node-red-contrib-alexa-remote2-applestrudel/nodes/alexa-remote-account.js` and on line 287, replace res.writeHeader(...) with res.writeHead(...) It should work, but I don’t know how to make the change permanent.
---
### Author:  [@Buckskin](https://discourse.nodered.org/u/Buckskin)
#### Post date: [23 July 2026 20:42 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/31 "2026-07-23T20:42:09Z")
Tried all that. Got rid of the error message but when trying to log onto Amazon I got
```auto
Looking for Something?
We're sorry. The Web address you entered is not a functioning page on our site
```
---
### Author:  [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)
#### Post date: [24 July 2026 05:35 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/32 "2026-07-24T05:35:21Z")
This is how I trigger the Alexa node on my set-up...
The top `inject` node is set to trigger every 180 minutes (3 hrs). When the `Initialise` node is triggered it can take 5 to 6 seconds before it shows the success state.
I updated to v5.1.1, 5-days ago - fingers crossed all working fine since that date.
---
### Author:  [@franz](https://discourse.nodered.org/u/franz)
#### Post date: [24 July 2026 11:20 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/33 "2026-07-24T11:20:59Z")
> [@Buckskin](#):
>
> ```auto
> Looking for Something?
> We're sorry. The Web address you entered is not a functioning page on our site
>
> ```
Can you tell me which versions you’re using of Node.red, Node.js and AppleStrudel, and which method you’re using – proxy or cookies ? It really does look as though you’re retrieving an expired cookie or an incorrect link to Amazon.
---
### Author:  [@Buckskin](https://discourse.nodered.org/u/Buckskin)
#### Post date: [24 July 2026 15:41 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/34 "2026-07-24T15:41:33Z")
Node Red v5.0.1
Node.js v26.5.0
AppleStrudel v5.1.1
I have tried both proxy & cookie. The cookie used to work and using it with the flow that Dave shows (which again I have been using for a long time) the initialise node shows success but none of the other nodes work (all show uninitialized)
Using proxy gives the failures as already mentioned. All settings as shown in the AppleStrudel node setup instructions for UK. (I can also log on to Amazon shopping using email & password used for authentication - again, which used to work)
Tried using a separated browser, also incognito mode, neither made any difference.
Fixed the problem (for the moment anyway). I created a new Amazon account and it now works. 😕 🤣
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [24 July 2026 15:58 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/35 "2026-07-24T15:58:32Z")
> [@Buckskin](#):
>
> Node.js v26.5.0
I would advise against using v26, it is not yet the LTS version, some nodes may well have problems with it. Stick to 24 for the moment.
---
### Author:  [@Buckskin](https://discourse.nodered.org/u/Buckskin)
#### Post date: [24 July 2026 16:17 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/36 "2026-07-24T16:17:14Z")
Acknowledged. I am experimenting using Temporal which requires 26. So far none of the nodes I use have a problem.
Re- the AppleStrudel issue, I also had to delete the config node and re-create so this may have been to problem all along.
---
### Author:  [@DiverRich](https://discourse.nodered.org/u/DiverRich)
#### Post date: [25 July 2026 01:16 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/37 "2026-07-25T01:16:59Z")
> I would advise against using v26, it is not yet the LTS version, some nodes may well have problems with it. Stick to 24 for the moment.
I had to downgrade from 24 to 22.23.1 because the 5.0.59 palette update was failing with EBADENGINE since the package engine declaration didn't include v24. Was that updated in applestrudel 5.1.1?
---
### Author:  [@Buckskin](https://discourse.nodered.org/u/Buckskin)
#### Post date: [25 July 2026 15:45 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/38 "2026-07-25T15:45:42Z")
I have given up. I can log in using the new user name & password, but still not on the original. The issue?? all my devices are on Alexa with the old user name & password (that still works by the way)
---
### Author:  [@franz](https://discourse.nodered.org/u/franz)
#### Post date: [30 July 2026 08:07 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755/39 "2026-07-30T08:07:25Z")
> [@DiverRich](#):
>
> I had to downgrade from 24 to 22.23.1 because the 5.0.59 palette update was failing with EBADENGINE since the package engine declaration didn't include v24. Was that updated in applestrudel 5.1.1?
As you can see, the engine hasn’t changed. EBADENGINE is probably due to the palette number it uses. --engine-strict; which is different from the ‘engines’ declaration in Applestrudel. You should try installing it on a test cloned container using `npm install node-red-contrib-alexa-remote2-applestrudel --no-engine-strict`, to see if it installs correctly.
[Previous page](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-applestrudel-error-on-amazon-login-page/100755.md?page=1)