I run and install Luis Container in my server according tutorial https://learn.microsoft.com/en-us/azure/cognitive-services/luis/luis-container-howto?tabs=v3
I run the container, it works fine. Api is also working fine. After several mins, when I check the status(http://192.168.10.140:5000/status),I got "Api Key is invalid.", then I restart the container, everything is ok. But after several mins, "Api key is invalid" occur again.
{"service":"luis","apiStatus":"Invalid","apiStatusMessage":"Api Key is invalid."}
When error occur, Luis container is running all the time.
By the way, the price tier for the Cognitive Services is SO(standard).
Could anyone give some suggestions why I got this error?
The LUIS Docker container reaches out to the billing endpoint every 10-15 minutes. I would imagine that this is why everything appears to work fine initially.
Ensure you're using the correct API Key
Go you the LUIS portal
Click your LUIS app
Click Manage
Click "Azure Resources" and copy your Primary key
Ensure you haven't hit any limits
Test your API Key in the online API tester
I'd imagine this will help you discover the real issue. If not, let me know and I will continue to help troubleshoot and update this answer.
Related
I have tried several time to open a Github account but it didn't accept me & continously showen me this type of something. (Unable to verify your captcha response. Please visit https://docs.github.com/articles/troubleshooting-connectivity-problems/#troubleshooting-the-captcha for troubleshooting information.)
someone can help me please to solve this?
Since Bangladesh is listed in the countries where SMS authentication is supported, I don't suppose your issues are linked to sanctioned countries GitHub would refuse to deal with.
Try first from another computer and network, to see if the issue persists.
I had this problem yesterday, you must use vpn or proxy connection first (in some countries like Iran and Middle East countries) and then you can create a Github account, connect to a vpn - proxy like " hoxx vpn proxy Extension in your browser" or use psiphon before creating an account.
My company has 2 Google Maps API keys that we have been using for several years. They started charging us for their use in June 2018. At that point and for several month afterwards, I could go to the Google Cloud Platform console and see the API keys listed, along with usage etc. Now when I go to the GCP console, it does not show those API keys. However, Google is still charging our credit card every month for their use.
I'm wondering what happened, and if it has happened to anyone else. If I could see the API keys, I could edit them, change their restrictions, etc.
If you're confident that you're checking the correct project, you may wish to review your audit logs to see whether the API Key was deleted by one of the project's authenticated accounts:
For ${PROJECT}, the following should list API key-related actions:
PROJECT=[[YOUR-PROJECT]]
LOGNAME="projects/${PROJECT}/logs/cloudaudit.googleapis.com%2Factivity"
METHOD="google.api.apikeys.v1.ApiKeys"
gcloud logging read "logName=\"${LOGNAME}\" protoPayload.methodName:\"${METHOD}\"" \
--project=${PROJECT} \
--format="value(protoPayload.authenticationInfo.principalEmail,protoPayload.methodName,timestamp)"
I created then deleted an API key to confirm the behavior.
My logs show (abbreviated):
[me] google.api.apikeys.v1.ApiKeys.DeleteApiKeys 2020-04-07T19:21:40.301Z
[me] google.api.apikeys.v1.ApiKeys.PatchApiKey 2020-04-07T19:18:38.395Z
[me] google.api.apikeys.v1.ApiKeys.CreateApiKey 2020-04-07T19:18:20.721Z
I've been trying to use Zoopla's property search API a few days now. First day I used the API, it was straight forward. I registered for a new key, and could do requests via the documentation. Starting yesterday, all the requests I would do would always return a 403 response with the body <h1>Developer Inactive</h1>.
I tried creating a new API key but the problem is still the same. Is anyone using the API that can share some knowledge about it? Seems to be deprecated, but I cannot understand how I was getting results from it without issues for a single day.
https://developer.zoopla.co.uk/docs/Property_listings
Ive just hit the exact same issue, trying to create an app using the API, worked great on the first day, but since coming back to my project today it no longer works!
It appears the API is dead and no longer maintained - https://medium.com/#mariomenti/how-not-to-run-an-api-looking-at-you-zoopla-bda247e27d15
Very frustrating.
The API is in the process of getting shut down and moved to a new solution.
When signing up to the API, it does not tell you this, which is strange.
When you sign up, the API key will die after 24 hours. However, if you email help#zoopla.co.uk with your email address and API key, they will reinstate the API access.
Please can you help me, I'm receiving this error when I'm trying to deploy a google cloud function:
HTTP Error: 400, Default service account 'project-name#appspot.gserviceaccount.com' doesn't exist. Please recreate this account (for example by disabling and enabling the Cloud Functions API), or specify a different account.
The command used to deploy is:
firebase deploy --only functions
A temporary solution is fine, but if you can help me to solve it permanently is better.
Thanks in advance.
In my case, the App Engine default service account was deleted. It looks like this: {project_id}#appspot.gserviceaccount.com
So I had to restore the service account like this:
You can now recover the deleted service accounts from https://cloud.google.com/iam/reference/rest/v1/projects.serviceAccounts/undelete
you have to get the UniqueID of the service account from https://console.cloud.google.com/home/activity
Source: https://stackoverflow.com/a/55277567/888881
The API explorer is an easy way to use the IAM API: https://developers.google.com/apis-explorer/#p/
I was struggling to resolve this issue, then I raised a case with Google.
here is a detailed article of my learnings :
https://medium.com/#ashirazee/http-error-400-default-service-account-appspot-gserviceaccount-com-accd178ea32a
Firstly navigate to Google Cloud Platform and view your service accounts.
try and find <project_id>#appspot.gserviceaccount.com' in your list of service accounts for the firebase project, it is linked to the App Engine.
if '#appspot.gserviceaccount.com' is missing you can not deploy anything(SEE EMAIL WITH GOOGLE BELOW), if it isn't, check and see if it's enabled, try disabling it and enabling it again.
#appspot.gserviceaccount.com is pre-installed by default, regardless of a paid account or not. try and recall if at any time you may have deleted it after or before deployment.
Now if you have for any reason deleted it over a period of more than 30 days than you can not retrieve it, and you must create a new firebase project. However, if it is within 30 days you can undelete it.
EMAIL FROM GOOGLE:
Email #1
"
Hello Ali
I am checking the logs of your project, unfortunately the service account was deleted on Ma, there is no chance to recover it nor recreate it
The only workaround available is to create a new project and deploy the service desired there. I know this could not be the best option for you nevertheless it is the way this works by design.
Do not hesitate to write back if you have more questions.
Cheers,"
Email #2,
"Hello Ali
I am glad to read that you have been able to deploy your functions successfully, unfortunately that service account cannot be recovered after 30 days of being deleted and that is the only solution. If you have other questions, please let us know by contacting us again through our support channel.
Cheers,"
lastly here is a helpful command line that will help you debug this, however, it won't help if there is no service account, it'll just highlight the obvious:
firebase deploy --only functions --debug
this was my error:
"HTTP Error: 400, Default service account '<project_id>#appspot.gserviceaccount.com' doesn't exist. Please recreate this account (for example by disabling and enabling the Clo
ud Functions API), or specify a different account."
Following the error message, you could enable the API by console accessing this url and enable the api.
Or by gcloud command:
gcloud services --project <project_id> enable cloudfunctions.googleapis.com
As the other stated, sadly, you need to use the default service account.
If within the 30 days period, you can use this tutorial to find and undelete the service acc: Read this guide to get https://cloud.google.com/iam/docs/creating-managing-service-accounts#undeleting_a_service_account
You have to enter the commands through the Google Cloud Console (one of the buttons will open a terminal on the right of the top blue app bar)
try to select Google Cloud Platform (GCP) resource location in Setting of Firebase. enter image description here
I've been working with website that uses geocode lookups via Google. I've been testing this for awhile now.
https://maps.googleapis.com/maps/api/geocode/json?address=1600+Pennsylvania+Ave+NW,+Washington,+DC&key=XXXXXXXXXXXXXXXXXXXXXXXXXXX
I've got that key locked to particular servers. All of a sudden I'm seeing geocode lookup errors. The response back from Google is:
{
error_message: "Browser API keys cannot have referer restrictions when used with this API.",
results: [ ],
status: "REQUEST_DENIED"
}
When I try a simple request without the API key at all it seems to work fine. Here you can try this yourself. Copy and paste the next line in your browser's URL and return.
https://maps.googleapis.com/maps/api/geocode/json?address=1600+Pennsylvania+Ave+NW,+Washington,+DC
Now, I probably shouldn't look a gift horse in the mouth, but the whole thing seems odd. If I remove my API keys today, will my websites, that rely on an address to Lat/Lng conversion, all fail tomorrow?
Is anybody else experiencing odd failures with Google Maps and GeoCode lookups? Is anyone aware of a systemic content or policy change from the Google mapping / GeoCoding team??
Edit, update:
So this defect lasted about 40 minutes, from around 9:10PM PST until a bit before 10PM PST. It seems to be fixed now.
Response to comment: Hmmm. I've been looking at the API keys as:
Server keys: Create and use a Server key if your application runs on a
server. Do not use this key outside of your server code. For example,
do not embed it in a web page. To prevent quota theft, restrict your
key so that requests are only allowed from your servers' source IP
addresses.
Browser keys: Create and use a Browser key if your application runs on
a client, such as a web browser. To prevent your key from being used
on unauthorized sites, only allow referrals from domains you
administer.
I'm definitely doing this complete lookup from user directly to Google without a server in the middle. No way can I safely use a Server key there. So I've read your input, and it definitely says Server key for geocoding. But, that really implies that no one should ever allow a browser / client interaction to process a geocode lookup. Frankly I just assumed the writeup was out of date and a bit inaccurate.
While you may be right, the whole thing just looks odd. I would have thought that if Geocode required a lookup from a server (only) and never from a web application via the browser (ever) that there would have been some direct comment as to that effect.
Oh, and the browser keys, with server fencing, seem to be working again. Again, I'm just saying the whole thing is odd. I'm treating this as a temporary hiccup up at the Google geocode servers.
And yes, I can certainly introduce an API server for a round trip Ajax call to do the lookup safely with a server key, but what's the point? Is there a benefit that I'm just not seeing? I guess I could add elements like a nonce to protect my round trip geocode intermediate lookup server from somebody else using it, etc.... But at this point, I'm just confused.
Update #2: 16 Jun 2016
Again, this whole thing is not clear. I filed a feature request to the Google GeoCode team asking for a clarification update to the documentation to address the use of Browser API keys for geocode lookups.
The documentation for the Geocoding Web Service states:
Standard API users: If you're using the API under the standard plan, you must use a server key (a type of API key) set up in a project of your choice.
The error message indicates you are using a browser key.