microsoft / microsoft/BotFramework-WebChat

500 internal Error, the server Azure

Open
#5,412 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bot Services bug customer-reported
Dominant language
HTML
Stars
1.8k
Forks
1.6k
Avg merge
22h 58m
Merged PRs (30d)
2

Description

Is it an issue related to Adaptive Cards?

No response

What is the PWD impact?

HI
the endpoint https://hawo-mockbot4-token-app.blueriver-ce85e8f0.westus.azurecontainerapps.io/api/token/directline reply always with error 500 (Internal Server Error).

I copy the workspace in public folder ROOT of Apache tomcat and running this example..
I launched Chrome without CORS and I go on the url http://localhost:8080/BotFramework-WebChat-main/samples/04.api/a.welcome-event/

Image

Please you can fix the server Azure so I can try your example.

What browsers and screen readers do this issue affect?

Windows: Chrome/Firefox with JAWS

Are there any code-based customization done to Web Chat?

No, I am using Web Chat without any customizations except "styleOptions".

What version of Web Chat are you using?

Latest production

Which area does this issue affect?

Others or unrelated

What is the public URL for the website?

https://hawo-mockbot4-token-app.blueriver-ce85e8f0.westus.azurecontainerapps.io

How to reproduce the issue?

I running the file index.html deployed in my tomcat.
the path is BotFramework-WebChat-main/samples/04.api/a.welcome-event/

What do you expect?

Maybe disable CORS on Azure and fix your error 500 internal error

What actually happened?

I can't try example and get 500 eorr and wmpty chat.

Do you have any screenshots or recordings to repro the issue?

No response

Did you find any DOM elements that might have caused the issue?

No response

MAS reference

No response

WCAG reference

No response

WAI-ARIA reference

No response

Adaptive Card JSON

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the request to the Azure endpoint /api/token/directline while loading samples/04.api/a.welcome-event/index.html from the Tomcat deployment. Inspect the endpoint response and Azure-side configuration or logs, including the reported CORS behavior. Done means the endpoint no longer returns 500 and the sample displays a chat.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, html
Domain
api, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.