Loading Plugins (Post Instalation) - Node-RED

General
1

Good morning, a few days ago I changed to a formatted computer and among the programs that I reinstalled this Node-RED, when I performed the typical steps for its installation I obtained what is shown in the image and when I try to enter the Localhost, Node-RED does not advance from the Loading Plugins message, do you think it is missing some drivers or additional programs? I would greatly appreciate your help.

image
image1717Ă—994 50.8 KB

image
image1603Ă—625 14.7 KB

2

Those are all just warnings and can be ignored.

As to why it gets stuck loading the editor we would need to see the Node-RED logs and the Browsers console.

Please post the Text, not screenshots if you supply this information as screenshots are hard to read.

3

Also probably duplicate of

4

There are two known issues at the moment. To know which you've hit, please look at the Developer Console in the browser for any error messages. If it says something about e.trim then we have this fixed in the next release. The workaround is to use a browser other than chrome for the moment.

If that is the error you see, could you do me a favour are provide a bit more information.

  1. in the developer tools, switch to the Network tab
  2. clear the log by clicking :no_entry_sign:
  3. reload the page
  4. enter plugins in the filter
  5. you should see a few entries - click on the last one.
  6. Click on the Headers tab and scroll down until you see the Accept-Language header - please tell me what value is has.

image
image1210Ă—932 121 KB

1 Like
5

I did not expect such detailed and fast answers, thank you for that, this is the text that appears:

  1. Accept:

text/html

  1. Accept-Encoding:

gzip, deflate, br

  1. Accept-Language:

es-419

  1. Connection:

keep-alive

  1. Host:

localhost:1880

  1. Node-RED-API-Version:

v2

  1. Referer:

http://localhost:1880/

  1. sec-ch-ua:

" Not A;Brand";v="99", "Chromium";v="90", "Google Chrome";v="90"

  1. sec-ch-ua-mobile:

?0

  1. Sec-Fetch-Dest:

empty

  1. Sec-Fetch-Mode:

cors

  1. Sec-Fetch-Site:

same-origin

  1. User-Agent:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36

  1. X-Requested-With:

XMLHttpRequest

6

image
image877Ă—310 9.74 KB

7

Thanks for sharing that. Yes, this is a known issue that will be fixed in 1.3.5 - probably getting that released tomorrow (Friday).

You could try setting your browser locale to en-US temporarily to avoid the error.

1 Like
8

It worked, I'll be waiting for you to fix it, thanks

9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.