Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEPLOY_ZIP_ERROR - Service Unavailable #8724

Closed
2 of 8 tasks
drguthals opened this issue Oct 4, 2021 · 4 comments
Closed
2 of 8 tasks

DEPLOY_ZIP_ERROR - Service Unavailable #8724

drguthals opened this issue Oct 4, 2021 · 4 comments
Assignees
Labels

Comments

@drguthals
Copy link

Describe the bug

When attempting to deploy a bot from Bot Composer, I can successfully provision the resources in Azure, but when I Publish I get the error:

Screenshot of the error in Bot Composer that says DEPLOY_ZIP_ERROR and calls out that the service is unavailable. It also says StatusCode 503

When I go to my Azure resource in the Portal, I see an error on the Channels pane:
There was an error sending this message to your bot: HTTP status code ServiceUnavailable

Version

Version: 2.0.0
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu

To Reproduce

  1. Create a bot
  2. Provision Azure Resources in Bot Composer
  3. Publish Bot

Expected behavior

Bot is published and has an available channel for testing

@drguthals drguthals added Needs-triage A new issue that require triage Type: Bug Something isn't working labels Oct 4, 2021
@tonyanziano
Copy link
Contributor

Could be related to #8707

@drguthals
Copy link
Author

@tonyanziano - I was thinking that, but that one seemed to have an issue with acquiring the address? Whereas mine simply said the service wasn't available.

Definitely could still be related though

@tonyanziano
Copy link
Contributor

@natalgar while you are investigating #8707 could you please take a look at this as well and find out if they have a similar cause?

@gabog
Copy link
Contributor

gabog commented Dec 14, 2021

Closing this one since it seems to have been a sporadic issue

@gabog gabog closed this as completed Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants