Node-Red, other browsers can log in, firefox can't
This is not a simple question to ask and is not very easy to explain. But I shall try.
I am running a program suite called "Node-Red" on another machine. Access is done via the "web". (http). Usually you just enter the IP address and you are into the edit screen. This is obviously not a good idea on a machine exposed to the net. So, you activate security settings. (See a bit later)
I am using Firefox as my main browser and I have activated security settings in Node-Red. Subsequently I can't log in. BUT! Other browsers can. (From other people) I have tried it and seen it once work. Sorry but that's all I have at this time. The information attached about my system is unedited, because as I said: I don't know what is needed at this stage.
I can get the "name" entered, but every time I click on the Password field, the cursor jumps back to the name field.
(Documents for what I am doing) https://nodered.org/docs/security.html
See attached image for what I see in FF. Please forgive the red arrows. I was talking to the Node-Red people about it also. "Luckily" someone else is having problems when using FireFox. But they can if they use another browser - as stated.
I don't know exactly what information (at this time) is needed. Alas it may require someone in here to install Node-Red and try it them selves.
I also appreciate that is a big ask. But it would seem I am not the only person with this problem and someone else has recently posted that they have the same problem.
What further complicated me asking here is I have a couple of other programs installed for password management and I had to go through the process of eliminating them.
So I am now at the point where it is pointing to FireFox and it not playing the game.
Thanks in advance for any help in resolving the problem.
Alle Antworten (5)
We've been there.
Screen shot supplied.
It shows the XML error.
But: Here it is.
Just a bit more info:
The RED error.
http:192.168.0.142:1880/settings? = .........
As is, I can't access it. DENIED.
So I disabled that part and tried again. This is what I get: {"httpNodeRoot":"/","version":"0.19.5","context":{"default":"memory","stores":["memory"]},"editorTheme":{"projects":{"enabled":true}},"git":{},"flowEncryptionType":"system","tlsConfigDisableLocalFiles":false}
Geändert am von teeny_weeny
Okay, but what is the connection between the XML Parsing error and the script? I would think the problem is in the XML file -- or maybe it's not really an XML file if the problem is at the very first character.
If you try loading the latest URL mentioned in the console --
http://192.168.0.142:1880/settings?_=number
-- what does the file look like? If that's how you got the script, the server seems to be sending the wrong file or the page is retrieving the wrong file or the page wrongly expects an XML file instead of a script file.
The file you mentioned is included......
(Just noticed the question and am now editing. Can't get scroll back so can't repaste what the file is.) There is a story of what happened in my previous post. (Ah, here it is after saving and editng)
Just a bit more info: The RED error. http:192.168.0.142:1880/settings? = .........
As is, I can't access it. DENIED.
So I disabled that part and tried again. This is what I get: {"httpNodeRoot":"/","version":"0.19.5","context":{"default":"memory","stores":["memory"]},"editorTheme":{"projects":{"enabled":true}},"git":{},"flowEncryptionType":"system","tlsConfigDisableLocalFiles":false}
Well, that's where I get lost.
It is an XML problem. FF doesn't really tell me WHERE this file is.
Looking at the errors (See new attached). Orange is the "Don't use this code, it is deprecated" and the Red is the XML error.
Maybe the first is causing the second. *&*&^ if I know. Searching the internet there are SQUILLIONS of articles about this. Many/Most say "You have a broken addon which is causing the problem". (Cough)... Yeah, right. The only thing I have done to FF is install a H264 codec. This is on a VM and is (now) used for testing bugs. So I need to keep it as clean as possible to remove such possibilities being true.
So that is unresolvable.
Then there is the XML error.
Again: NO INFORMATION IS GIVEN TO WHERE THIS FILE IS. (Or: WHO's FILE IT IS) I am looking everywhere. The links to the right have been looked at - but they can't be opened directly as they have extra stuff at the end like another : and so I have to manually type them in. They take me to a whole new world of stuff I don't get.
All I can do is report what I see/find.
It is all (basically) a different language to me.
I am somewhat off put by the REAL FF, and the REAL NR people not looking at this problem.
It is contentious - sure - but it is a problem.
One of those two sets of people should be able to work out what is causing the problem, rather than leaving it to the end users to muddle through the "doings" and work it out.
(Ok, I'll shut up now.)
Geändert am von teeny_weeny
Okay, if the file that is listed in the XML error doesn't exist, or Firefox is not authorized to retrieve it, then I wonder why Firefox is requesting it?
*frustrated*
I know someday I should learn more about Node, and then I would be better able to understand what Node-red is about, but I just can't do it right now.
Okay, if the file that is listed in the XML error doesn't exist, or Firefox is not authorized to retrieve it, then I wonder why Firefox is requesting it?
No. If Node-Red is set for passwords, I am DENIED access to the file. That isn't saying it doesn't exist.
So, I changed the settings so Node-Red isn't wanting passwords. I can then access the file.
GRANTED it is not guaranteed to be the same file.
But I posted the contents of said file (twice).
It is "GREEK" to me.
It would be nice if someone in the know could look at this problem and help me identify "WHO" is causing the problem.
I'm not interested in laying blame. I would prefer it simply fixed.
And I appreciate your help. Shame there is nothing coming from the Node-Red camp with information on this.
Geändert am von teeny_weeny