Ben Hardill

Workaround is to manually generate keys with `ssh-keygen -t ed25519 ` and replace the ones in the users .ssh dir (or mount them into /data/projects/.ssh_keys` for docker) Looking at forcing...

Fix in next docker builds, will close when done. https://github.com/node-red/node-red-docker/pull/323

Closing this as 3.0.1 has shipped @Steve-Mcl we should look at what options we could present for key types, but that I think that should be separate issue.

Hi, Thanks for raising this, but as described in the template you removed when opening the issue we prefer that questions and feature requests should be raised on the Node-RED...

@NetHans but just because an email has been accepted by the mail server is no indication that it will actually be sent to the recipient

Nodes should block at the left hand edge of the canvas (and do while testing here). Please add something a little more useful to the steps to reproduce as "Be...

What nodes have you installed or upgraded recently? Failing that a list of what 3rd party (including Home Assistant) nodes do you have installed and are using. Also "Hard to...

Trimmed version of the list to just those listed as in-use to make it easier to check them off - [ ] 1.2.0 node-red-contrib-advanced-ping - [ ] 1.1.9 node-red-contrib-amcrest-ad110 -...

Can reproduce, attached is a full testcase ```html Test const foo = { hello: "world" } function send() { const XHR = new XMLHttpRequest(); XHR.open( 'POST', 'http://foo:[email protected]:1880/foo', true ); XHR.withCredentials...

Think I know what the issue is, we have multiple cors handlers on the same path when httpNode and the editor are both on `/` Workaround is to move the...