# "web-ext sign" command is timing out

**URL:** <https://discourse.mozilla.org/t/web-ext-sign-command-is-timing-out/49670>\
**Category:** Add-ons\
**Created:** [December 2, 2019, 11:12pm UTC](https://discourse.mozilla.org/t/web-ext-sign-command-is-timing-out/49670 "2019-12-02T23:12:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![forcepoint\_endpoint](https://avatars.discourse-cdn.com/v4/letter/f/ecb155/32.png) [@forcepoint\_endpoint](https://discourse.mozilla.org/u/forcepoint_endpoint)\
**Post date:** [December 2, 2019, 11:12pm UTC](https://discourse.mozilla.org/t/web-ext-sign-command-is-timing-out/49670/1 "2019-12-02T23:12:33Z")

</div>

Since 11/21/2019, we are seeing an error when using “web-ext sign” to generate our Firefox extension. There have been no code changes to the extension when the issue started occuring. The command has only been successful 3 times in the last ~30 attempts. When logging into our Mozilla dev account, we can see that all submissions have passed all of the Firefox extension tests, but the command is still failing. We’ve tried updating NPM and NodeJS to latest versions, but the issue still occurs. We specified a timeout of 20 minutes and still see the issue.

> web-ext sign --api-key=user:\*\*\*\*\*\*\* --api-secret=\*\*\*\*\*\*\*\*  
> Building web extension from C:\Users\Administrator.DELL123456\Desktop\New folder\dlpext\dlpext  
> Validating add-on […]
> 
> sign: Error: Validation took too long to complete; last status: {“[guid":"fpdlpffext3@forcepoint.com](mailto:guid%22:%22fpdlpffext3@forcepoint.com)”,“active”:false,“automated\_signing”:true,“url”:"[https://addons.mozilla.org/api/v3/addons/fpdlpffext3@forcepoint.com/versions/8.1.4402.102/uploads/12b670d85045423a9f29c791d2ac187e/",“files”:[{“download\_url”:“https://addons.mozilla.org/api/v3/file/3460180/forcepoint\_endpoint-8.1.4402.102-an+fx.xpi?src=api”,“hash”:“sha256:2e724be07ada0ca6f94627379f7e4a7fb9926ca34d429c8b031bcf20428cd961”,“signed”:false}],“passed\_review”:false,“pk”:"12b670d85045423a9f29c791d2ac187e](https://addons.mozilla.org/api/v3/addons/fpdlpffext3@forcepoint.com/versions/8.1.4402.102/uploads/12b670d85045423a9f29c791d2ac187e/%22,%22files%22:%5B%7B%22download_url%22:%22https://addons.mozilla.org/api/v3/file/3460180/forcepoint_endpoint-8.1.4402.102-an+fx.xpi?src=api%22,%22hash%22:%22sha256:2e724be07ada0ca6f94627379f7e4a7fb9926ca34d429c8b031bcf20428cd961%22,%22signed%22:false%7D%5D,%22passed_review%22:false,%22pk%22:%2212b670d85045423a9f29c791d2ac187e)…  
> at Timeout.\_onTimeout (C:\Program Files\nodejs\web-ext-master\node\_modules\sign-addon\dist\webpack:\src\amo-client.js:222:16)  
> at ontimeout (timers.js:386:14)  
> at tryOnTimeout (timers.js:250:5)  
> at Timer.listOnTimeout (timers.js:214:5)

---

<div class="post-metadata">

**Author:** ![caitlin](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/caitlin/32/6091_2.png) [@caitlin](https://discourse.mozilla.org/u/caitlin)\
**Post date:** [December 2, 2019, 11:51pm UTC](https://discourse.mozilla.org/t/web-ext-sign-command-is-timing-out/49670/2 "2019-12-02T23:51:35Z")

</div>

Hi @forcepoint_endpoint, it sounds like you may have encountered the timeout error from [recent changes to the AMO submission flow](https://blog.mozilla.org/addons/2019/11/11/security-improvements-in-amo-upload-tools/). Have you tried updating web-ext to v2.3.1?

---

<div class="post-metadata">

**Author:** ![forcepoint\_endpoint](https://avatars.discourse-cdn.com/v4/letter/f/ecb155/32.png) [@forcepoint\_endpoint](https://discourse.mozilla.org/u/forcepoint_endpoint)\
**Post date:** [December 3, 2019, 12:14am UTC](https://discourse.mozilla.org/t/web-ext-sign-command-is-timing-out/49670/3 "2019-12-03T00:14:15Z")

</div>

Hi Caitlin. I updated the version of web-ext last week to 3.2.1 and the “web-ext sign” command still fails.

I also see this failure frequently also:

> Potentially unhandled rejection [1] Error: connect ETIMEDOUT 34.215.211.225:443 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1129:14)

Pinging [addons.mozilla.org](http://addons.mozilla.org) at that time gives me the same IP address 34.215.211.225

---

<div class="post-metadata">

**Author:** ![caitlin](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/caitlin/32/6091_2.png) [@caitlin](https://discourse.mozilla.org/u/caitlin)\
**Post date:** [December 3, 2019, 1:48pm UTC](https://discourse.mozilla.org/t/web-ext-sign-command-is-timing-out/49670/4 "2019-12-03T13:48:31Z")

</div>

Thanks @forcepoint_endpoint! The logs show the versions have been approved with no errors so far. The network error is a little weird and looks more like a connectivity issue than a problem with the API.

If this persists, can you file an issue on the [web-ext repo](https://github.com/mozilla/web-ext/issues)?

In the meantime, are you able to successfully submit new versions through [addons.mozilla.org](http://addons.mozilla.org)?

---

<div class="post-metadata">

**Author:** ![forcepoint\_endpoint](https://avatars.discourse-cdn.com/v4/letter/f/ecb155/32.png) [@forcepoint\_endpoint](https://discourse.mozilla.org/u/forcepoint_endpoint)\
**Post date:** [December 3, 2019, 7:35pm UTC](https://discourse.mozilla.org/t/web-ext-sign-command-is-timing-out/49670/5 "2019-12-03T19:35:59Z")

</div>

Okay, I’ve opened an issue under [https://github.com/mozilla/web-ext/issues/1773](https://github.com/mozilla/web-ext/issues/1773).

We are able to manually submit new versions through [addons.mozilla.org](http://addons.mozilla.org). It seems like we won’t have a fix for web-ext sign right away, so we’ll have to change our build process to handle this step manually.