Hi Chaps.
After a reinstall of Raspberry Pi OS, I have managed to get my Node Red instance working again by importing a previously backed up JSON file with all my home automation flows. I had to install a few extra nodes including Alexa-remote2-applestrudel. This is where the problem lies, I cannot reinitialise this set of smart home nodes to communicate with my Alexa account. The message in Node red to open http://192.168.1.XXX:3456 is complied with and login to my Alexa account. Entering my credentials and receiving a code on my phone is also performed only to receive a message that the page could not be found. I have read that other folks are having the same issues, and the conclusion seems that it is no longer possible to link Node Red to Alexa. My question is: has anyone managed to regain the Alexa functionality from Node Red or is it lost forever?
Thank you for any guidance.
It is very hit and miss and usually involves sacrificing a small animal!
Also, I've found best to do it on Tuesdays 
Eventually, on about the 15th attempt it might work
Hmmm that easy eh?
Annoying thing is, if I boot from my old SSD with old OS, the Node red instance there will allow the Alexa node will connect. I wonder if its just a matter of identifying and copying a configuration file across to the new OS.
I have found also that this page is sometimes very difficult to load. It does though, in the end, and just recently after success I implemented this solution for proxy.
How to get your Alexa cookie?
I can see the saved Alexa cookie in the context folder (Filebrowser on an iHost), which refreshes periodically and so far everything is running great.
Who knows!
It's one of the flakiest things I've ever had the misfortune to work with
For some people, it failed about 3 years ago and they never managed to get it going again
It stopped working for me for about 2 months once 
I seem to be lucky then as it was working fine until I re-installed the Raspberry pi OS. I was wondering if I could copy the AuthFile from the old install to the new if only I knew where it was located.
If the old OS connects, and you save the alexa login cookie to context you can simply move the logincookie to the new OS.
I use this simple flow to renew and save logincookie. I copy the context to a new machine and avoid the :3456 login hassle.
[{"id":"48d034130f262ec8","type":"inject","z":"e1ef5728e9206b4a","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"00 02 * * 5","once":true,"onceDelay":0.1,"topic":"","payload":"#:(file)::alexa","payloadType":"flow","x":150,"y":620,"wires":[["f78696691771c3ee"]]},{"id":"f78696691771c3ee","type":"alexa-remote-init","z":"e1ef5728e9206b4a","name":"","account":"c8738129.d902c","option":"initialise","x":360,"y":620,"wires":[["3b6342b82af27c5f"]]},{"id":"3b6342b82af27c5f","type":"change","z":"e1ef5728e9206b4a","name":"","rules":[{"t":"set","p":"#:(file)::alexa","pt":"flow","to":"payload","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":580,"y":600,"wires":[[]]},{"id":"c8738129.d902c","type":"alexa-remote-account","name":"alexa remote 2","authMethod":"proxy","proxyOwnIp":"localhost","proxyPort":"3456","cookieFile":"/data/data/com.termux/files/home/.node-red/.alexa.cookie","refreshInterval":"14","alexaServiceHost":"layla.amazon.co.uk","pushDispatchHost":"","amazonPage":"amazon.co.uk","acceptLanguage":"en-GB","onKeywordInLanguage":"","userAgent":"","usePushConnection":"on","autoInit":"off","autoQueryActivityOnTrigger":"off"}]
Obviously you have to have logged in at least once. and save the logincookie
Thanks for that. Any idea how/where to find then move the old cookie? Sorry not very good at this stuff.
I didn't really specify a location in the file path box (I know I should have) just typed authFile so just wondering where it might be located.
I do not use auto init. You have set a path of authFile, so why not search you system for that directory.
Yes I'll have a search and see where it is
Just to draw a line under this post, I managed to locate and copy the authFile file from my old installation to my new one and it is now working as before, my Alexa remote node is initialising with my Alexa account. Thanks again for your time in helping me.
