Worker Troubleshooting Guide
  • Introduction
    • (Important) Requirements for running Workers
  • Environment Setup Guide
    • Windows
      • Installing WSL2 (Important)
    • Mac OS
    • Linux
  • How to re-run the Docker
    • Windows
    • Mac OS
    • Linux
  • FAQs
    • Containers's CPU are 0%
    • Docker running normally but Worker not connecting
    • Containers disappear
    • Worker's blocked
    • Unsupported status
    • Workers disappear
    • Can't connect new worker
    • Multiple containers are running.
    • UI bugs and issues
    • Creating multiple workers from same device
    • Incompatible CPU detected
    • Bad CPU type in executable
    • Unexpected WSL error
    • Vmmem use much ram usage
    • FAQs from team
    • 🆘NOTE
Powered by GitBook
On this page
  1. FAQs

Docker running normally but Worker not connecting

PreviousContainers's CPU are 0%NextContainers disappear

Last updated 1 year ago

Sometimes you met the case that , but the worker notices Disconnected, this issue occurs due to two reasons:

  • UI Error: This issue may arise due to a UI error, leading to inaccurate information displayed on the dashboard. This error is still under investigation by the team.

  • Backend and Frontend don't sync: Another possibility is the backend and frontend haven't beeen synchronized, resulting in the worker not being connected.

But anw, if your docker's running smoothly, your uptime will be recorded 100% and you still receive airdrop confirmed by the team.

Docker is running normally