microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

[local] HueBot setup

Open
#241 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Hello Team,

I was previously working on and had successfully set up the audio video bot using cloud service.

I am trying to locally set up the HueBot now using service fabric.

I am facing the following error
“The application URL is not set or is not an HTTP/HTTPS URL so the browser will not be opened to the application”
and Failed to match service domain name '0.tcp.ngrok.io' against certificate with subject name CN=.com,

I feel my configuration i snot done properly.
I have made changes to my ngrok.yml as per the sample and started an ngrok session.

I had an azure app service standard cert from the audio bot instance and I have mapped the cname's

  1. www (indicating www..com) to 0.tcp.ngrok.io
  2. 0 (indicating 0..com) to 0.tcp.ngrok.io (I am assuming this is how it works)

while configuring my service fabric project I chose:
** -dns 383a8dee.ngrok.io -cn www.<bot - domain>.com **

I have also updated references :
** "BotMediaProcessorUrl": "net.tcp://0.tcp.ngrok.io:10828",
"BotBaseUrl": "https://www.:9444/api/calls"**

In cloud.xml
** <ClusterConnectionParameters ConnectionEndpoint="8470ed15.ngrok.io:19000"**

I am confused of where all the ngrok(tcp , http and https) endpoints go.
Kindly also help me with the url for the calling endpoint in azure bot channel registration.

Regards,
Aarushi

Contributor guide

No contributing guide indexed for this repository

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 reviewing ngrok.yml, cloud.xml, and the BotMediaProcessorUrl, BotBaseUrl, and ConnectionEndpoint values against the local Service Fabric and Azure Bot Channel setup described. Trace which TCP, HTTP, and HTTPS endpoints are required; done means a consistent configuration that launches without the reported certificate and application-URL errors.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.