Node Red仪表盘远程访问咨询：无需VNC供客户端直接访问

Great question! You’re on the right track with ngrok and Dataplicity—both are perfect for exposing your Node-RED dashboard to clients without letting them touch your VNC server. Let’s walk through step-by-step implementations for each tool, plus key things to keep in mind.

Using ngrok #

ngrok is ideal for quick, temporary access (or permanent if you upgrade to a paid plan). Here’s how to set it up:

• Confirm your Node-RED details: By default, Node-RED runs on port 1880, and the dashboard lives at the /ui path. So your local access URL is http://localhost:1880/ui.
• Install ngrok: Download the appropriate version for your server’s OS from the ngrok platform, then extract it to a folder you can access via terminal.
• Authenticate your account: Sign up for an ngrok account, grab your auth token from the dashboard, and run this command to save it (so you don’t have to enter it every time):

  ngrok config add-authtoken YOUR_AUTH_TOKEN
  

• Start the tunnel: Run this command to forward traffic from ngrok’s public network to your Node-RED port:

  ngrok http 1880
  

• Share the URL: ngrok will output a public HTTPS URL (like https://xyz789.ngrok.io). Tell your clients to visit https://xyz789.ngrok.io/ui—that’s it, they’ll see your dashboard directly.

ngrok Key Notes #

• Free vs Paid: Free ngrok generates a random URL every time you restart the tunnel. If you need a fixed, custom domain, you’ll need a paid plan.
• Node-RED Access Permissions: Double-check your Node-RED settings.js file to make sure it doesn’t restrict access to only local IPs. Look for the httpNodeOptions or ui configuration blocks—remove any IP whitelists if present.
• Security First: Add password authentication to your Node-RED dashboard! You can do this by enabling adminAuth in settings.js, or using Node-RED’s built-in login nodes. This prevents random people from accessing your dashboard via the ngrok URL.
• Bandwidth Limits: Free ngrok has monthly bandwidth caps. If you have multiple clients or frequent access, upgrade to avoid hitting limits.

Using Dataplicity #

Dataplicity is better for long-term, stable access—especially if you want a fixed URL without upgrading immediately. Here’s the setup:

• Register & Install Client: Sign up for a Dataplicity account, then follow the on-screen instructions to install their client on your Node-RED server. The installation is usually a single terminal command that pulls and sets up the client automatically.
• Enable Tunnel Access: Once your device shows up in the Dataplicity dashboard, find the "Tunnel" or "Remote Access" feature and enable it.
• Configure the Tunnel: Set the tunnel to point to your Node-RED port (1880) and optionally the /ui path. Alternatively, point it to the root and have clients add /ui themselves.
• Share the Fixed URL: Dataplicity will give you a permanent public URL (like your-device-name.dataplicity.io). Clients can visit your-device-name.dataplicity.io/ui to access the dashboard anytime your server is online.

Dataplicity Key Notes #

• Free Plan Limits: The free plan lets you connect one device and has moderate bandwidth limits. For more devices or higher traffic, you’ll need a paid tier.
• Auto-Start: Make sure the Dataplicity client is set to start automatically when your server boots. This ensures the tunnel stays up even after a restart.
• Security: Just like with ngrok, add authentication to your Node-RED dashboard. Dataplicity also lets you restrict tunnel access to specific IPs in their dashboard for an extra layer of security.
• Device Management: The Dataplicity dashboard lets you monitor your device’s status, restart the tunnel, and manage access—handy for long-term setups.

Final Recommendations #

• Use ngrok if you need a quick, temporary solution (e.g., testing with a client for a day).
• Use Dataplicity if you need a stable, fixed URL for ongoing client access.
• Always secure your dashboard: No matter which tool you use, adding password auth prevents unauthorized access to your Node-RED instance and data.

内容的提问来源于stack exchange，提问作者Tom van Nes