{"id":644,"date":"2023-07-28T06:55:07","date_gmt":"2023-07-28T06:55:07","guid":{"rendered":"https:\/\/blog.hostinger.io\/support\/2023\/07\/28\/8184984-how-to-launch-an-asp-net-application-at-hostinger\/"},"modified":"2026-03-16T12:12:02","modified_gmt":"2026-03-16T12:12:02","slug":"8184984-how-to-launch-an-asp-net-application-at-hostinger","status":"publish","type":"post","link":"https:\/\/www.hostinger.com\/support\/8184984-how-to-launch-an-asp-net-application-at-hostinger\/","title":{"rendered":"How to Launch an ASP.NET Application at Hostinger"},"content":{"rendered":"

ASP.NET<\/a><\/b> is a popular web development framework created by Microsoft<\/b>. It allows developers to build dynamic and robust web applications, websites, and services using various programming languages like C#<\/b> and Visual Basic .NET<\/b>. <\/p>

\n<\/p>

With its powerful features and seamless integration with other Microsoft technologies, ASP.NET simplifies the process of creating and deploying web applications<\/b>.<\/p>

\n<\/p>

The ASP.NET supported on Ubuntu is ASP.NET core<\/b>. If you use ASP.NET MVC with .NET Framework<\/b> or Web API<\/b>, you might need to convert your project to ASP.NET Core MVC<\/a><\/b> before you can deploy it in our Linux VPS.<\/p>

\n<\/p>

To launch the ASP.NET application at Hostinger, you need a VPS<\/b> with Ubuntu 22.04 64bit with ASP.NET template<\/a><\/b> installed.<\/p>

\n<\/p>

\n

Visit our ASP.NET hosting<\/a><\/b> page to learn more about the VPS plans available 🚀 <\/p>\n<\/div>

\n<\/p>

Configure the ASP.NET Core Application<\/h2>

Once you log into your VPS via SSH<\/a><\/b>, you can check installed .NET versions by running this command:<\/p>

dotnet --version<\/code><\/pre>
To start off, we will create a simple web application from preinstalled templates and call it NewApp<\/b>:<\/p>
dotnet new webapp -o NewApp<\/code><\/pre>
This creates a new folder for your application: \/root\/NewApp\/<\/b>. Let’s change the default port of your application to 5000<\/b> in launchSettings.json<\/b>:<\/p>
nano \/root\/NewApp\/Properties\/launchSettings.json<\/code><\/pre>
It should look like this:<\/p>
  \"profiles\": {
    \"NewApp\": {
      \"commandName\": \"Project\",
      \"dotnetRunMessages\": true,
      \"launchBrowser\": true,
      \"applicationUrl\": \"http:\/\/localhost:5000\",
      \"environmentVariables\": {
        \"ASPNETCORE_ENVIRONMENT\": \"Development\"
      }
    }<\/code><\/pre>
Also, we have to remove the UseHttpsRedirection()<\/b> middleware because we’ll use NGINX to handle the HTTPS redirection. Open the Program.cs<\/b> file and make sure there are no app.UseHttpsRedirection()<\/b>:<\/p>
 nano \/root\/NewApp\/Program.cs<\/code><\/pre>
