[GH-ISSUE #1577] Failing deployment on Azure WebApp #1007

New issue

Closed

opened 2026-03-03 02:05:29 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 02:05:29 +03:00

Owner

Originally created by @Gyarbij on GitHub (Apr 2, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1577

Subject of the issue - Failing production instance

Deployment environment

bitwarden_rs version: 1.20.0 (from ASP logs)

Install method: Azure App Service Plan/Docker
Clients used: All
Reverse proxy and version:
MySQL/MariaDB or PostgreSQL version:
Other relevant details:

Expected behaviour -

To work

Actual behaviour -

Does not work and fails with the below

Troubleshooting data -

2021-04-02T14:02:26.743Z INFO - Initiating warmup request to container cxxxfor site cxxxx
2021-04-02T14:02:27.778Z ERROR - Container cxxx for site cxxx has exited, failing site start
2021-04-02T14:02:27.795Z ERROR - Container cxxx didn't respond to HTTP pings on port: 80, failing site start. See container logs for debugging.
2021-04-02T14:02:27.804Z INFO - Stopping site cxxxt because it failed during startup.

Originally created by @Gyarbij on GitHub (Apr 2, 2021). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1577   ### Subject of the issue - Failing production instance  ### Deployment environment     * bitwarden_rs version: 1.20.0 (from ASP logs)  * Install method: Azure App Service Plan/Docker * Clients used: All * Reverse proxy and version:  * MySQL/MariaDB or PostgreSQL version:  * Other relevant details: ### Steps to reproduce - Try to launch an Azure Web App with mounted file share for persistence  ### Expected behaviour - To work  ### Actual behaviour - Does not work and fails with the below  ### Troubleshooting data - 2021-04-02T14:02:26.743Z INFO - Initiating warmup request to container cxxxfor site cxxxx 2021-04-02T14:02:27.778Z ERROR - Container cxxx for site cxxx has exited, failing site start 2021-04-02T14:02:27.795Z ERROR - Container cxxx didn't respond to HTTP pings on port: 80, failing site start. See container logs for debugging. 2021-04-02T14:02:27.804Z INFO - Stopping site cxxxt because it failed during startup.

kerem closed this issue

2026-03-03 02:05:29 +03:00

kerem commented

2026-03-03 02:05:30 +03:00

Author

Owner

@RealOrangeOne commented on GitHub (Apr 2, 2021):

Got any application logs?

@RealOrangeOne commented on GitHub (Apr 2, 2021): Got any application logs?

kerem commented

2026-03-03 02:05:30 +03:00

Author

Owner

@BlackDex commented on GitHub (Apr 2, 2021):

You can't use sqlite on azure. Or, make sure to turn of wall, but if i remember correctly, that has mixed results.

The issue is that azure uses a samba/cifs based storage which does not work that well.

@BlackDex commented on GitHub (Apr 2, 2021): You can't use sqlite on azure. Or, make sure to turn of wall, but if i remember correctly, that has mixed results. The issue is that azure uses a samba/cifs based storage which does not work that well.

kerem referenced this issue

2026-03-03 09:08:37 +03:00

[PR #1007] [MERGED] Admin interface restyle #2853