10 — Troubleshooting

In this section we will describe most common problems and how to fix them. At the beginning if you do not have a public IP address, then make sure, that you have forwarded ports 40102, 40103 and 3282 on your router and this ports are not blocked on your firewall. Without that, Golem would not work properly. Please follow instruction from: Bitcoin enabling connection section, but use ports 40102, 40103 and 3282 instead of 8333 and 18333

  • After starting Golem you cannot connect to the network (Windows)

    First of all, check if you have Golem, Geth, Docker and hyperg in your system Path
    You can do that by typing echo %path% in the command line and checking if they are present. Default locations are:
    Docker - C:\Program Files\Docker Toolbox
    Geth - C:\Program Files\Geth
    Golem - C:\Program Files\Golem
    HyperG - C:\Program Files\HyperG

    If you do not have any of them, please add missing ones to the Path and reboot your PC, to reload Path.

    If it does not help, type in the command line:
    docker-machine env golem

    If it returns an error Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"
    you need to enable VT-X/AMD-v in your BIOS.

    If it returns an error host does not exist: 'golem', type
    docker-machine create golem --driver virtualbox,
    then type in cmd:
    docker-machine start golem

    If it returns no error, and shows configuration, then type:
    @FOR /f "tokens=*" %i IN ('docker-machine env golem') DO @%i
    in the cmd or
    & "C:\Program Files\Docker Toolbox\docker-machine.exe" env golem | Invoke-Expression
    in the PowerShell

  • When you start Golem you get error:

    Failed to import script golemapp

    Probably you have some geth process in background. Close Golem, then kill Geth process and try to launch Golem again

  • When you start Golem you get error:

    could not read CA certificate "C:\\Users\\USER_NAME\\.docker\\machine\\machines\\default \\ca.pem": open C:\Users\USER_NAME\.docker\machine\machines\default \ca.pem: The system cannot find the path specified.

    Type in command line docker-machine regenerate-certs golem

  • When you start Golem you get error

    INFO [05-10|18:59:19] Block synchronisation started


    INFO [golem.client] Waiting for block synchronization…

    Just wait. Sometimes geth need some time to start synchronisation

  • When you start Golem you get error

    ERROR [golem.docker.manager] DockerMachine: failed to start the VM: Command '['docker-machine', 'start', 'golem']' returned non-zero exit status 1 Error checking TLS connection: machine does not exist

    Type the following commands in the command line:

    docker-machine create golem --driver virtualbox
    docker-machine start golem
    eval $(docker-machine env golem)

  • When you start Golem you get error

    Error with pre-create check: "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)"

    You can disable Hyper-V by typing in command line (with administrator priveleges):

    dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All


    Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

  • All subtasks fail with error

    Traceback: : HTTPConnectionPool(host='', port=3292): Max retries exceeded with url: /api (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',))

    Make sure that you've got HyperG in your PATH. If you don't, add it manually to PATH and restart Golem. You can also try to reinstall HyperG

  • In the log I can see

    WARNING [golem.network.transport.tcpnetwork ] Deserialization of message failed
    WARNING [golem.task.tasksession] Fail to decrypt message wrong ecies header


    Failed to import scrypt. This is not a fatal error but does mean that you cannot create or decrypt privkey jsons that use scrypt

    You don’t have to worry about it. It’s just a warning

Other useful links