bot framework embedded chat 403 error - node.js

I am using the embedded chat control to hook up to my Microsoft Bot Framework bot and I keep getting these errors:
(I'm using Node.js on AWS Elastic Beanstalk. None of these errors happen when I run the code locally)
jquery.min.js:11 POST https://webchat.botframework.com/api/conversations/null/messages 403 (Forbidden)
The bot doesn't respond and a few minutes later it shows this:
jquery.min.js:11 GET https://webchat.botframework.com/api/conversations/Bv3bkhOgxas/messages?watermark=131101401454109138 403 (Forbidden)
which is sometimes accompanied by a 500 (Internal Server Error)
I assume the null in the first message is a clue. Does anyone know what is going on or how I can fix it?
Thanks.

Hard to tell what you are doing w/o additional detail. But it's likely your header either doesn't contain an auth token or the incorrect one.

Related

JMeter - API test Plan - Service unavailable. Please try again later error

I created an API test plan in JMeter.
(Post) Login Authentication API
(Get) API to search for data (Authenticated with the help of correlation)
The Login API works fine I am able to see the response. But, the Search API is returning an error "Service unavailable. Please try again later." with error code 500. My API request has got all the data required Can someone help me to fix the issue.
Thanks,
As per 500 Internal Server Error description:
The HyperText Transfer Protocol (HTTP) 500 Internal Server Error server error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
This error response is a generic "catch-all" response. Usually, this indicates the server cannot find a better 5xx error code to response. Sometimes, server administrators log error responses like the 500 status code with more details about the request to prevent the error from happening again in the future.
So my expectation is that you should rather check your server logs to figure out the root cause of the problem rather than looking for a solution from JMeter side.
In general if something is wrong with your request the server should respond with 4xx status code
If you have another way of sending the "search" request you can inspect it and cross check all the associated data including:
URL
Headers (can be passed via HTTP Header Manager), pay attention to Content-Type one
Request body
The value you correlated which can be checked using Debug Sampler and View Results Tree listener combination

Azure - The request could not be completed. (Internal Server Error)

I'm using Xamarin.Forms with azure and everything been working fine, but today I started getting this weird error - "The request could not be completed. (Internal Server Error)", the only thing that I know of that I've changed lately is the sql server password. So I'm wondering if that could be the issue of if it could be something else and how to fix it. The diagnostics tool is also showing http server errors whenever a request is attempted.
Ok, so I figured it out, sure enough it was the change in my sql server password, to fix it I simply changed it back to what it originally was.

Why does Auth0 fails with error unknown client?

I have a React project using express/node.js on the backend. Tested the project thoroughly before deploying, fully functional with no problems. After hosting and configuration, the site is accessible online but any login attempt generates a 400 error stating the request is coming from an unknown client?
I can share any code snippets needed but I'm thinking something is wrong in my Auth0 configuration. I've checked and triple-checked the clientID and key in my code, as well as my web origin urls and allowed callback URLs.
Can't find any reference to this error code here on stack or on google. Auth0 support has no mention.
Has anyone had this problem?

Gmail API keeps returning error 500 Backend Error for a particular email address

For a while it's been working fine. Now today, all of a sudden, when I try to list messages for a particular email address the API call just hangs for a while and then returns Backend Error (500). It still works sometimes, and sometimes it's just really slow at responding, but for the most part it seems to hang.
Any ideas what the problem could be, or how to diagnose it. I'm using the node, googleapis package, oauth2 tokens, server-side calls.
PS: I've checked the logs and there aren't any 4xx errors.

Spotify Web API won't work for a specific user?

I'm trying to use the web api to query a user's playlists (using the spotipy Python library). I got the user to oAuth in, got an access token, made the request and got a 500 error:
SpotifyException: http status: 500, code:-1 - https://api.spotify.com/v1/users/125139403/playlists?limit=50&offset=0: Server error.
I then tried the same request in Web API test console and it worked fine.
But then things get kind of weird. I tried running the cURL command the console generated in a terminal and got the same 500 error.
Then I tried running the same request using cURL but just changing the username in the URL and it worked fine (at least for public playlists) for both my username and a random friend's user ID number.
I thought maybe I'm having a token issue but the token I'm using seems to work fine with other usernames. It's just the one specific user for whom I'm getting the error.
I'd rather not post the user's ID on this public forum but I can email it to someone if it's relevant.
My best guess for what's wrong at this point is a bug on Spotify's side but I certainly could be doing something wrong.
Again, thanks for reporting this. This bug was fixed by Matt M. and was just deployed to production.
Please try it out in our API Console. (which Matt was also part of building!)

Resources