# Self-hosted WebExt extension has no "update\_url" and "id" in manifest.json file

**URL:** <https://discourse.mozilla.org/t/self-hosted-webext-extension-has-no-update-url-and-id-in-manifest-json-file/22739>\
**Category:** Add-on Support\
**Created:** [November 30, 2017, 6:15am UTC](https://discourse.mozilla.org/t/self-hosted-webext-extension-has-no-update-url-and-id-in-manifest-json-file/22739 "2017-11-30T06:15:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![oleg.usmanov1991](https://avatars.discourse-cdn.com/v4/letter/o/8baadc/32.png) [@oleg.usmanov1991](https://discourse.mozilla.org/u/oleg.usmanov1991)\
**Post date:** [November 30, 2017, 6:15am UTC](https://discourse.mozilla.org/t/self-hosted-webext-extension-has-no-update-url-and-id-in-manifest-json-file/22739/1 "2017-11-30T06:15:40Z")

</div>

We had an old self-hosted extension in a XUL format, that was updated using “updateURL” and “Id” in install.rdf file.  
Then we published new WebExt extension, but without “id” and “update\_url” in the manifest file.  
Is there a way to update this version now?

---

<div class="post-metadata">

**Author:** ![erosman](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/erosman/32/15447_2.png) [@erosman](https://discourse.mozilla.org/u/erosman)\
**Post date:** [November 30, 2017, 8:13am UTC](https://discourse.mozilla.org/t/self-hosted-webext-extension-has-no-update-url-and-id-in-manifest-json-file/22739/2 "2017-11-30T08:13:10Z")

</div>

AFAIK, since each update needs to be signed in order to work, even if there is an update URL, it would not be useful since even if the addon is updated with that URL, it wont run.

---

<div class="post-metadata">

**Author:** ![oleg.usmanov1991](https://avatars.discourse-cdn.com/v4/letter/o/8baadc/32.png) [@oleg.usmanov1991](https://discourse.mozilla.org/u/oleg.usmanov1991)\
**Post date:** [November 30, 2017, 8:45am UTC](https://discourse.mozilla.org/t/self-hosted-webext-extension-has-no-update-url-and-id-in-manifest-json-file/22739/3 "2017-11-30T08:45:51Z")

</div>

New WebExt addon has been signed and used for updating. It contains META-INF folder with signature files. Currently users have this WebExt addon installed, but it has no id and update\_url in its manifest file. So it has no ways to track new updates now. Can it still be updated?

---

<div class="post-metadata">

**Author:** ![erosman](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/erosman/32/15447_2.png) [@erosman](https://discourse.mozilla.org/u/erosman)\
**Post date:** [November 30, 2017, 8:52am UTC](https://discourse.mozilla.org/t/self-hosted-webext-extension-has-no-update-url-and-id-in-manifest-json-file/22739/4 "2017-11-30T08:52:01Z")

</div>

> [@oleg.usmanov1991](#):
>
> Can it still be updated?

AFAIK, there is no automatic system.@jorgev knows more about it.

---

<div class="post-metadata">

**Author:** ![jorgev](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jorgev](https://discourse.mozilla.org/u/jorgev)\
**Post date:** [November 30, 2017, 4:48pm UTC](https://discourse.mozilla.org/t/self-hosted-webext-extension-has-no-update-url-and-id-in-manifest-json-file/22739/5 "2017-11-30T16:48:52Z")

</div>

Add-ons with no `update_url` can only be updated in a couple of ways:

- Manually by the user installing a new version.
- Via an application installer. Many self-hosted add-ons are installed by an application, so an application update can also update the add-on.
- Via AMO. Add-ons with no `update_url` check AMO for updates, so you can submit a new listed version that will be delivered to those users. However, that would be the only way to update those users, and you would effectively have a listed AMO add-on after that.