# Problems with node-red-contrib-alexa-remote2-applestrudel and Amazon

**URL:** <https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606>\
**Category:** General\
**Created:** [5 November 2025 21:51 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606 "2025-11-05T21:51:54Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [5 November 2025 21:51 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/1 "2025-11-05T21:51:54Z")

</div>

I have recently received the message open XXXX:3456 in your browser. However, when I do and enter my email & password I then get a pass code sent to my phone. The resulting entry box is very flaky and when I finally do get to enter the code I get an [amazon.com](http://amazon.com) 404 error (I have my node set to [amazon.co.uk](http://amazon.co.uk))

Has anyone else had this problem, and if so have you resolved it and how?

---

<div class="post-metadata">

**Author:** ![DiverRich](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/diverrich/32/64523_2.png) [@DiverRich](https://discourse.nodered.org/u/DiverRich)\
**Post date:** [6 November 2025 03:24 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/2 "2025-11-06T03:24:36Z")

</div>

Not sure but this may be part of the problem. [https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/234](https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/234)

---

<div class="post-metadata">

**Author:** ![ghayne](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ghayne/32/39_2.png) [@ghayne](https://discourse.nodered.org/u/ghayne)\
**Post date:** [6 November 2025 09:12 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/3 "2025-11-06T09:12:31Z")

</div>

Same here, here we go again!

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [6 November 2025 14:50 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/4 "2025-11-06T14:50:40Z")

</div>

Yes that is the issue .  
I fixed mine by upgrading applestrudle to latest, then edited the `alexa-remote-ext.js` as described in the link you provided. Then restarted node-red and re authorised via proxy url `http://localhost:3456`  
There should be an update to the node coming soon if you do not fancy editing your node\_module files.

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [6 November 2025 16:14 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/5 "2025-11-06T16:14:50Z")

</div>

I've just updated the Alexa node using the Palette Manager to 5.0.54 and restarted Node-RED.  
Seems to initialise without any problems. (No edits needed or performed.)  
It will be interesting to "hear" if Alexa delivers my weather forecast tomorrow morning.

 ![alexa_update](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/a/2a07afa1e8ddb0ae86d244b9c90385df27c40648.png)

 ![alexa_initialised](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/d/3dd051cac8c0a012c75050402bf7bdda62373856.png)

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [6 November 2025 17:05 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/6 "2025-11-06T17:05:04Z")

</div>

Nope. Still doesn't work. I still get to the Amazon login enter email & password, then get flaky entry for SMS code straight to Amazon dot com 404

PS Checked the customer ID bit

```auto
	async getCustomerId() {
		const response = await new Promise((resolve, reject) => {
			const callback = (err, val) => err ? reject(err) : resolve(val);
			this.getUsersMe(callback);
		});
		ensureMatch(response, { id: '' });
		return response.id;
	}

```

---

<div class="post-metadata">

**Author:** ![DiverRich](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/diverrich/32/64523_2.png) [@DiverRich](https://discourse.nodered.org/u/DiverRich)\
**Post date:** [6 November 2025 18:28 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/7 "2025-11-06T18:28:56Z")

</div>

It might be worth trying a private browser when requesting your cookie as mentioned [in this post.](https://discourse.nodered.org/t/how-to-get-your-alexa-cookie/88174)

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [6 November 2025 19:14 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/8 "2025-11-06T19:14:14Z")

</div>

Tried that. Exactly the same flaky entry for an SMS code straight to 404

---

<div class="post-metadata">

**Author:** ![franz](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/franz/32/71949_2.png) [@franz](https://discourse.nodered.org/u/franz)\
**Post date:** [7 November 2025 17:31 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/9 "2025-11-07T17:31:48Z")

</div>

I also have Alexa... Applestrudel stuck at authentication (I have version 5.0.55 and nodered4.1.1.) and I can't even uninstall it. it will be because of this problem : `npm audit

# npm audit report

cookie \<0.7.0  
cookie accepts cookie name, path, and domain with out of bounds characters - [cookie accepts cookie name, path, and domain with out of bounds characters · CVE-2024-47764 · GitHub Advisory Database · GitHub](https://github.com/advisories/GHSA-pxg6-pf52-xh8x)  
No fix available  
node\_modules/alexa-cookie2/node\_modules/cookie  
alexa-cookie2 \>=2.0.0  
Depends on vulnerable versions of cookie  
node\_modules/alexa-cookie2  
alexa-remote2 \>=2.0.0  
Depends on vulnerable versions of alexa-cookie2  
node\_modules/alexa-remote2  
node-red-contrib-alexa-remote2-applestrudel \*  
Depends on vulnerable versions of alexa-remote2  
node\_modules/node-red-contrib-alexa-remote2-applestrudel

4 low severity vulnerabilities

Some issues need review, and may require choosing  
a different dependency.`

---

<div class="post-metadata">

**Author:** ![DiverRich](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/diverrich/32/64523_2.png) [@DiverRich](https://discourse.nodered.org/u/DiverRich)\
**Post date:** [8 November 2025 19:36 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/10 "2025-11-08T19:36:34Z")

</div>

If you haven't resolved this yet, have you tried another browser or tried getting the cookie on another device?

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [8 November 2025 20:23 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/11 "2025-11-08T20:23:47Z")

</div>

Yes. I even tried moving the nodes to a different device. Entering the cookie request in the browser keeps sending me to [amazon.com](http://amazon.com), not [amazon.co.uk](http://amazon.co.uk) (not sure if that is correct) and I still end up with a 404 error (dogs on the page)

---

<div class="post-metadata">

**Author:** ![franz](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/franz/32/71949_2.png) [@franz](https://discourse.nodered.org/u/franz)\
**Post date:** [9 November 2025 17:40 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/12 "2025-11-09T17:40:03Z")

</div>

I have Nodered in a container. I made a backup and reinstalled everything. Now it works fine.

---

<div class="post-metadata">

**Author:** ![ghayne](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ghayne/32/39_2.png) [@ghayne](https://discourse.nodered.org/u/ghayne)\
**Post date:** [9 November 2025 18:01 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/13 "2025-11-09T18:01:13Z")

</div>

The same procedure worked for me too @dynamicdave,

---

<div class="post-metadata">

**Author:** ![franz](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/franz/32/71949_2.png) [@franz](https://discourse.nodered.org/u/franz)\
**Post date:** [10 November 2025 08:42 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/14 "2025-11-10T08:42:53Z")

</div>

I waited 24 hours, but with the latest version of Applestrudel, I can only do one voice query at a time. I had to tie a knot to reset Alexa every minute, but that's not a good solution. It almost seems like there's a problem with proxy mode. Does anyone know how to use cookie mode?

---

<div class="post-metadata">

**Author:** ![Sgooch](https://avatars.discourse-cdn.com/v4/letter/s/2acd7d/32.png) [@Sgooch](https://discourse.nodered.org/u/Sgooch)\
**Post date:** [12 November 2025 23:20 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/15 "2025-11-12T23:20:16Z")

</div>

I can see version 5.0.55 in palette manager, but it tells me I have a conflict with "node-red-contrib-alexa-remote2 (not the applestrudel version). I thought I had disabled everything that uses that, but it seems to think that "something" is using it but I sure can not see it visually! Any thoughts on next steps? I REALLY want to get the Alexa stuff working again.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [13 November 2025 09:35 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/16 "2025-11-13T09:35:32Z")

</div>

Uninstall that node. If it won't let you then check in Configuration Nodes for any unused configuration nodes related to that and delete them and deploy and try again. If it still won't let you uninstall it then open a command window and go into your .node-red folder (assuming this is a conventional install) and run  
`npm remove node-red-contrib-alexa-remote2`  
Then restart node-red.

---

<div class="post-metadata">

**Author:** ![Sgooch](https://avatars.discourse-cdn.com/v4/letter/s/2acd7d/32.png) [@Sgooch](https://discourse.nodered.org/u/Sgooch)\
**Post date:** [13 November 2025 13:55 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/17 "2025-11-13T13:55:36Z")

</div>

I had to remove each please it was used even though they were “disabled”. New version seems to be working great!

Can someone explain to me (in old man terms) exactly what was failing in the Alexa authentication and what was done to fix it in the new version?

-Steve

---

<div class="post-metadata">

**Author:** ![franz](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/franz/32/71949_2.png) [@franz](https://discourse.nodered.org/u/franz)\
**Post date:** [7 February 2026 08:59 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/18 "2026-02-07T08:59:46Z")

</div>

node-red-contrib-alexa-remote2-applestrudel 5.0.55. Until the day before yesterday, everything was working correctly. I am using proxy authentication with cookies saved in /data and refreshing every day. Now it shows me `7 Feb 03:31:44 - [info] Server now running at http://127.0.0.1:1880/ 7 Feb 03:31:44 - [info] Starting flows 7 Feb 03:31:44 - [info] [alexa-remote-account:alexa] intialising "alexa" with the PROXY method and NO saved data... 7 Feb 03:31:46 - [info] Started flows` It seems to work only with the cookies option instead of proxy, but I have to renew the cookies every time I restart nodered. Do you also experience these strange logouts?

---

<div class="post-metadata">

**Author:** ![DiverRich](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/diverrich/32/64523_2.png) [@DiverRich](https://discourse.nodered.org/u/DiverRich)\
**Post date:** [7 February 2026 21:15 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/19 "2026-02-07T21:15:43Z")

</div>

At the moment my setup is still working.

---

<div class="post-metadata">

**Author:** ![franz](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/franz/32/71949_2.png) [@franz](https://discourse.nodered.org/u/franz)\
**Post date:** [7 February 2026 21:35 UTC](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606/20 "2026-02-07T21:35:55Z")

</div>

I deleted the cookie, re-authenticated with the proxy, and set the refresh to 4 hours instead of one day. I think that's the problem.

[Next page](https://discourse.nodered.org/t/problems-with-node-red-contrib-alexa-remote2-applestrudel-and-amazon/99606.md?page=2)