azure chatbot not working. after publishing from visual studio(2017)
i done the following steps:
created web app bot (bot framework sdk v4) and perform 'test web chat'. which is successful and the bot responded.
note: Microsoft app id and password are created.Downloaded the code.
updated bot file(.bot) with luis and qna configuration manually
#{
"appId": "XXXXXXX",
"authoringKey": "xxxxxxxxxx",
"version": "0.1",
"region": "xxxxx",
"type": "luis",
"name": "BasicBotLuisApplication",
"id": "6"
#}
#{
"appId": "XXXXXXX",
"authoringKey": "xxxxxxxxxx",
"version": "0.1",
"region": "xxxxx",
"type": "qna",
"name": "myqna"
#}
and put 'Padlock' with empty value
Also updated the code (Startup.cs,BotServices.cs) and build app locally.
- For testing locally,used bot framework emulator and which was successful.
- Then 'Publish' the application with visual studio.
- Try to connect with 'Test webchat'. The operation failed and received error code(401 and 403).
what shall do? any solutions?
c#
azure azure-web-sites 
botframework edited Nov 14 '18 at 20:06
Manfred Radlwimmer
10.5k123550
asked Nov 14 '18 at 16:06
sumithsumith
84
add a comment |
i done the following steps:
created web app bot (bot framework sdk v4) and perform 'test web chat'. which is successful and the bot responded.
note: Microsoft app id and password are created.Downloaded the code.
updated bot file(.bot) with luis and qna configuration manually
#{
"appId": "XXXXXXX",
"authoringKey": "xxxxxxxxxx",
"version": "0.1",
"region": "xxxxx",
"type": "luis",
"name": "BasicBotLuisApplication",
"id": "6"
#}
#{
"appId": "XXXXXXX",
"authoringKey": "xxxxxxxxxx",
"version": "0.1",
"region": "xxxxx",
"type": "qna",
"name": "myqna"
#}
and put 'Padlock' with empty value
Also updated the code (Startup.cs,BotServices.cs) and build app locally.
- For testing locally,used bot framework emulator and which was successful.
- Then 'Publish' the application with visual studio.
- Try to connect with 'Test webchat'. The operation failed and received error code(401 and 403).
what shall do? any solutions?
c#
azure azure-web-sites botframework edited Nov 14 '18 at 20:06
Manfred Radlwimmer
10.5k123550
asked Nov 14 '18 at 16:06
sumithsumith
84
Do you have other pages in your bot that work? For example, do you have the default.htm page that comes by default underneath wwwroot folder? (Browse to https://<your bot application>.azurewebsites.net/ to test). Does browsing to the endpoint (https://<your bot application>.azurewebsites.net/api/messages) give you the typical HTTP 405, or does it also give a 401/403?
– Dana V
Nov 19 '18 at 20:04
add a comment |
i done the following steps:
created web app bot (bot framework sdk v4) and perform 'test web chat'. which is successful and the bot responded.
note: Microsoft app id and password are created.Downloaded the code.
updated bot file(.bot) with luis and qna configuration manually
#{
"appId": "XXXXXXX",
"authoringKey": "xxxxxxxxxx",
"version": "0.1",
"region": "xxxxx",
"type": "luis",
"name": "BasicBotLuisApplication",
"id": "6"
#}
#{
"appId": "XXXXXXX",
"authoringKey": "xxxxxxxxxx",
"version": "0.1",
"region": "xxxxx",
"type": "qna",
"name": "myqna"
#}
and put 'Padlock' with empty value
Also updated the code (Startup.cs,BotServices.cs) and build app locally.
- For testing locally,used bot framework emulator and which was successful.
- Then 'Publish' the application with visual studio.
- Try to connect with 'Test webchat'. The operation failed and received error code(401 and 403).
what shall do? any solutions?
c#
azure azure-web-sites botframework edited Nov 14 '18 at 20:06
Manfred Radlwimmer
10.5k123550
asked Nov 14 '18 at 16:06
sumithsumith
84
i done the following steps:
created web app bot (bot framework sdk v4) and perform 'test web chat'. which is successful and the bot responded.
note: Microsoft app id and password are created.Downloaded the code.
updated bot file(.bot) with luis and qna configuration manually
#{
"appId": "XXXXXXX",
"authoringKey": "xxxxxxxxxx",
"version": "0.1",
"region": "xxxxx",
"type": "luis",
"name": "BasicBotLuisApplication",
"id": "6"
#}
#{
"appId": "XXXXXXX",
"authoringKey": "xxxxxxxxxx",
"version": "0.1",
"region": "xxxxx",
"type": "qna",
"name": "myqna"
#}
and put 'Padlock' with empty value
Also updated the code (Startup.cs,BotServices.cs) and build app locally.
- For testing locally,used bot framework emulator and which was successful.
- Then 'Publish' the application with visual studio.
- Try to connect with 'Test webchat'. The operation failed and received error code(401 and 403).
what shall do? any solutions?
c#
azure azure-web-sites botframework c#
azure azure-web-sites botframework edited Nov 14 '18 at 20:06
Manfred Radlwimmer
10.5k123550
asked Nov 14 '18 at 16:06
sumithsumith
84
edited Nov 14 '18 at 20:06
Manfred Radlwimmer
10.5k123550
asked Nov 14 '18 at 16:06
sumithsumith
84
edited Nov 14 '18 at 20:06
Manfred Radlwimmer
10.5k123550
edited Nov 14 '18 at 20:06
Manfred Radlwimmer
10.5k123550
edited Nov 14 '18 at 20:06
Manfred Radlwimmer
10.5k123550
10.5k123550
asked Nov 14 '18 at 16:06
sumithsumith
84
asked Nov 14 '18 at 16:06
sumithsumith
84
asked Nov 14 '18 at 16:06
sumithsumith
84
84
Do you have other pages in your bot that work? For example, do you have the default.htm page that comes by default underneath wwwroot folder? (Browse to https://<your bot application>.azurewebsites.net/ to test). Does browsing to the endpoint (https://<your bot application>.azurewebsites.net/api/messages) give you the typical HTTP 405, or does it also give a 401/403?
– Dana V
Nov 19 '18 at 20:04
add a comment |
Do you have other pages in your bot that work? For example, do you have the default.htm page that comes by default underneath wwwroot folder? (Browse to https://<your bot application>.azurewebsites.net/ to test). Does browsing to the endpoint (https://<your bot application>.azurewebsites.net/api/messages) give you the typical HTTP 405, or does it also give a 401/403?
– Dana V
Nov 19 '18 at 20:04
Do you have other pages in your bot that work? For example, do you have the default.htm page that comes by default underneath wwwroot folder? (Browse to https://<your bot application>.azurewebsites.net/ to test). Does browsing to the endpoint (https://<your bot application>.azurewebsites.net/api/messages) give you the typical HTTP 405, or does it also give a 401/403?
– Dana V
Nov 19 '18 at 20:04
Do you have other pages in your bot that work? For example, do you have the default.htm page that comes by default underneath wwwroot folder? (Browse to https://<your bot application>.azurewebsites.net/ to test). Does browsing to the endpoint (https://<your bot application>.azurewebsites.net/api/messages) give you the typical HTTP 405, or does it also give a 401/403?
– Dana V
Nov 19 '18 at 20:04
add a comment |
2 Answers
2
active
oldest
votes
401 is unauthorized so did you make sure your file containing your authorization key got published?
If the file is not part of your solution/project it will not get deployed. Make sure that file is available post deployment on your app service (I presume?), you can use Kudu by going to [AppServiceName].scm.azurewebsites.net
Use the Debug Console to verify the file.
answered Nov 14 '18 at 20:04
Simon BourdeauSimon Bourdeau
19114
add a comment |
You need to look at your authentication. Usually, there should be some sort of session ID token that your browser session caches after authentication. From what you told us, there doesn't seem to be an authentication step.
answered Nov 14 '18 at 20:29
The.NetDeveloperThe.NetDeveloper
13
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53304359%2fazure-chatbot-not-working-after-publishing-from-visual-studio2017%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
401 is unauthorized so did you make sure your file containing your authorization key got published?
If the file is not part of your solution/project it will not get deployed. Make sure that file is available post deployment on your app service (I presume?), you can use Kudu by going to [AppServiceName].scm.azurewebsites.net
Use the Debug Console to verify the file.
answered Nov 14 '18 at 20:04
Simon BourdeauSimon Bourdeau
19114
add a comment |
401 is unauthorized so did you make sure your file containing your authorization key got published?
If the file is not part of your solution/project it will not get deployed. Make sure that file is available post deployment on your app service (I presume?), you can use Kudu by going to [AppServiceName].scm.azurewebsites.net
Use the Debug Console to verify the file.
answered Nov 14 '18 at 20:04
Simon BourdeauSimon Bourdeau
19114
add a comment |
401 is unauthorized so did you make sure your file containing your authorization key got published?
If the file is not part of your solution/project it will not get deployed. Make sure that file is available post deployment on your app service (I presume?), you can use Kudu by going to [AppServiceName].scm.azurewebsites.net
Use the Debug Console to verify the file.
answered Nov 14 '18 at 20:04
Simon BourdeauSimon Bourdeau
19114
401 is unauthorized so did you make sure your file containing your authorization key got published?
If the file is not part of your solution/project it will not get deployed. Make sure that file is available post deployment on your app service (I presume?), you can use Kudu by going to [AppServiceName].scm.azurewebsites.net
Use the Debug Console to verify the file.
answered Nov 14 '18 at 20:04
Simon BourdeauSimon Bourdeau
19114
answered Nov 14 '18 at 20:04
Simon BourdeauSimon Bourdeau
19114
answered Nov 14 '18 at 20:04
Simon BourdeauSimon Bourdeau
19114
answered Nov 14 '18 at 20:04
Simon BourdeauSimon Bourdeau
19114
19114
add a comment |
add a comment |
You need to look at your authentication. Usually, there should be some sort of session ID token that your browser session caches after authentication. From what you told us, there doesn't seem to be an authentication step.
answered Nov 14 '18 at 20:29
The.NetDeveloperThe.NetDeveloper
13
add a comment |
You need to look at your authentication. Usually, there should be some sort of session ID token that your browser session caches after authentication. From what you told us, there doesn't seem to be an authentication step.
answered Nov 14 '18 at 20:29
The.NetDeveloperThe.NetDeveloper
13
add a comment |
You need to look at your authentication. Usually, there should be some sort of session ID token that your browser session caches after authentication. From what you told us, there doesn't seem to be an authentication step.
answered Nov 14 '18 at 20:29
The.NetDeveloperThe.NetDeveloper
13
You need to look at your authentication. Usually, there should be some sort of session ID token that your browser session caches after authentication. From what you told us, there doesn't seem to be an authentication step.
answered Nov 14 '18 at 20:29
The.NetDeveloperThe.NetDeveloper
13
answered Nov 14 '18 at 20:29
The.NetDeveloperThe.NetDeveloper
13
answered Nov 14 '18 at 20:29
The.NetDeveloperThe.NetDeveloper
13
answered Nov 14 '18 at 20:29
The.NetDeveloperThe.NetDeveloper
13
13
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53304359%2fazure-chatbot-not-working-after-publishing-from-visual-studio2017%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you have other pages in your bot that work? For example, do you have the default.htm page that comes by default underneath wwwroot folder? (Browse to https://<your bot application>.azurewebsites.net/ to test). Does browsing to the endpoint (https://<your bot application>.azurewebsites.net/api/messages) give you the typical HTTP 405, or does it also give a 401/403?
– Dana V
Nov 19 '18 at 20:04