Reputation: 19571
We have created a chrome extension for our Team Members and we want to self host it.
I am aware of the non-web store install policies and I feel like I have set this up correctly but it does not work.
Here is what I have:
I set up my manifest with an update url and an extension id key like this:
{
"update_url": "https://ourownserver.com/extensions/updates.xml",
"key":"obljkonioibfihfjbaiidbobmckpkned",
....
}
I created updates.xml
like this:
<gupdate xmlns="http://www.google.com/update2/response" protocol="2.0">
<app appid="obljkonioibfihfjbaiidbobmckpkned">
<updatecheck codebase="some-extension.crx" version="3.6"/>
</app>
</gupdate>
I used the chrome://extensions
to package the .crx and .pem files and droped them all into https://ourownserver.com/extensions/
like this:
I used regedit to add the ExtensionInstallWhitelist
and ExtensionInstallSources
under HKEY_LOCAL_MACHINE
as follows:
I then closed Chrome and re-opened it
After doing all of this, I expect that going to https://ourownserver.com/extensions/extensionName.crx
will instal the extension and that it will be enabled. However, if I go https://ourownserver.com/extensions/extensionName.crx
I still get:
And on the extensions tab, it is installed but disabled and has this message:
Im thinking that I have not added the registry entries correctly but I cant find a more detailed walkthrough to be sure.
What am I doing wrong here?
Upvotes: 2
Views: 3726
Reputation: 1984
Your update XML needs to contain the absolute path of the extension CRX, rather than the relative one. For example:
<gupdate xmlns="http://www.google.com/update2/response" protocol="2.0">
<app appid="obljkonioibfihfjbaiidbobmckpkned">
<updatecheck codebase="https://ourownserver.com/extensions/some-extension.crx" version="3.6"/>
</app>
</gupdate>
Upvotes: 2