Save $300–$500 monthly on hosting costs with proper Umbraco configuration. When a .NET developer needs to quickly launch a powerful ASP.NET Core CMS with custom business logic, the choice often falls on Umbraco (Wikipedia). But the standard installation via dotnet new is just the beginning. Without proper Umbraco configuration, database setup, reverse proxy, and monitoring, a production environment will collapse under the first load. We have been through this on 50+ projects — from simple landing pages to portals with millions of requests. In this article, we will show how to avoid common mistakes and configure Umbraco to run stably and cost-effectively. Order a turnkey setup from $500 and save 20–30% on monthly hosting costs.
Why Umbraco on .NET?
Umbraco is one of the few CMS platforms that natively supports .NET. This gives full control over performance: you can use async requests, Redis caching, and Hangfire background jobs. Compared to PHP-based engines, Umbraco on .NET is up to 5 times faster for complex content trees — in our tests, the difference was 3–5 times on large data operations. For instance, in a comparison test, Umbraco on .NET was 5 times faster than WordPress on PHP for rendering a content tree with 10,000 nodes. Additionally, using .NET ensures 99.9% uptime with proper configuration. For high-load scenarios, it handles over 10,000 concurrent users without breaking a sweat.
Typical Installation Problems
Beginners often stumble on three things:
- Incorrect connection string. Using SQLite in production leads to LOCK errors under load. You need SQL Server with
TrustServerCertificate=True. SQL Server is 10x more reliable for concurrent access. - Forgotten migrations. After updating a package, migrations aren't run — the database remains on the old version, causing exceptions.
- Misconfigured reverse proxy. Without setting
X-Forwarded-Forheaders, real user IPs are lost, and speed drops due to missing keep-alive.
Production Configuration for Umbraco
We use a unified checklist that guarantees stability under load. Focus on Umbraco configuration, Umbraco deployment, Umbraco SQL Server, Umbraco Nginx, Umbraco IIS, Umbraco reverse proxy, Umbraco backup, and Umbraco Ubuntu for a robust setup. Let's look at the key steps using a VPS with Ubuntu 22.04 and SQL Server. Proper Umbraco configuration can reduce hosting costs by $200–$500 per month.
System Requirements
- .NET 8 SDK
- SQL Server 2019+ / SQL Server Express / SQLite (dev only)
- IIS 10+ / Kestrel + Nginx or Apache
- Windows Server 2019+ or Linux (Ubuntu 20.04+)
- Umbraco Ubuntu recommended for production
- Minimum 2 GB RAM, 20 GB disk
Installing Umbraco via CLI
To install Umbraco via CLI, run the following commands:
# Template for SQLite (development)
dotnet new umbraco -n MyProject --friendly-name "Admin" --email [email protected] --password "P@ssw0rd123" --connection-string "Data Source=|DataDirectory|/Umbraco.sqlite.db;Cache=Shared;Foreign Keys=True;Multithread Safety=True"
# Template for SQL Server (production)
dotnet new umbraco -n MyProject --connection-string "Server=localhost;Database=UmbracoDb;Trusted_Connection=True;TrustServerCertificate=True"
Configuring appsettings.json
Main Umbraco appsettings configuration file including database connection and Serilog for logging:
{
"ConnectionStrings": {
"umbracoDbDSN": "Server=srv;Database=UmbracoDb;User=sa;Password=secret;TrustServerCertificate=True",
"umbracoDbDSN_ProviderName": "Microsoft.Data.SqlClient"
},
"Umbraco": {
"CMS": {
"Global": {
"Id": "b9c6e1a1-0000-4000-8000-000000000001",
"SendVersionCheckResult": false,
"UseHttps": true,
"ReservedPaths": "~/.well-known",
"MainDomLock": "FileSystemMainDomLock"
},
"Security": {
"AllowPasswordReset": true,
"AuthCookieName": "UMB_UCONTEXT",
"UsernameIsEmail": true,
"UserPassword": {
"RequireDigit": true,
"RequireLowercase": true,
"RequireNonLetterOrDigit": false,
"RequireUppercase": true,
"RequiredLength": 10
}
},
"Content": {
"AllowedUploadFiles": ["jpg", "jpeg", "png", "gif", "webp", "svg", "pdf", "docx"],
"MaximumAllowedUploadSizeInBytes": 10485760,
"ResolveUrlsFromTextString": false
},
"DeliveryApi": {
"Enabled": true,
"ApiKey": "your-secret-key-here"
}
}
},
"Serilog": {
"MinimumLevel": {
"Default": "Warning",
"Override": {
"Microsoft": "Warning",
"Umbraco": "Warning"
}
},
"WriteTo": [
{
"Name": "File",
"Args": {
"path": "umbraco/Logs/UmbracoTraceLog.txt",
"rollingInterval": "Day",
"retainedFileCountLimit": 14
}
}
]
}
}
With proper configuration, you can save up to 30% on hosting resources through optimized caching and compression. And thanks to deployment automation, maintenance costs drop by an additional 20–30% — typically from $1,000 to $700 per month. That's a saving of $300 per month.
Web Server Configuration
IIS — the standard choice for Windows. Add the ASP.NET Core handler:
<!-- web.config -->
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="dotnet" arguments=".\MyProject.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess">
<environmentVariables>
<environmentVariable name="ASPNETCORE_ENVIRONMENT" value="Production" />
</environmentVariables>
</aspNetCore>
</system.webServer>
</location>
</configuration>
Nginx + systemd on Linux:
server {
listen 443 ssl http2;
server_name mysite.com;
ssl_certificate /etc/letsencrypt/live/mysite.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/mysite.com/privkey.pem;
client_max_body_size 20M;
location / {
proxy_pass http://127.0.0.1:5000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_cache_bypass $http_upgrade;
}
location /media/ {
alias /var/www/mysite/wwwroot/media/;
expires 30d;
add_header Cache-Control "public, immutable";
}
}
# /etc/systemd/system/mysite.service
[Unit]
Description=MyProject Umbraco site
After=network.target
[Service]
WorkingDirectory=/var/www/mysite
ExecStart=/usr/bin/dotnet /var/www/mysite/MyProject.dll
Restart=always
RestartSec=10
KillSignal=SIGINT
SyslogIdentifier=mysite
User=www-data
Environment=ASPNETCORE_ENVIRONMENT=Production
Environment=DOTNET_PRINT_TELEMETRY_MESSAGE=false
[Install]
WantedBy=multi-user.target
Activate the service: systemctl enable mysite && systemctl start mysite.
Microsoft's recommendations for ASP.NET Core deployment outline the reverse proxy requirements (Microsoft Docs).
Updates and Backups
To update the package, run dotnet add package Umbraco.Cms --version <version>, then start the project — migrations apply automatically. In production, first run migrations separately: dotnet umbraco migrate. Backing up the database and the wwwroot/media/ folder is mandatory before any update. Ensure a reliable Umbraco backup strategy.
What's Included
| Component | Description |
|---|---|
| Hosting selection | Choosing a VPS plan, installing the OS, configuring the firewall. |
| Umbraco installation | Via CLI or Visual Studio, creating an admin, configuring the backoffice. |
| Database configuration | Setting up SQL Server, optimizing indexes, scheduling backups. |
| Web server | Configuring Nginx/IIS, SSL certificate, HTTP/2, gzip. |
| Monitoring and logging | Serilog, log rotation setup, error alerts. |
| Documentation & training | Handing over access, admin instructions, training editors. |
Work Process
- Analysis — discuss requirements, load, technology stack.
- Design — select hosting, reverse proxy, database schema.
- Implementation — install and configure according to the checklist, including deployment automation.
- Testing — load testing, migration checks, response speed.
- Deployment — switch to production, monitor the first few hours.
- Support — handover of documentation, warranty service.
Timelines and Cost
Installation on a VPS with Nginx and SQL Server, backoffice setup, and first admin — from 1 day. Full cycle with SSL, systemd service, backup configuration, and basic content types — 2–3 days. Cost ranges from $500 for basic setup to $2,000 for complex projects with custom modules. Contact us for a consultation and accurate estimate.
Choosing Between SQL Server and SQLite
| Criteria | SQLite | SQL Server |
|---|---|---|
| Performance | Low under concurrent access | High, transaction support |
| Backup | File-based backup | Online backup, point-in-time |
| Reliability | No built-in replication | Always On, clustering |
| Recommendation | Development only | Production of any complexity |
We guarantee stable operation of your Umbraco project thanks to the experience of certified engineers. Order a turnkey setup from $500 and forget about infrastructure problems. Get a consultation for your project — we will select the optimal configuration.