We can add app.UseForwardedHeaders()<\/b> middleware as well since we are using NGINX as a reverse proxy. It should look like this:<\/p>
var builder = WebApplication.CreateBuilder(args);
\/\/ Add services to the container.
builder.Services.AddRazorPages();
var app = builder.Build();
\/\/ Configure the HTTP request pipeline.
if (!app.Environment.IsDevelopment())
{
    app.UseExceptionHandler(\"\/Error\");
    \/\/ The default HSTS value is 30 days. You may want to change this for production scenarios, see https:\/\/aka.ms\/aspnetcore-hsts.
    app.UseHsts();
}
app.UseStaticFiles();
app.UseForwardedHeaders();
app.UseRouting();
app.UseAuthorization();
app.MapRazorPages();
app.Run();<\/code><\/pre>
\n<\/p>
Publish and Run the Application<\/h2>
To publish the application using the Release<\/b> configuration, make sure you’re in the project directory<\/b>, and then run the command below:<\/p>
cd \/root\/NewApp\/
dotnet publish --configuration Release <\/code><\/pre>
The project has been published. Now, we must create a service to ensure the application starts and runs. First, let’s create a service file for<\/b> our project inside the \/etc\/systemd\/system <\/b>directory:<\/p>
cd \/etc\/systemd\/system
sudo nano NewApp.service<\/code><\/pre>
In the new file, put the following configuration:<\/p>
[Unit]
Description=NewApp
 
[Service]
WorkingDirectory=\/root\/NewApp\/bin\/Release\/net6.0\/publish\/
ExecStart=\/usr\/bin\/dotnet \/root\/NewApp\/bin\/Release\/net6.0\/publish\/NewApp.dll
Restart=always
# Restart service after 10 seconds if the dotnet service crashes:
RestartSec=10
KillSignal=SIGINT
SyslogIdentifier=dotnet-NewApp
User=root
Environment=ASPNETCORE_ENVIRONMENT=Production
Environment=DOTNET_PRINT_TELEMETRY_MESSAGE=false
 
[Install]
WantedBy=multi-user.target<\/code><\/pre>
Now, let’s enable and start the service<\/b> using the commands below:<\/p>
sudo systemctl enable NewApp.service
sudo systemctl start NewApp.service<\/code><\/pre>
\n<\/p>
Install and Configure the NGINX<\/h2>
Start with installing the NGINX server<\/b>. It is a popular open-source web server software known for its high performance, scalability, and robustness. It is widely used as a reverse proxy server, load balancer, and HTTP cache.<\/p>
sudo apt-get -y install nginx certbot python3-certbot-nginx<\/code><\/pre>
After the installation is completed, let’s configure the NGINX<\/b>. To do that, you can edit the configuration file<\/b> using the command below:<\/p>
sudo nano \/etc\/nginx\/sites-available\/default <\/code><\/pre>
Let’s make two changes to this file. First, set your domain name in server_name<\/b>:<\/p>
server_name domain.tld; <\/code><\/pre>
Then, set the location<\/b> configuration as follows:<\/p>
location \/ {
    proxy_pass http:\/\/localhost:5000;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection keep-alive;
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}<\/code><\/pre>
\n<\/p>
Install an SSL and Launch the NGINX Proxy<\/h2>
Once the DNS propagation of your domain is completed, proceed with generating the SSL certificate <\/b>for your ASP.NET application. Run the command below to generate the SSL certificate automatically:<\/p>
sudo certbot --nginx -d domain.tld<\/code><\/pre>
After that, restart the NGINX<\/b> to apply the configuration:<\/p>
nginx -t && nginx -s reload<\/code><\/pre>
Then, run the crontab <\/b>command to auto-renew the SSL certificate<\/b>:<\/p>
crontab -e<\/code><\/pre>
Finally, add the command below to auto-renew the SSL every day at 12:00 (noon)<\/b>:<\/p>
0 12 * * * \/usr\/bin\/certbot renew --quiet<\/code><\/pre>
And that is it! You can now access your application via the domain you configured in this tutorial 🎉 <\/p>\n","protected":false},"excerpt":{"rendered":"
Launching an ASP.NET application at Hostinger<\/p>\n","protected":false},"author":581,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"include_on_kodee":true,"footnotes":""},"categories":[199],"tags":[],"class_list":["post-644","post","type-post","status-publish","format-standard","hentry","category-vps-management"],"hreflangs":[{"locale":"en-US","link":"https:\/\/www.hostinger.com\/support\/8184984-how-to-launch-an-asp-net-application-at-hostinger\/","default":1}],"include_on_kodee":true,"_links":{"self":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/644","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/users\/581"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/comments?post=644"}],"version-history":[{"count":0,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/644\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/media?parent=644"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/categories?post=644"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/tags?post=644"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}