# Intranet hosting

**URL:** <https://discourse.mozilla.org/t/intranet-hosting/18606>\
**Category:** addons.mozilla.org\
**Created:** [August 31, 2017, 9:05am UTC](https://discourse.mozilla.org/t/intranet-hosting/18606 "2017-08-31T09:05:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![habett](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/habett/32/30896_2.png) [@habett](https://discourse.mozilla.org/u/habett)\
**Post date:** [August 31, 2017, 9:05am UTC](https://discourse.mozilla.org/t/intranet-hosting/18606/1 "2017-08-31T09:05:36Z")

</div>

Hello there,

I’m trying to setup auto-update for an addon that is designed for internal use inside the firm I work for.  
My problem is that we don’t have an internal https server. So I’ve set the update\_url to point to an http address of an intranet server here and created the accordingly needed updates.json but I just can’t find a way to get it right.  
So is it really possible to achieve auto update for an add-on hosted on an intranet server ?

Thanks for your help.

---

<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:** [September 6, 2017, 8:04pm UTC](https://discourse.mozilla.org/t/intranet-hosting/18606/2 "2017-09-06T20:04:35Z")

</div>

Have you looked into [Let’s Encrypt](https://letsencrypt.org/)? It should be fairly easy to set up an HTTPS server.

If that doesn’t work, I think the only way to get updates of plain HTTP is to sign your updates, and I think that only works with the old RDF update file. See this documentation for an explanation:

> **[Extension Versioning, Update and Compatibility](https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Extension_Versioning,_Update_and_Compatibility)**
>
> Add-ons should specify their versions using the Toolkit version format. As a rough overview this is a version string split by periods, some examples:

---

<div class="post-metadata">

**Author:** ![habett](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/habett/32/30896_2.png) [@habett](https://discourse.mozilla.org/u/habett)\
**Post date:** [September 7, 2017, 4:53am UTC](https://discourse.mozilla.org/t/intranet-hosting/18606/3 "2017-09-07T04:53:36Z")

</div>

As far as I remember LetsEncrypt requires visibility of the server on the internet so that it can verify the host, and the host is an intranet server so the verification will fail.  
I am in the new format.

---

<div class="post-metadata">

**Author:** ![habett](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/habett/32/30896_2.png) [@habett](https://discourse.mozilla.org/u/habett)\
**Post date:** [September 7, 2017, 5:24am UTC](https://discourse.mozilla.org/t/intranet-hosting/18606/4 "2017-09-07T05:24:36Z")

</div>

I have placed a mirroring script on a outside visible https server hat mirrors the intranet updates.json and it works as expected. Not so good a solution but it does the job.