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

Can't connect new worker

PreviousWorkers disappearNextMultiple containers are running.

Last updated 1 year ago

This issue can stem from several common reasons:

  • The GPU/CPU you're using to run the worker is not supported,

  • Docker is not running properly on your system.

  • You have low internet connection speed. You can check

  • The backend and frontend haven't synchronized, should wait for at least 30 minutes, as advised by the project.

check
here