the interface remained blank and none of the windows showed anything... :/

[NimovaProj]

Steps to reproduce the problem:

Please fill the below with the necessary steps to reproduce the problem

Error Information:

i.getParent is not a function

TypeError: i.getParent is not a function at n.value (https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/main.bundle.js:303:543118) at il (https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/common.bundle.js:46:83470) at ds (https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/common.bundle.js:46:101245) at t.unstable_runWithPriority (https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/common.bundle.js:54:3844) at Bo (https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/common.bundle.js:46:45023) at ps (https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/common.bundle.js:46:97717) at Zl (https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/common.bundle.js:46:93871) at https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/common.bundle.js:46:45314 at t.unstable_runWithPriority (https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/common.bundle.js:54:3844) at Bo (https://v2.virtualflybrain.org/org.geppetto.frontend/geppetto/build/common.bundle.js:46:45023)

%2B Host for MessageSocket to connect: wss://v2.virtualflybrain.org/org.geppetto.frontend/GeppettoServlet%0A%2B %c WebSocket Status %2D Opened 
background: %23444; color: %23bada55%0A%2B %c WebSocket Status %2D Open connection error 
background: %23000; color: red%0A%2B WebSocket Status %2D retry in 5000ms
[object CloseEvent]%0A%2B %c WebSocket Status %2D reconnecting... 
background: %23444; color: %23bada55%0A%2B %c WebSocket Status %2D Opened 
background: %23444; color: %23bada55%0A%2D TypeError: i.getParent is not a function

[Robbie1977]

@NimovaProj Hey, Thanks for flagging this. Sorry, no one flagged this one was looked at back in Jan. This was related to a server issue, the affected node was reset so hopefully this issue has gone away for you.

Please let us know if there is still an issue showing on your end and I'll look into it further.