# Deploy Openboxes to Azure problem
**URL:** https://community.openboxes.com/t/deploy-openboxes-to-azure-problem/793
**Category:** troubleshooting
**Created:** [July 16, 2023, 8:02pm UTC](https://community.openboxes.com/t/deploy-openboxes-to-azure-problem/793 "2023-07-16T20:02:54Z")
**Posts on this page:** 1
**Showing post:** 10
### Author:  [@jmiranda](https://community.openboxes.com/u/jmiranda)
#### Post date: [July 22, 2023, 4:05am UTC](https://community.openboxes.com/t/deploy-openboxes-to-azure-problem/793/10 "2023-07-22T04:05:30Z")
> [@ruben.ser](#):
>
> As I explained to you already, I was trying to deploy the Openboxes to Azure portal.
Understood. This week, I was working on a fix for the Deploy to Azure bug through the following ticket.
>
>
> A user encountered the following issue when using the Deploy to Azure feature.
> …
> !\[image\](https://github.com/openboxes/openboxes-devops/assets/1162935/0f3a6dea-c458-4b2b-9cba-e7f0022d9c03)
>
> See the discussion on Discourse for more details.
> https://community.openboxes.com/t/deploy-openboxes-to-azure-problem/793
As of earlier today, the Deploy to Azure feature is now completing successfully.
Unfortunately, there’s a bug in the application that’s preventing it from starting. Hypotehtically, you could use the Deploy to Azure feature to create all of the Azure resources needed to run OpenBoxes and then just wait for us to fix the bug. But that might be a waste of money, so I’d recommend waiting.
I have created a bug ticket for that issue and will try to work on it next week. [OBGM-626.pdf](https://community.openboxes.com/uploads/short-url/sftWnpGdOlblyLI9s3e5poRVpXU.pdf) (95.3 KB)
* * *
As mentioned in an earlier reply, the Deploy to Azure feature will deploy a pre-release version (v0.9.0-SNAPSHOT) of OpenBoxes to Azure. This is a very buggy version of the application, so it is not recommended for production use. We are hoping to release v0.9.0 in the Autumn.
The Deploy to DigitalOcean feature will install a production-ready version (v0.8.20-hotfix1) of the application to DigitalOcean.
* * *
> [@ruben.ser](#):
>
> However, I was not able to find a solution with the DigitalOcean deployment yet…
Here’s the Deploy to DigitalOcean button.
[](https://marketplace.digitalocean.com/apps/openboxes-server?refcode=da4712a483b4&action=deploy)
… along with a link with complete instructions on how to deploy OpenBoxes to a DigitalOcean droplet.
> [@Install OpenBoxes via DigitalOcean Marketplace](https://community.openboxes.com/t/install-openboxes-via-digitalocean-marketplace/311):
>
> We’re very excited to announce that OpenBoxes can now be installed as a DigitalOcean droplet using the 1-Click App DigitalOcean Marketplace. This makes installing OpenBoxes much easier as all of the legwork (i.e. installing dependencies, creating and populating the database, configuring the application) has been taken care of for you. You just need to create a DigitalOcean account, pick your droplet size, region, and go. Note: You will be charged (2GB = $10 per month, 4GB = $20 per month, 4…
---
_[View the full topic](https://community.openboxes.com/t/deploy-openboxes-to-azure-problem/793)._