Problem while installing Self-hosted Extension

[Silambarasan Raju]

When I add an extension through enterprise policy under ExtensionInstallForcelist with extension_id;<locallyhosted_server_url>

The policy applied successfully & it shows no error. but the extension doesn't installed automatically. but If i visit the server url once, it get installed.

The server doesn't use any third party certificate & I just used the self-signed certificate.

Is Installing the extension from self-hosted server without third party certificate cause issue like this?
is this known behaviour? 

Please help in this case.....!!!!!

[Oliver Dunk]

Hi,

Could you expand on this?

If i visit the server url once, it get installed

I wouldn't expect visiting the URL to make a difference, so my only guess would be that maybe visiting the URL provides some authentication or other activity that allows you to download the file.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/88b0eb1b-3b0b-4fc7-bf50-b088d1bc7e0bn%40chromium.org.

[Silambarasan Raju]

But the server doesn't use any authorization/authentication to serve this file.

I have suspect that there is something like SSL error. that the server doesn't use any third party certificate that it only uses self-signed certificate. 

Installing chrome extension from the server which uses self-signed certificate is trusted or not.

If you have any query please revert this thread. 

[Oliver Dunk]

Is the self-signed certificate trusted on your machine or do you have to bypass some warnings to reach the site?

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Silambarasan Raju]

It is trusted on my machine, no such warnings are triggered. but when i checked in debug logs, it says responce code -1. I have attached the error info for your reference.

[11716:5572:1011/150821.183:VERBOSE1:extension_downloader.cc(754)] Failed to fetch manifest 'https://<server_url>:8383/xxx/xxx/meta-file-name.xml?os=win&arch=x64&os_arch=x86_64&nacl_arch=x86-64&prod=chromecrx&prodchannel=&prodversion=118.0.5993.71&lang=en-US&acceptformat=crx3,puff&x=id%3Dkikjjbklamkmdfipkcajcccnmgjfijan%26v%3D0.0.0.0%26installsource%3Dnotfromwebstore%26installedby%3Dpolicy%26uc' response code:-1

[Oliver Dunk]

Thanks for sharing that.

I could definitely imagine self-signed certificates being the problem, but I'm not sure how that system works.

The best option is probably to file a bug at https://crbug.com/. That should reach the right people and they can close it with an answer if this turns out to be working as intended.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Silambarasan Raju]

Thanks for your time being response.

I will proceed with filing bug, 

thank you so much ^_^

[Pavel Aronovich]

Do you have the update_url address specified in the extension manifest?
Try using HTTP and it will be clear whether the certificate error or not.
Try using the ExtensionSettings policy. It is better to use it.

среда, 11 октября 2023 г. в 15:27:39 UTC+3, Silambarasan Raju:

[Silambarasan Raju]

Yes, I have tried with http and its working properly, the only issue is when it is https & I have used third party vendor certificate which is trusted by chrome root as well, still it says same issue mentioned above(failed to fetch manifest -1).

Yes the update_url points to google actual update_url & not to the meta xml. but it works in other machine, so i suspect the update_url in manifest doesn't give this issue so.