Botframework-composer: WeatherBot : After deployment, shows "Invalid URI: The hostname could not be parsed"

[deenaMaistering]

After deploying the weather bot as a web app, it is not recognizing the intents (which is using LUIS recognizer) and shows "Invalid URI: The hostname could not be parsed". The same works fine when I try it in the composer before deployment.

[luhan2017]

@deenaMaistering ， did you use our deployment script to deploy? there is a logic to generate the hostname in the deployment script, it will be missed if we don't use the script to deploy.

[hibrenda]

https://github.com/microsoft/BotFramework-Composer/issues/2001 @deenaMaistering should I close this one ?

[ismendes]

I'm using the composer but I'm not using it to deploy in our environment. What should I change in my deploy script to fix this error?

[jst84]

Hi @ismendes! the problem is the bot's appsettings.json. In particular, the LUIS url that the bot have to call is missing. Publish process via cli change this appsettings.
If you want to do the manual process, you have to set this keys. Here an example of working appsettings:
{ "bot": "ComposerDialogs", "cosmosDb": { "authKey": "", "collectionId": "", "cosmosDBEndpoint": "", "databaseId": "" }, "applicationInsights": { "InstrumentationKey": "" }, "blobStorage": { "connectionString": "", "container": "" }, "qna": { "knowledgebaseid": "", "endpointkey": "", "hostname": "" }, "MicrosoftAppId": "", "MicrosoftAppPassword": "", "luis": { "endpoint": "", //luisurl "endpointKey": "", //luiskey "Main_en-us_lu": "" //luisappid } }
If you want to try, you can publish bot by follow the instruction and then see the appsettings.json.
NB. the deployment process set MicrosoftAppId & MicrosoftAppPassword in the azure appservice settings.

[RussHelfand]

Hi @js84, I work with @ismedes. Thank you for your answer (above). It solved a problem that we've been struggling with for several days. We now have a system where we can edit with Composer, then have Visual Studio notice the changes to the files so we can check them into our private Git repository (via ADO), and the publish them via Azure pipelines' continuous deployment. Works like a charm... now that we have the 3 new settings that you pointed out (above) for our luis configuration! Again, thanks.