We have a chrome extension that is running well on private accounts but we tackled with the following error on some accounts:
Unchecked runtime.lastError: This page cannot be scripted due to an ExtensionsSettings policy.
The extension has content script and edits some pages.
How can we fix this?
Related
How to force install a self hosted chrome extension in my organization?
I went over the requirements detailed in the official documentation.
I have packed the extension with Chrome's "pack extension" button, hosting it in a publicly accessible location, headers are as required. The extension is very basic.
Works when I load it (unpacked), when I manually download it, it shows "package is invalid, CRX proof required" which is fine, because it's not from the Web Store.
To force deploy it I use the google admin panel (Adding the extension by ID from a custom URL)
Any further ideas?
Search for the following setting in your Google Admin Portal:
"Allow insecure extension packaging", set it to "Allow insecurely packaged extensions" and try again.
In the Azure Portal, in certain scenarios when it prompts me to open a URL in a new tab, I get a 403 error.
"Error 403 - This web app is stopped"
I have followed the help link on that page (https://blogs.msdn.microsoft.com/waws/2016/01/05/azure-web-apps-error-403-this-web-app-is-stopped/), but none of these issues (see footnote for issues) apply to me.
Specific examples of when I get this message:
In an app service > App Service Diagnostics > Collect Memory Dump: the report is available to view in a pop-out URL. When I click on the link, it opens a new browser tab and I can see from the url that it's attempting an oauth sign-in, which eventually displays the 403 page.
In an app service > App Service Editor (Preview), when I click on the "Go" link, as before, it opens a new browser tab and I can see from the url that it's attempting an oauth sign-in, which eventually displays the 403 page.
In both cases, it redirects to a https://****.sso.azurewebsites.net url which displays the 403 message.
Any suggestions?
Footnote: According to that url, there are 3 conditions that can cause this error to be presented.
The site has reached a billing limit and your site has been disabled.
The Website has been stopped in the portal.
The Azure Website has reached a resource quota limit that applies to either Free or Shared scale modes.
Based on Ivan's comment, I checked my role settings. I was a Contributor for this Azure subscription. Since I changed it to an Owner (via Access control IAM > Role Assignments), it now works as expected.
It's frustrating that this is not made obvious in the Azure Portal.
In my case, There were network IP restrictions applied to the site. So I was getting the same error above from my home network. You can check the rules by going to the properties tab. To modify, go to Networking->Configure access restrictions.
If you are only getting the error when you open a new tab, it could be a problem with the maximum number of connections.
Are you running in debug mode? For Basic and below the maximum number of debug connections is 1.
We customised our Azure AD B2C tenant's Combined Sign-Up/Sign-In Policy to serve up our own login page. This worked across all the major browsers when we tested last week, but it stopped working today for some of our users on Chrome and Firefox.
We are getting this 404 error when some of our users browse to our home page and they get redirected to the login page (our B2C tenant and custom login URL is redacted but all other query parameters are unchanged):
https://login.microsoftonline.com/redacted.onmicrosoft.com/B2C_1_sign_up_in/api/CombinedSigninAndSignup/error?code=UX004&diags=%7B%22version%22%3A%222.0.0%22%2C%22user-agent%22%3A%22Mozilla%2F5.0%20(Windows%20NT%2010.0%3B%20Win64%3B%20x64%3B%20rv%3A54.0)%20Gecko%2F20100101%20Firefox%2F54.0%22%2C%22online%22%3Atrue%2C%22trace%22%3A%5B%22%231%20T005%20(3ms)%22%2C%22%232%20T027%22%2C%22%233%20T021%20(37ms)%22%5D%2C%22code%22%3A%22UX004%22%7D&csrf_token=YzQ0N3F3NXlTVzBVWTFraG96cmlVU3FVbjVNRmZRbHZ6RURIaHdPRExNRTlDRVRNL3hPN00xRXhoOUV0bnE0V3pYc3ZYcEg0YzRhVnp5WE5QYTJZN0E9PTsyMDE3LTA4LTA4VDAwOjU3OjM2Ljc3MjM1MDlaO283Mm9nSFVXb3lIbWtVZy9CeHZVbFE9PTt7Ik9yY2hlc3RyYXRpb25TdGVwIjoxfQ==&tx=eyJUSUQiOiI4MDgwNWE3Ny02OTU2LTRiNGMtYmUyYi05OGZkZGEwYzM4MDkifQ&desc=https%3A%2F%2Fourdomain.redacted.html
We have tested the following with no success:
Clearing all our cache and cooking
Disabled all extensions
Private browsing/Incognito mode
Chrome on Android
But Internet Explorer loads the custom sign-in page just fine on their computer!
I have tried searching online for error code UX004 but didn't find anything. Can someone from Microsoft advise what this error code means? Thank you.
I didn't get any response from Microsoft, but we tried various fixes. The one that worked for us is to apply a SSL certificate issued by a commonly-trusted issuer on our test domain. I can't confirm that this error message means AAD B2C is complaining of an insecure connection, but it's worth exploring in case it works for anyone else too.
It appears as though this may be a CORS issue on your hosted login page. Use (F12) to open up your developer tools, look into the Console tab and ensure you have Preserve log switched on. Navigate to the website and hopefully the error should be visible.
For me it was a CORS issue with the storage account. Adding a CORS rule that allowed everything solved the problem.
Go to azure portal (https://portal.azure.com) and open the storage account that contains your custom login page templates. In the right hand navigation find Settings > Resource sharing (CORS)
Add a new rule with the following values
Allowed origins = *
Allowed methods = Select all items
Allowed headers = *
Exposed headers = *
Max age = 200
Hopefully that helps!
I haven't paid the "one-time developer registration fee" and I have uploaded my extension. In my developer dashboard it says.
"The fee is not required to publish only to users in mydomain.com"
How can I publish to users only in mydomain.com without paying the "one-time developer registration fee". I can't find that option anywhere.
To be able to publish to only people in your domain, you must have this permission enabled by the Google Apps for Work administrator for your organization.
From Google: "Administrators can choose which users they want to be able to publish private apps for their organization by clicking this checkbox in the Admin console under Device management > Chrome management > User settings > Chrome Web Store Permissions."
Once this permission has been enabled, you can upload the ZIP file, for your extension, fill out the form, and at the end, select Private (Everyone at yourdomain.com) under Visibility options. This will allow you to publish without paying the fee.
See their documentation here: https://support.google.com/chrome/a/answer/2663860?hl=en
Based on: http://developer.chrome.com/extensions/hosting.html
Once you package your extension (Go to and click the developer mode checkbox. Now you should see the packaging button), you upload it to your server. Now you will need to use the appropriate HTTP headers to get Chrome to recognize your extension (A .crx on your server) as an installable. Chrome considers a file to be installable if:
The file has the content type application/x-chrome-extension
The file suffix is .crx and both of the following are true:
The file is not served with the HTTP header X-Content-Type-Options: nosniff
The file is served with one of the following content types:
empty string
"text/plain"
"application/octet-stream"
"unknown/unknown"
"application/unknown"
"*/*"
Am trying to publish my extension to trusted testers. (as described here: https://developers.google.com/chrome/web-store/docs/publish#testaccounts)
In publishing page, i left the trusted testers dropdown empty and clicked "Publish to trusted testers". Now as described in help center, i added one email ID as trusted tester.
Everything works fine, the user able to access the extension in webstore via direct url.
But the problem is, now I removed the user email id from my trusted tester list, but that User is still be able to access the extension. Tried sign-out sign-in but the user still able to access the extension using the URL.
How do I stop that user accessing my extension?
You should try to unpublish your extension. Then "Publish to trusted testers" again with different email ID.