UIBUILDER problem after Node-Red Update to 4.1.0

General
1

Hello,

I just upgrade my Node-Red platform to 4.1.0 on my Raspberry 5 and then I get stuck with UiBuilder to get access to my UiBuilder dashboard.

image
image416×340 7.39 KB

I did the complete cleaning of the cookies like requested in the message, no way. It’s the same situation with other browser. I uninstall uibuilder and install it again. No way. No error message in Node-Red logs telling a problem somewhere or in relation to UIBUILDER.

Some ideas to check ?

Regards

Jean-Rem

2

Hi, this is not a cookie issue. Something is causing a redirect of your selected URL to something else and is then looping.

Please let us know the usual baseline info which you can get from the node-red log at startup. Versions of node.js, node-red, uibuilder. Also please show what URL's you are working with and whether you have changed the node-red HTTP roots in settings.js (which will impact the URL's).

Also, let us know if you are using a proxy server to control access.

3

Hello,

Here are the requested information:

image
image705×784 162 KB

settings.txt (22.9 KB)

Using uibuilder 7.4.3 without proxy server

image
image417×235 7.44 KB

Regards

Jean-Rem

4

It would be useful to see the uibuilder part of the startup log as well. You cut off the display just before it.

Next thing to look at is your uibuilder index.html file

It might also be useful for you to check your browser's dev tools - both the console and the networks tab.

You should be able to check what is causing the redirect by following this:

Check the Redirect Chain

  • Use browser DevTools → Network tab:
    • Reload the page (disable cache).
    • Look at the first request, then follow the Status Code (301, 302, 307, 308).
    • Each redirect will show a Location header telling the browser where it’s being sent.
    • Trace until you see where it loops back.
  • Alternatively, use command-line tools:
curl -I -L http://example.com

(the -L follows redirects, showing each hop)

5

Hello,

Here is the complete Popup.

image
image421×644 21.2 KB

Here is the curl information

curl_info.txt (22.7 KB)

Here is the browser network tab information.

image
image916×516 32.4 KB

Regards

Jean-Rem

6

So it is bouncing between /wf3/ (with) and /wf3/ (without trailing /) and back-and-forth.

This indicates a misconfigured web server.

What should happen is that accessing /wf3/, the browser should directly receive a 200 status along with the content. Or a 301 status which means the browser already has the page in its cache.

If you access /wf3, the browser should be told that this does not actually exist and that the real resource is at /wf3/ (via a 301 "Moved Permanently" response). At that point, the browser requests the correct resource and receives a 200 response along with the content.

For some reason, your configuration is not doing that because it cannot find the content at /wf3/. That should map to /wf3/index.html. Even if that cannot be found, UIBUILDER's default index web page should be returned which tells you that you don't have an index.html file in the right place.

The main thing I'm noticing is that the initial response for /wf3/ is NOT actually returning all the headers you would expect from Node-RED's default ExpressJS server.

To me, this still indicates a mis-configured node-red server. You should probably try stopping node-red, renaming the settings.js file and restarting node-red. This should create a fresh settings file.

If that doesn't work, I need the output of node-red's log after startup a little further than you've shared, as previously asked. There is a secton in the log that should look something like this:

image
image913×231 8.99 KB

And I would also need you to make sure that you have something valid in the src folder that you see listed as the "Server folder" on the Core tab of the uibuilder node's configuration panel.

Beyond looking at those, I may be at a bit of a loss. I've tested this against both my dev server and my live, the live server even has a proxy server in the way. In all cases, this works as expected.

7

Hello,

Thanks for your reply (and your time).

I test your suggestion for the settings.js file but without success.

Then, I take care of the screenshot I gave you here above (logs at N-R startup). It didn’t mention the information you request to me because the logs itself stop appear at this line. So the information about uibuilder never appear. It’s like this at each start of N-R. So, for me, it confirm a more general problem.

Due to that situation, I will make a new clean installation on this Dev. Raspberry Pi 5. I believe that’s the best way. This last 4.1 upgarde is maybe the last step of many other small mistakes.

Now i’ts the good time :wink:

Regards

Jean-Rem

1 Like
8

@Jean-Rem So just to confirm… is the problem related to UIBUILDER, or that you believe it was due to the node-RED update failing?

9

I'm almost entirely certain that it is a node-red issue. A clean install should help us know.

10

Hello,

As soon as I can do the complete refresh of my Raspberry, I’ll come back to you for confirmation.

Regards

Jean-Rem

2 Likes