NexusCore has been discontinued. Please read more about it in our blog posts.

NexusCore Knowledgebase


Below you’ll find our FAQ containing some of the most-asked questions for NexusCore.

Installation / Deinstallation questions

Can I Install SQL Server later?

When you install NexusCore you are given the choice to install SQL Server for linux. If you want to install SQL Server later, you can do so by running the following command:

/usr/local/nexuscore/ install_mssql

How to uninstall NexusCore

You can simply uninstall nexuscore by running the command below. Keep in mind that any accounts running dotnet core will _not_ be reverted to a php_only hosting package, and you will need to do this yourself. This process is irreversable.

/usr/local/nexuscore/ uninstall

Troubleshooting / Debugging

The dotnet and sql icons do not show up in cPanel

During installation of NexusCore, two hosting packages are created:

  • dotnet core without SQL Server
  • dotnet core with SQL Server

These hosting packages might not have been created correctly. Go into WHM, and choose the “edit package” menu item. Select the package that is not working and edit it.

On the next screen, verify that the correct options have been set for the package, at the bottom of the page:

Once you’ve validated the options, and found a mistake:

  1. Correct the options
  2. Change the hosting account back to a PHP-based hosting account
  3. Change the hosting account back to a DOTNET-based hosting account
  4. The account should now be able to see the dotnet and sql server icons.

The hosting account webpage is shows an empty directory

When the website is showing an empty directory, the package is probably not set up correctly with dotnet core. Please refer to the previous question to fix this issue.

Fix 503 - Internal server error

A 503 – Internal server error can mean a number of things. In essence it means that dotnet core cannot run your application. This can be due to a number of reasons:

  1. You do not have your application deployed in the /home/ACCOUNT/public_aspnet folder
  2. Dependancies
  3. Runtime errors


The first is quite straightforward to fix: Just follow the guide in cPanel on how to deploy your application, and this should be automatically fixed.


Your dotnet core application is built against a version of the SDK. Common versions are: 2.1, 2.2, 3.0. Our auto updater does not yet install all available SDKs at the moment (due to eating a lot of disk space). You can easily installed the most common SDKs by running the following command as root:

yum install -y aspnetcore-runtime-2.1 
yum install -y aspnetcore-runtime-2.2 
yum install -y aspnetcore-runtime-3.0
yum install -y aspnetcore-runtime-3.1

Runtime errors

Once your application is running, but you still receive errors, it might be possible that your application itself is throwing errors (no connection to database, entity framework migration errors, etcetera). You can view this errors in your cPanel account “.NET Logs”.

How do I manually debug an account?

If you cannot solve your issue with the troubleshooting steps in the previous FAQ items, you might want to manually debug your dotnet core application.

Please run the following command as root:

Change the CPANEL ACCOUNT NAME and the application dll name. You should now see dotnet core trying to start your application. Any errors should popup on the screen right there for you to fix. Don’t forget to “start” the service afterwards.

system nexuscore-account-CPANELACCOUNTNAME.service stop
cd /home/CPANELACCOUNTNAME/public_aspnet
/usr/bin/dotnet YOURAPPLICATION.dll