GhostlyHosting for self-hosted .NET applications
GhostlyHosting for Blazor server hosting on your own VPS
GhostlyHosting transforms an Ubuntu VPS into a practical hosting environment for Blazor Server and ASP.NET Core apps. It guides GitHub deployments, Nginx reverse proxy setup, SSL certificates, Cloudflare DNS, backups, and service management via a single console workflow.
Summary
GhostlyHosting assists VPS control but is not a managed hosting platform
Use GhostlyHosting if you want control over your server but prefer not to manually repeat every Nginx, systemd, SSL, GitHub, and Cloudflare step. It simplifies small production setups, but you retain responsibility for server, updates, secrets, backups, and monitoring.
Suitability check
Use GhostlyHosting when VPS control outweighs managed hosting convenience
The key question isn’t if GhostlyHosting can deploy an app—it can. It’s whether owning the server benefits your project more than managed platforms.
Where GhostlyHosting assists
- You want a small Blazor Server or ASP.NET Core app hosted on your own Ubuntu VPS.
- You require SSH access, custom services, direct log access, and consistent server paths.
- You are confident reviewing Nginx, systemd, DNS, and firewall modifications.
- You want GitHub deployments, SSL, and rollback support without scripting every step manually.
Where managed hosting is simpler
- You prefer not to manage Ubuntu security updates, backups, disk space, and service health.
- Your team expects managed scaling, managed databases, platform logs, and provider support as standard.
- You cannot securely store and rotate GitHub, Cloudflare, or provider tokens.
- Your app should be deployable by non-technical editors or support personnel.
Contents
Before setup
Prepare accounts and access before running the installer
GhostlyHosting is valuable once the basics are in place: a clean Ubuntu VPS, domain, GitHub access, a Cloudflare token for DNS validation, and sufficient server knowledge to assess changes.
GitHub token
Use the minimal token scope needed to clone or pull your repositories. Avoid broad personal tokens on shared servers.
Cloudflare token
DNS validation requires a token authorised to edit the correct zone. Keep it domain-scoped and rotate when access changes.
Ubuntu VPS
Begin with a clean Ubuntu server, secure SSH, and maintain simple provider firewall rules before adding apps.
Workflow
The clear sequence is server first, repository second, then app.
Consider the first run as infrastructure setup, not merely app deployment. Secure server access, correct DNS pointing, and clear environment variables are essential before traffic arrives.
Prepare the server
Set up a clean Ubuntu VPS, enable SSH access, apply updates, assign a staging domain, and ensure ports 80 and 443 are accessible.
Connect the repository
Choose the GitHub repository, branch, project path, and environment variables before the initial deployment.
Allow GhostlyHosting to configure the stack
The workflow sets up the app service, Nginx reverse proxy, SSL certificates, DNS integration, and deployment backup process.
Verify before production
Verify HTTPS, redirects, logs, restart behaviour, backup restoration, and minor content changes before switching the live domain.
Security
Automation does not eliminate server responsibility
GhostlyHosting configures services, certificates, and provider integrations but cannot define your threat model. Keep tokens scoped, rotate secrets, patch Ubuntu, test backups, and monitor logs after each deployment.
Limit access scope
GitHub and Cloudflare tokens should have minimal necessary scope. Store securely and rotate when devices or team members change.
Minimise public interface
Most app servers require only SSH, HTTP, and HTTPS ports open. Provider and Ubuntu firewalls should align accordingly.
Restoration is the true test
A backup is only valuable once you have restored it successfully. Test rollback before the app becomes critical.
Plan maintenance
GhostlyHosting assists deployment, but Ubuntu packages, .NET runtimes, certificates, logs, and disk usage still require management.
Screenshots
The screenshot gallery illustrates the management workflow post-setup
Retain the gallery as it illustrates the actual console workflow: app overview, repository selection, server health, and main menu. It supports the article rather than serving as mere decoration.
App overview
Dashboard displaying repository details, SSL status, DNS records, uptime, and management options.
Providers
DigitalOcean and UpCloud are convenient, though any clean Ubuntu VPS will suffice
Integrated provider support assists firewall management on DigitalOcean and UpCloud. Other Ubuntu VPS providers can host the app, but you might need to set up firewall rules and networking manually.
DigitalOcean
A well-known VPS route featuring droplets, firewalls, managed databases, and extensive documentation.
Check DigitalOceanUpCloud
A robust VPS choice for fast cloud servers, reliable pricing, and a clean Linux hosting environment.
Check UpCloudOther Ubuntu VPS
Suitable when you can manage firewall rules, DNS records, SSH access, and package updates independently.
Decision point
Opt for managed hosting if you prefer not to handle Linux operations
A VPS offers control, fixed costs, SSH access, custom services, and consistent file paths. It also requires managing patches, log rotation, disk space, backups, failures, and incident handling. GhostlyHosting eases setup but doesn’t convert a VPS into managed hosting.
| Question | VPS with GhostlyHosting | Managed hosting |
|---|---|---|
| Who applies server patches? | You do, even if deployment is automated. | Platforms or providers typically handle more runtime patching for you. |
| Who is responsible for backups? | You need to configure, test, and monitor backups and restoration procedures. | Managed services often provide snapshots, restore utilities, or database backups. |
| Who troubleshoots production? | You can directly examine logs, services, files, Nginx, and systemd. | You rely on platform logs and support limits rather than full server access. |
| Who manages costs? | VPS costs are predictable, but your operational time contributes to overall expense. | Costs may be higher, but reduced server maintenance can make it more economical overall. |
Get started
Start with a disposable server, then replicate the setup on production
The safest initial run uses a test VPS and staging domain. Once clear, repeat with production DNS, scoped tokens, real environment variables, and a tested backup plan.
Frequently Asked Questions
GhostlyHosting FAQ
Concise answers on setup, access, providers, SSL, backups, and when managed hosting is preferable.
Is GhostlyHosting a managed hosting service?
No. GhostlyHosting automates VPS setup, but you retain responsibility for the server, updates, secrets, backups, logs, and recovery.
Which cloud providers does GhostlyHosting support?
GhostlyHosting includes firewall support for DigitalOcean and UpCloud. Other Ubuntu VPS providers are compatible if you manage firewall and network settings yourself.
Does GhostlyHosting manage SSL certificates automatically?
Yes. It can request and renew Let’s Encrypt certificates via Cloudflare DNS validation if token and domain are correctly set.
Can I revert a failed deployment?
Yes. The deployment process retains backups allowing restoration of previous versions. Test this on a staging app before relying on it in production.
Is GhostlyHosting suitable for beginners?
Beginners can gain much from it, but it remains VPS hosting. If you prefer to avoid Linux management, managed hosting is generally simpler.