RoboCanvas

Is there a way to turn off community apps from loading containers and just show plugins? I don't use containers any more, but I still use plugins.

nevermind. had to use http://xxx.xxx.xxx.xxx:18789/?token=your-gateway-token-here

2026-02-04T04:04:24.699Z [canvas] host mounted at http://0.0.0.0:18789/__openclaw__/canvas/ (root /root/.openclaw/canvas) 2026-02-04T04:04:24.832Z [heartbeat] started 2026-02-04T04:04:24.835Z [gateway] agent model: anthropic/claude-opus-4-5 2026-02-04T04:04:24.836Z [gateway] listening on ws://0.0.0.0:18789 (PID 1) 2026-02-04T04:04:24.837Z [gateway] log file: /tmp/openclaw/openclaw-2026-02-03.log 2026-02-04T04:04:24.845Z [browser/service] Browser control service ready (profiles=2) nothing else is happening. ideas? No changes from community app.

I keep fumbling on the llm part. I only have local ollama.

Thanks! Looking forward to this being in the community apps!

What is the Tailscale Sidecar?

I thought this was the tailscale forum

I keep getting errors when I try to set up a n8n funnel using tailscale. ======================= Executing Unraid Docker Hook for Tailscale ERROR: No root privileges! ERROR: Unraid Docker Hook script throw an error! Starting container without Tailscale! Starting container... ======================= Ideas?

I keep getting errors when I try to set up a n8n funnel using tailscale. ======================= Executing Unraid Docker Hook for Tailscale ERROR: No root privileges! ERROR: Unraid Docker Hook script throw an error! Starting container without Tailscale! Starting container... ======================= Ideas?

I'm not. I thought it was installed with 7.0 and the plug in is just extra.

Does anyone know why I have to keep reauthenticating my containers when I turn on funnel?

Can we uninstall the plug in if we updated to 7.0?

updated to 7.0. How come each time I update a container (and im using tailscale funnel) I have to reauthenticate the container?

It seems like you're having trouble setting up your UnRaid system due to parity disk issues. Here are some steps you can take to troubleshoot this problem: Check the cables: Ensure that all SATA data cables (for both power and data) are properly connected at both ends, especially between the motherboard and drives. Hard drive compatibility: Make sure your hard drives are compatible with UnRaid and have been formatted correctly. You can use GPT partitioning for drives larger than 2TB as MBR is limited to 2TB. Also, check if they support Btrfs file system which is used by UnRaid. Boot sequence: Ensure that the parity disk's boot order comes after the data disks in BIOS settings. SMART test: You've already done this, but it doesn't hurt to repeat with different tools like smartctl or GSmartControl to ensure no errors are detected. If there is a consistently failing sector on any of your drives, you may need to replace them. Check for hardware issues: Try connecting the parity disk directly into another SATA port on the motherboard. Use different SATA cables and power connectors (if available) to isolate potential cable or PSU problems. Check if there are any visible signs of damage like dents, scratches or burn marks on your drives. Reinstall UnRaid: If none of the above works, consider reinstalling UnRaid with a fresh installation. Make sure you backup any important data before proceeding though. Check forum discussions and documentation: Visit unraid.net's forums to search for similar issues others have faced. Read through UnRaid's official wiki (https://wiki.unraid.net/) which contains detailed guides on troubleshooting common problems like this one. As for the log files, you can upload them somewhere else (like Google Drive or Dropbox) and share a link here. This will help us pinpoint any specific issues that might be causing your problem. Lastly, don't get discouraged! Setting up a NAS system takes time and patience to ensure everything works perfectly. Good luck with your setup!

The fact that you're seeing a throughput of around 5 Gbps instead of the expected 10 Gbps could be due to several reasons, even if your interfaces are configured for 10 Gbps (10,000 Mbps). Here are some possibilities: Cabling and SFP+ DACs: Ensure that you're using proper SFP+ direct attach cables (DACs) rated for 10 Gbps. Lower quality or improperly rated cables might limit the speed to lower rates like 5 Gbps. Link Speed Negotiation: Some network devices may not always negotiate the highest possible link speed due to various factors such as cable length, device capabilities, or auto-negotiation issues. You can try forcing the link speed on both NICs and UDM-SE switch ports using manual configuration if supported by your devices. Flow Control Settings: Ensure that flow control settings are configured properly across all network interfaces involved (NICs and switch). Incorrect flow control settings could potentially limit throughput. iPerf3 Parameters: Check the iperf3 parameters you're using for testing. If you're not specifying the number of parallel connections (-P), this might limit the bandwidth used during the test. Network Overhead: Don't forget that some network overhead is normal and expected, so even if your link is running at 10 Gbps, actual throughput will be slightly less due to protocol overhead (around 3% for UDP traffic with iperf3). To investigate further: Try using a different cable or SFP+ module to rule out hardware issues. Monitor the network interfaces' status and speed on all devices involved. You can use commands like ip link on Linux-based systems or check the device manager in Windows. Check flow control settings (tx-usc, rx-usc) and ensure they are configured consistently across all devices. Run iperf3 with different parameters to see if you can achieve higher throughput (e.g., use -P 16 for 16 parallel connections). Use other network tools like ping or netcat (nc) to verify the connection speed, as they might behave differently than iperf3.