electron-build-service icon indicating copy to clipboard operation
electron-build-service copied to clipboard

Error: Cannot get, wait error=Get https://service.electron.build/find-build-agent?no-cache=1f42oro: dial tcp 51.15.76.176:443:

Open ThummalaJanardhanReddy opened this issue 5 years ago • 19 comments

I'm getting below error while building AppImage for linux on windows OS.

• cannot get, wait error=Get https://service.electron.build/find-build-agent?no-cache=1f42oro: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. attempt=0 waitTime=2 • cannot get, wait error=Get https://service.electron.build/find-build-agent?no-cache=1f42oro: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. attempt=1 waitTime=4 • cannot get, wait error=Get https://service.electron.build/find-build-agent?no-cache=1f42oro: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. attempt=2 waitTime=6 ⨯ Get https://service.electron.build/find-build-agent?no-cache=1f42oro: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
⨯ C:\Users\mcw\AppData\Roaming\npm\node_modules\electron-builder\node_modules\app-builder-bin\win\x64\app-builder.exe exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE stackTrace=..

can any one please tell me that is this service issue or my application configuration issue ?

ThummalaJanardhanReddy avatar Feb 10 '20 14:02 ThummalaJanardhanReddy

I have the same problem

BriceFab avatar May 24 '20 08:05 BriceFab

I get same error for linux-build but windows build is OK. ` ⨯ Get https://service.electron.build/find-build-agent?no-cache=1fco0dr: dial tcp 51.15.76.176:443: connectex: No connection could be made because the target machine actively refused it.

ERROR Error: C:\Users\sissi\apps\translatedictionary\node_modules\app-builder-lib\node_modules\app-builder-bin\win\x64\app-builder.exe exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE`

frankjoke avatar May 25 '20 17:05 frankjoke

I get same error for linux-build but windows build is OK. ` ⨯ Get https://service.electron.build/find-build-agent?no-cache=1fco0dr: dial tcp 51.15.76.176:443: connectex: No connection could be made because the target machine actively refused it.

ERROR Error: C:\Users\sissi\apps\translatedictionary\node_modules\app-builder-lib\node_modules\app-builder-bin\win\x64\app-builder.exe exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE`

I have some problem, can you tell me how do you build electron-app for linux?

miyanoyuriko avatar Jun 11 '20 07:06 miyanoyuriko

up! OS: Windows 10 Pro command: electron webpack && electron-builder -lw log: ⨯ Get "https://service.electron.build/find-build-agent?no-cache=1fj7io1": dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ⨯ C:\Users\WELLD\Workspace\Client\electron\node_modules\app-builder-bin\win\x64\app-builder.exe exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE stackTrace= Error: C:\Users\WELLD\Workspace\Client\electron\node_modules\app-builder-bin\win\x64\app-builder.exe exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE

Silvano14 avatar Aug 12 '20 09:08 Silvano14

same here.
OS: Win 10 Home 2004 log:

  • cannot get, wait  error=Get https://service.electron.build/find-build-agent?no-cache=1fmonpg: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
                      attempt=0
                      waitTime=2
  • building block map  blockMapFile=dist_electron\mfm Setup 0.5.0.exe.blockmap
  • cannot get, wait  error=Get https://service.electron.build/find-build-agent?no-cache=1fmonpg: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
                      attempt=1
                      waitTime=4
  • cannot get, wait  error=Get https://service.electron.build/find-build-agent?no-cache=1fmonpg: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
            

my command:

npm run electron:build -- --linux deb --win nsis

dhanyn10 avatar Sep 24 '20 09:09 dhanyn10

Unfortunately the https://service.electron.build has been down since months and it doesn't seem that such issue will be fixed anytime soon, as we can see from the amount of (mostly open) GitHub issues that have been opened from users that are trying to deal with such problem in the past months.

