You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -123,18 +122,24 @@ Open the .bot file you decrypted. Copy **all** entries listed under the `service
123
122
124
123
Save the file.
125
124
125
+
You can use the msbot tool to generate a new secret and encrypt the .bot file before you publish. If you re-encrypt your .bot file, update the bot's **botFileSecret** in the Azure portal to contain the new secret.
126
+
127
+
```cmd
128
+
msbot secret --bot <name-of-bot-file> --new
129
+
```
130
+
126
131
### Setup a repository
127
132
128
-
To support continuous deployment, create a git repository using your favorite git source control provider. Commit your code into the repository.
133
+
To support continuous deployment, create a git repository using your favorite git source control provider. Commit your code into the repository.
129
134
130
135
Make sure that your repository root has the correct files, as described under [prepare your repository](https://docs.microsoft.com/azure/app-service/deploy-continuous-deployment#prepare-your-repository).
131
136
132
137
### Update App Settings in Azure
133
-
The local bot does not use an encrypted .bot file, but the Azure portal has an that you are deploying doesn't
138
+
The local bot does not use an encrypted .bot file, but the Azure portal is configured to use an encrypted .bot file. You can resolve this by removing the **botFileSecret** stored in the Azure bot settings.
134
139
1. In the Azure portal, open the **Web App Bot** resource for your bot.
135
140
1. Open the bot's **Application Settings**.
136
141
1. In the **Application Settings** window, scroll down to **Application settings**.
137
-
1. Locate the **botFileSecret** and delete it.
142
+
1. Locate the **botFileSecret** and delete it. (If you re-encrypted your .bot file, make sure the **botFileSecret** contains the new secret and **do not** delete the setting.)
138
143
1. Update the name of the bot file to match the file you checked into the repo.
Copy file name to clipboardExpand all lines: articles/bot-service-debug-bot.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: kamrani
8
8
ms.topic: article
9
9
ms.service: bot-service
10
10
ms.subservice: sdk
11
-
ms.date: 2/09/2019
11
+
ms.date: 2/26/2019
12
12
---
13
13
14
14
# Debug a bot
@@ -133,8 +133,10 @@ Additionally, you can view log details in the console window.
133
133
134
134
## Additional resources
135
135
136
-
To learn about debugging bots in production, refer to [Debug any channel locally using ngrok](https://blog.botframework.com/2017/10/19/debug-channel-locally-using-ngrok/) blogpost.
136
+
- See [troubleshoot general problems](bot-service-troubleshoot-bot-configuration.md) and the other troubleshooting articles in that section.
137
+
- See the how to [debug any channel locally using ngrok](https://blog.botframework.com/2017/10/19/debug-channel-locally-using-ngrok/) blog post.
137
138
138
139
## Next steps
140
+
139
141
> [!div class="nextstepaction"]
140
-
> [Debug your bot using transcript files](~/v4sdk/bot-builder-debug-transcript.md).
142
+
> [Debug your bot using transcript files](v4sdk/bot-builder-debug-transcript.md).
Copy file name to clipboardExpand all lines: articles/bot-service-debug-emulator.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.author: v-demak
7
7
manager: kamrani
8
8
ms.topic: article
9
9
ms.service: bot-service
10
-
ms.date: 11/13/2018
10
+
ms.date: 2/26/2019
11
11
---
12
12
13
13
# Debug with the emulator
@@ -76,7 +76,9 @@ Open the **Emulator Settings**, enter the path to ngrok, select whether or not t
76
76
77
77
The Bot Framework Emulator is open source. You can [contribute][EmulatorGithubContribute] to the development and [submit bugs and suggestions][EmulatorGithubBugs].
78
78
79
+
For troubleshooting, see [troubleshoot general problems](bot-service-troubleshoot-bot-configuration.md) and the other troubleshooting articles in that section.
Copy file name to clipboardExpand all lines: articles/bot-service-troubleshoot-authentication-problems.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: v-demak
6
6
manager: kamrani
7
7
ms.topic: article
8
8
ms.service: bot-service
9
-
ms.date: 12/13/17
9
+
ms.date: 02/26/2019
10
10
---
11
11
12
12
# Troubleshooting Bot Framework authentication
@@ -222,6 +222,7 @@ If the bot responds appropriately to the input, you have verified that your bot
222
222
223
223
If you are still experiencing issues after completing the steps above, you can:
224
224
225
+
* Review how-to [debug a bot](bot-service-debug-bot.md) and the other debugging articles in that section.
225
226
*[Debug your bot in the cloud](~/bot-service-debug-emulator.md) using the Bot Framework Emulator and <ahref="https://ngrok.com/"target="_blank">ngrok</a>.
226
227
* Use a proxying tool like [Fiddler](https://www.telerik.com/fiddler) to inspect HTTPS traffic to and from your bot. *Fiddler is not a Microsoft product.*
227
228
* Review the [Bot Connector authentication guide][BotConnectorAuthGuide] to learn about the authentication technologies that the Bot Framework uses.
Copy file name to clipboardExpand all lines: articles/bot-service-troubleshoot-bot-configuration.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: kamrani
8
8
ms.topic: article
9
9
ms.service: bot-service
10
10
ms.subservice: sdk
11
-
ms.date: 12/20/2018
11
+
ms.date: 2/26/2019
12
12
---
13
13
14
14
# Troubleshoot bot configuration issues
@@ -82,3 +82,7 @@ Below are some additional links that can help with individual channels:
82
82
Occasionally, some channels might have an interruption of service. Usually, such outages don't last long. However, if you suspect an outage, consult a channel web site or social media.
83
83
84
84
Another way to determine if a channel has an outage is to create a test bot (such as a simple Echo Bot) and add a channel. If the test bot works with some channels but not others, that would indicate that the problem is not in your production bot.
85
+
86
+
## Additional resources
87
+
88
+
See how-to [debug a bot](bot-service-debug-bot.md) and the other debugging articles in that section.
Copy file name to clipboardExpand all lines: articles/bot-service-troubleshoot-general-problems.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: v-demak
6
6
manager: kamrani
7
7
ms.topic: article
8
8
ms.service: bot-service
9
-
ms.date: 09/26/2018
9
+
ms.date: 02/26/2019
10
10
---
11
11
12
12
# Troubleshooting general problems
@@ -15,11 +15,12 @@ These frequently asked questions can help you to troubleshoot common bot develop
15
15
## How can I troubleshoot issues with my bot?
16
16
17
17
1. Debug your bot's source code with [Visual Studio Code](debug-bots-locally-vscode.md) or [Visual Studio](https://docs.microsoft.com/en-us/visualstudio/debugger/navigating-through-code-with-the-debugger?view=vs-2017).
18
-
2. Test your bot using the [emulator](bot-service-debug-emulator.md) before you deploy it to the cloud.
19
-
3. Deploy your bot to a cloud hosting platform such as Azure and then test connectivity to your bot by using the built-in web chat control on your bot's dashboard in the <ahref="https://dev.botframework.com"target="_blank">Bot Framework Portal</a>. If you encounter issues with your bot after you deploy it to Azure, you might consider using this blog article: [Understanding Azure troubleshooting and support](https://azure.microsoft.com/en-us/blog/understanding-azure-troubleshooting-and-support/).
20
-
4. Rule out [authentication][TroubleshootingAuth] as a possible issue.
21
-
5. Test your bot on Skype. This will help you to validate the end-to-end user experience.
22
-
6. Consider testing your bot on channels that have additional authentication requirements such as Direct Line or Web Chat.
18
+
1. Test your bot using the [emulator](bot-service-debug-emulator.md) before you deploy it to the cloud.
19
+
1. Deploy your bot to a cloud hosting platform such as Azure and then test connectivity to your bot by using the built-in web chat control on your bot's dashboard in the <ahref="https://dev.botframework.com"target="_blank">Bot Framework Portal</a>. If you encounter issues with your bot after you deploy it to Azure, you might consider using this blog article: [Understanding Azure troubleshooting and support](https://azure.microsoft.com/en-us/blog/understanding-azure-troubleshooting-and-support/).
20
+
1. Rule out [authentication][TroubleshootingAuth] as a possible issue.
21
+
1. Test your bot on Skype. This will help you to validate the end-to-end user experience.
22
+
1. Consider testing your bot on channels that have additional authentication requirements such as Direct Line or Web Chat.
23
+
1. Review the how-to [debug a bot](bot-service-debug-bot.md) and the other debugging articles in that section.
0 commit comments