MeshCentral: Node-Red Editor Sometimes Hangs on Load over Webrelay
Describe the bug When loading NodeRed Code Editor via Webrelay, the page will often stall midway through its loading screen. This issue seems to only happen via WebRelay and not other access methods (remote-it relay, access within LAN).
To Reproduce Steps to reproduce the behavior:
- Install Nodered on Raspberry Pi
- Populate with complex project. (maybe not related)
- Install MeshCentral on Raspberry Pi
- Set HTTP alternate port to Nodered
- Open Webrelay
- Observe Nodered top bar & background load. Loading bar loads and begins to fill before stopping part of the way.
- Refreshing the page an indeterminate number of times occasionally will finish loading the page.
Expected behavior Loading bar should fill up quickly and shift the body of the page to include the Flow editor and current project.
Screenshots
Server Software (please complete the following information):
- OS: Ubuntu LXC on Proxmox
- Virtualization: Docker
- Network: WAN mode, Behind NGINX Proxy Manager, which manages SSL
- Version: 1.1.32
- Node: 20.10.0
Client Device (please complete the following information):
- Device: Desktop Workstation
- OS: Windows 11
- Network: Local to Meshcentral
- Browser: Chrome
- MeshCentralRouter Version: N/A
Remote Device (please complete the following information):
- Device: Raspberry Pi
- OS: Raspberry Pi OS bookworm, 64-Bit
- Network: Happens both locally and across WAN.
- Current Core Version (if known): Nov 21 2022, 2018810399
Additional context We’ve tried to reproduce the issue via a Remote.it relay, as well as local access, and the issue seems to only happen when accessed via MeshCentral webrelay. It is not consistent, no logs appear in the browser console, but several media objects seem to stall with “pending” status. Nodered’s logs do fire a “Connection Refused” error on hang, but without specification as to why. It’s possible that this issue is with NodeRed, but since the presentation seems exclusive to Meshcentral, I wanted to see if it was possibly something about the how the relay communicates with the remote webserver. It feels like a similar experience to #4369.
This has occurred across several remote devices and several client devices. On client devices, we’ve replicated the issue using Chrome on Windows, and Chrome & Safari on Mac. For remote devices, this has happened on multiple Raspberry Pi devices, as well as an Intel NUC running Ubuntu 23.04. All types of remote devices we currently field have exhibited some sort of inconsistent hang-on-load issue in this manner.
Your config.json file
{
"$schema": "http://info.meshcentral.com/downloads/meshcentral-config-schema.json",
"settings": {
"cert": "mesh.$DOMAIN.com",
"_WANonly": true,
"_LANonly": true,
"sessionKey": "$PASSWORD",
"port": 443,
"_aliasPort": 443,
"redirPort": 80,
"_redirAliasPort": 80,
"RelayDNS": "relay.mesh.$DOMAIN.com",
"AgentPong": 300,
"TLSOffload": false,
"trustedProxy": "$PROXY_IP,$ROUTER_IP",
"SelfUpdate": false,
"allowLoginToken": true,
"allowFraming": true,
"mongodb": "mongodb://mongodb:27017/mesh",
"mongodbcol": "mesh",
"WebRTC": true,
"desktopMultiplex": true,
"cookieIpCheck": "none",
"sessionSameSite": "lax",
"plugins": { "enabled": true }
},
"domains": {
"": {
"title": "$COMPANY",
"title2": "Internal Mesh",
"_minify": true,
"NewAccounts": "false",
"_userNameIsEmail": true,
"certUrl": "https://$PROXY_IP:443",
"passwordRequirements": {
"force2factor": true,
"autofido2fa": true
}
}
},
"_letsencrypt": {
"__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before>",
"_email": "myemail@mydomain.com",
"_names": "myserver.mydomain.com",
"production": false
}
}
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 18
Commits related to this issue
- remove CSP for web relay as apps dont load properly with the default set #6456 Signed-off-by: si458 <simonsmith5521@gmail.com> — committed to Ylianst/MeshCentral by si458 2 years ago
Hello Simon, I have emailed you directly to your published email on here, its regarding some help with MC. Kind Regards Dan Smith
(I typed this response via email last week, and didn’t realize until now that it was in my drafts folder)
My current working theory is an out-of-date version of node.js or node-red, or possibly one of the dependencies. I will try to put refactoring and dependency updating on my to-do list for the near future, see if that can sort it out. I will also see if I can replicate the issue on a blank project. I appreciate the effort you put into trying to recreate the issue. If you wanted to resolve this as
worksforme, I think that’s totally reasonable. I’m willing to conclude at this point that the issue is likely in our project, and I can reopen the ticket if further data implies otherwise.On Thu, Nov 14, 2024, 9:10 AM Simon Smith @.***> wrote: