Google Cloud DNS failed to load - dns

I am developing new website using google cloud, but cloud DNS failed to load. Don't know what's wrong with that. Any solutions?

Go to APIs & services -> Library
Type DNS
Click on "Google Cloud DNS API"
Click on "Enable"

I had the exact same problem this afternoon. I was using Safari on a Mac, so I thought I'd try another browser. Sure enough, Chrome loads the page just fine.
Maybe try a different browser? (I had success with a with Chrome in an Incognito window)

you can only 'enable dns' on one project at a time. you will probably have another project dns enabled. disable it, then enable the dns on the project you want to work on.

Yes just enable the API and give the Cloud DNS a couple minutes to load up

Related

Enable DNS over HTTPS (DoH) when visiting a specific domain

I am totally new with this new protocol that is already available in latest Firefox browser but I can not manage it to work on Chrome browser at least in a Windows PC. Now I totally had no idea where to put this question in SO so please understand.
Can I enable DoH feature automatically on Firefox or Chrome in Windows by just visiting a site?
If can not, then can I create a batch script or desktop app instead that will patch/enable DoH to the said browsers?
You can enable DNS over HTTPS (DoH) for Google Chrome like this:
1) Type this into address(URL) bar of Google Chrome: chrome://flags/#dns-over-https
2) You will see "Secure DNS lookups" in the opened tab: Click and change from the select box: Enabled/Disabled or Default
3) Done

Azure data factory not loading

I am not able to open Azure data factory in any browser, it just keep loading from past 1 hour. I have tried refreshing and using other browser, is there any specific reason why it happens? All other services on azure portal is working fine.
Browsers which I have tried:
Mozilla Firefox 65.0.2
Internet explorer 9
Microsoft Edge 42
Opera Latest
For all of the above browsers all services are fine but when I click on "Author & Monitor", it opens up a new tab and keep loading.
I often experience this issue but not always.The azure data factory UI keep loading or keep asking me to re-enter my account information. I fixed it by using incognito mode in the browser.
You could find many clues from this MSDN case. Also,try Chrome browser according to this case:Azure Data Factory v2 portal is slow
In order to access ADF portal you should use Google Chrome as at this moment other browsers does not support this portal.
See the response for similar issue: https://social.msdn.microsoft.com/Forums/en-US/26dd2244-efa2-4225-a32f-2f68d3a60139/data-factory-ui-is-not-loading .
Thank you that worked - using firefox vs IE solved it. I don't wish to use Chrome.
I had this problem today too, I fixed it just by logging out from another account that I had log in moments before
This is the official solution: https://learn.microsoft.com/en-us/azure/data-factory/data-factory-ux-troubleshoot-guide?tabs=edge#azure-data-factory-studio-fails-to-load
Pay attention to the third party cookie settings.
ADF officially supports both Chrome and Edge. So you don't have to use Chrome. Firefox actually also works.

Chrome Extension -- externally_connectable and any way to set "matches" entries upon install

We have created a Chrome Extension that is a companion to web sites that we host for our customers. These web sites are hosted under our domain name and interact with the extension using external messaging and relying on the sites being configured in the manifest similar to the following (abcdefg.com is a ficticious domain name):
"externally_connectable": {
"matches": [ "http://*.abcdefg.com/*", "https://*.abcdefg.com/*"]
}
This works great in these cases. However, we have a subset of customers that prefer to host the website themselves under their own domain. The problem is that we do not want to update the extension manifest for the published extension to include all of these sites.
Is there any option of distributing a version of the extension (on Windows) where the "externally_connectable" site list can be set upon installation?
Thanks to kzahel for highlighting the obstacles I was facing and thanks to wOxxOm for providing a solution that will work.
Rather than trying to find a way to override the "externally_connectable" matches configuration upon installation, we found the easiest alternative was to avoid external messaging and use messaging via a content script instead.
The following is a copy of the solution posted above by wOxxOm:
chrome extension - alternative to externally_connectable?
Unfortunately there's no way to do this. You'll need to create a custom extension for every customer with their own domain name. Luckily, there is an API for updating the extension, so you would be able to at least update multiple extensions without too much difficulty. However, the 20 extension limit per account would be a little annoying. I think you can get more extension allowed per account by creating a publishing group and assigning the extensions there.
You could if you are willing to have customers install this in developer mode. That would bypass the 20-extension limit.

Enabling Adsense Management API [duplicate]

I am trying to enable the adsense management api from the google developers console. I have created a project and under APIs and auth I go to APIs and try to turn on AdSense Management API, but when I click it it just shows a toast notification saying "Error Enabling Adsense Management API". I really need this to work. So help is appreciated.
Thanks,
Sai
I had the same problem. I disabled my AdBlocker. Then it worked just fine!
Have you tried using a different browser or going back to the old version of the console? I had a similar issue because the browser blocked the Terms of Service agreement page.
I had the same problem. Disable AdBlock plugin and it will work!
Open a new incognito window and open the console url "https://console.developers.google.com/" there. After that, activate the AdSense Management API.

File upload/download problems using Internet Explorer to a Sharepoint site

A cheeseburger to the first person who can help me make sense of this. I have a page in a Sharepoint app that uses Telerik's RadUpload to upload files. This has worked for months; last week it stopped working (in Internet Explorer, this detail is important). After talking with a co-worker about the problem, I tried the upload with Firefox; it worked. Not only that, all subsequent uploads from Internet Explorer started working. Flash forward an hour, and the aforementioned coworker, on another Sharepoint site, running on different servers, was having problems downloading (using Internet Explorer). Being half serious, half smart-aleck, I said 'try it in Firefox'. Not only did that work, ALL SUBSEQUENT DOWNLOADS IN INTERNET EXPLORER WORKED! And he re-produced this behavior on another machine. My fear is that this a browser issue. All advice will be greatly appreciated.
a
IE will try and present credentials to a server it knows to be in its Local Intranet zone when it tries to connect (depending on the setting of "Automatic logon only in Intranet zone").
Firefox will only present credentials when prompted, and will generally ask you by popping up a box (unless you've configured a list of sites for it to always present NTLM credentials to).
I've seen a similar case with Sharepoint where you can cause IE to work by logging in with Firefox. I theorized it was due to a permission on a remote resource being for "Authenticated Users", and you're causing your user to authenticate by logging in forcefully. We eventually set the "Automatic logon only in Intranet zone" to "Prompt" and it worked. My theory there was that it wasn't detecting the site as being in the Local Intranet zone for some reason. If you're not accessing a domain with no .'s in it, try also setting your Local Intranet site policy to match the full domain of the Sharepoint server, not just *.example.com - I've read that that can help.
Was it as simple as IE not re-downloading miss-cached .js file, maybe, that firefox did download, making IE work after that?
Pretty gnarly to debug.

Resources