Here's a viable alternative to build a redistributable Linux package on a Windows 10 environment: I'll try to explain it using a step-by-step approach in order to make it as easy as possible for those who don't know Docker well.

  • Install Docker from here
  • Download the electronuserland/builder Docker image with the following console command: docker pull electronuserland/builder
  • From the Electron project's root folder (such as C:\MyApp), type the following command-line command to run the container and map the Electron project's root folder to the /project virtual path: docker run -rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder
  • From inside the container, type the following commands to upgrade the Electron project's Yarn packages, globally install the electron-builder package and build the Linux redistributable package:
cd /project
yarn upgrade
yarn global add electron-builder
electron-builder -l

If everything went smooth, you should be able to locate your MyApp.deb file (or rpm, AppImage, or anything you've configured within the electron-builder's package.json file) inside the Electron project's /dist/ folder.

For further info about this whole procedure and a bit of background, check out this post on my blog.

Darkseal avatar Oct 06 '20 06:10 Darkseal

Unfortunately the https://service.electron.build has been down since months and it doesn't seem that such issue will be fixed anytime soon, as we can see from the amount of (mostly open) GitHub issues that have been opened from users that are trying to deal with such problem in the past months.

Here's a viable alternative to build a redistributable Linux package on a Windows 10 environment: I'll try to explain it using a step-by-step approach in order to make it as easy as possible for those who don't know Docker well.

  • Install Docker from here
  • Download the electronuserland/builder Docker image with the following console command: docker pull electronuserland/builder
  • From the Electron project's root folder (such as C:\MyApp), type the following command-line command to run the container and map the Electron project's root folder to the /project virtual path: docker run -rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder
  • From inside the container, type the following commands to upgrade the Electron project's Yarn packages, globally install the electron-builder package and build the Linux redistributable package:
cd /project
yarn upgrade
yarn global add electron-builder
electron-builder -l

If everything went smooth, you should be able to locate your MyApp.deb file (or rpm, AppImage, or anything you've configured within the electron-builder's package.json file) inside the Electron project's /dist/ folder.

For further info about this whole procedure and a bit of background, check out this post on my blog.

This also seems to work with just wsl instead of docker (at least for me)

EverlyScott avatar Oct 18 '20 05:10 EverlyScott

Hi @ScribbleNerd, that's good to know!

Darkseal avatar Oct 18 '20 12:10 Darkseal

Unfortunately the https://service.electron.build has been down since months and it doesn't seem that such issue will be fixed anytime soon, as we can see from the amount of (mostly open) GitHub issues that have been opened from users that are trying to deal with such problem in the past months.

Here's a viable alternative to build a redistributable Linux package on a Windows 10 environment: I'll try to explain it using a step-by-step approach in order to make it as easy as possible for those who don't know Docker well.

  • Install Docker from here
  • Download the electronuserland/builder Docker image with the following console command: docker pull electronuserland/builder
  • From the Electron project's root folder (such as C:\MyApp), type the following command-line command to run the container and map the Electron project's root folder to the /project virtual path: docker run -rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder
  • From inside the container, type the following commands to upgrade the Electron project's Yarn packages, globally install the electron-builder package and build the Linux redistributable package:
cd /project
yarn upgrade
yarn global add electron-builder
electron-builder -l

If everything went smooth, you should be able to locate your MyApp.deb file (or rpm, AppImage, or anything you've configured within the electron-builder's package.json file) inside the Electron project's /dist/ folder.

For further info about this whole procedure and a bit of background, check out this post on my blog.

It works,but the command should be: docker run --rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder The -rm flag should be --rm

JasonkayZK avatar Nov 08 '20 09:11 JasonkayZK

Unfortunately the https://service.electron.build has been down since months and it doesn't seem that such issue will be fixed anytime soon, as we can see from the amount of (mostly open) GitHub issues that have been opened from users that are trying to deal with such problem in the past months. Here's a viable alternative to build a redistributable Linux package on a Windows 10 environment: I'll try to explain it using a step-by-step approach in order to make it as easy as possible for those who don't know Docker well.

  • Install Docker from here
  • Download the electronuserland/builder Docker image with the following console command: docker pull electronuserland/builder
  • From the Electron project's root folder (such as C:\MyApp), type the following command-line command to run the container and map the Electron project's root folder to the /project virtual path: docker run -rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder
  • From inside the container, type the following commands to upgrade the Electron project's Yarn packages, globally install the electron-builder package and build the Linux redistributable package:
