We have moved to a new Sailfish OS Forum. Please start new discussions there.

[SDK] Can't connect to Build Engine or Emulator on 1801

asked 2018-06-02 16:57:02 +0300

Ingvix gravatar image

Cables are connected in settings so it's not like the previous case. SSH daemon wasn't even on when I checked on build engine but I couldn't connect to it even after starting it.

I'm on Windows 7.

edit retag flag offensive close delete


Is this right after installation? Does disabling antivirus help? What is the exact error when trying to connect with SSH from command line line described here https://sailfishos.org/wiki/Tutorial_-_Building_packages_manually? If you know how to retrieve application debug output on Windows, you can start Qt Creator with QT_LOGGING_RULES="mer.vms=true" defined in environment to collect related logs.

martyone ( 2018-06-04 07:29:16 +0300 )edit

@martyone Yes, right after fresh installation. Disabling antivirus doesn't help. I'm on Windows so I can't really run that exact command but in general connection is refused when I try to connect it via SSH. I'm afraid I don't know how to retrieve debug application on Windows.

It sort of seems that emulator and build engine have no working network connection at all so I can't reach them with it.

Ingvix ( 2018-06-04 22:25:07 +0300 )edit

@Ingvix Please start the build engine virtual machine, then run the following commands and paste the output:

  • "c:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo "Sailfish OS Build Engine"
  • netstat -abn

Run the following commands inside the build engine and paste the output

  • sudo ss -tulnp
  • /sbin/ip a
  • /sbin/ip r
martyone ( 2018-06-05 08:15:32 +0300 )edit

Here are the local command outputs:

I can't really copy from the build engine as I don't have the SSH connection so I took a picture:

Ingvix ( 2018-06-05 12:02:56 +0300 )edit

@Ingvix According to the netstat output VirtualBox does not listen on any port on your host - check this post https://forums.virtualbox.org/viewtopic.php?f=6&t=33850#p151484. According to the VBoxManage output the second virtual network adapter has not "cable connected" - you can fix this in virtual machine settings > Network > Adapter 2 > Advanced (not sure why this happened, maybe another consequence of the former issue).

martyone ( 2018-06-05 17:13:24 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2019-09-17 01:40:23 +0300

bongo gravatar image

Same problem here on Win10 withSailfish sdK 2.24

  • Tried turning off windows firewall
  • tried running virtualbox manager as admin, and starting vms from there
  • virtualbox was warning about error in configuration (no hardware virtualization), so fixed that.
edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2018-06-02 16:57:02 +0300

Seen: 570 times

Last updated: Sep 17 '19