cd /project
yarn upgrade
yarn global add electron-builder
electron-builder -l

If everything went smooth, you should be able to locate your MyApp.deb file (or rpm, AppImage, or anything you've configured within the electron-builder's package.json file) inside the Electron project's /dist/ folder. For further info about this whole procedure and a bit of background, check out this post on my blog.

This also seems to work with just wsl instead of docker (at least for me)

How to get it packaged with WSL 2 ? Care to provide how to map the windows project path? I have WSL2 with Ubuntu 20xx setup but don't know how to get it packaged.

makers-cave avatar Apr 21 '21 13:04 makers-cave

same here

⨯ Get "https://service.electron.build/find-build-agent?no-cache=1ga9ac2": dial tcp 51.15.76.176:443: connectex: No connection could be made because the target machine actively refused it.

AmarsDing avatar May 19 '21 06:05 AmarsDing

Update December 2021

It's still like that

Bump. Help.

A-Eugene avatar Dec 23 '21 04:12 A-Eugene

@A-Eugene reading this thread makes me understand that there is no plan on fixing this and the workaround is to use the docker image

tomwolfgang avatar Jan 06 '22 09:01 tomwolfgang

Update April 2022

It's still like that

Bump.

jviaches avatar Apr 09 '22 12:04 jviaches

Same

ildar-in avatar May 20 '22 08:05 ildar-in

Same here:

⨯ Get "https://service.electron.build/find-build-agent?no-cache=1hap2p4": dial tcp 51.15.76.176:443: connectex: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione.

el3um4s avatar Jun 17 '22 14:06 el3um4s

@el3um4s you can use docker.

dhanyn10 avatar Jun 19 '22 14:06 dhanyn10

Unfortunately the https://service.electron.build/ has been down since months and it doesn't seem that such issue will be fixed anytime soon, as we can see from the amount of (mostly open) GitHub issues that have been opened from users that are trying to deal with such problem in the past months.

Here's a viable alternative to build a redistributable Linux package on a Windows 10 environment: I'll try to explain it using a step-by-step approach in order to make it as easy as possible for those who don't know Docker well.

Install Docker from here Download the electronuserland/builder Docker image with the following console command: docker pull electronuserland/builder From the Electron project's root folder (such as C:\MyApp), type the following command-line command to run the container and map the Electron project's root folder to the /project virtual path: docker run --rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder From inside the container, type the following commands to upgrade the Electron project's Yarn packages, globally install the electron-builder package and build the Linux redistributable package:

cd /project
yarn upgrade
yarn global add electron-builder
electron-builder -l

If everything went smooth, you should be able to locate your MyApp.deb file (or rpm, AppImage, or anything you've configured within the electron-builder's package.json file) inside the Electron project's /dist/ folder.

For further info about this whole procedure and a bit of background, check out this post on Ryadel Blog.

Make sure to enable the Hyper-V Feature with this command on administrator Powershell Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

arnon001 avatar Aug 29 '22 18:08 arnon001

same here. log:

  • cannot get, wait  error=Get "https://service.electron.build/find-build-agent?no-cache=1it6rqj": dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
                      attempt=0
                      waitTime=2
  • cannot get, wait  error=Get "https://service.electron.build/find-build-agent?no-cache=1it6rqj": dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
                      attempt=1
                      waitTime=4
  • cannot get, wait  error=Get "https://service.electron.build/find-build-agent?no-cache=1it6rqj": dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
                      attempt=2
                      waitTime=6
  ⨯ Get "https://service.electron.build/find-build-agent?no-cache=1it6rqj": dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

This problem still exists, and it seems that only Linux hosts can be used to build it now

BoyChai avatar Feb 19 '24 15:02 BoyChai