VPS Hosting for CMS DotNetNuke on SSD
DotNetNuke (called DNN Platform in its documentation) is a .NET content management system built around IIS, Windows Server and a Microsoft SQL Server database. VPS hosting for DotNetNuke at HIP-HOSTING means a machine of your own, though the system on it has to be Windows: the panel offers trial images (Trial) and no DotNetNuke image at all. Find out what your version demands before picking a plan. Reserve extra RAM, because the site and its database frequently run side by side.
Get VPS from $3/mo- Standardfrom $3/mo
- Memoryfrom $10/mo
- Hi-CPUfrom $5/mo
VPS / VDS PLANS
Our VPS hosting plans for CMS DotNetNuke
Choose a location and plan line. Prices shown per month.
FAQ
Frequently asked questions
IN DETAIL
Service description
Platform and system
For releases 10.0.0 and newer the documentation names Windows 10 and 11, Windows Server 2016 and newer, and Azure App Service. The IIS role must be enabled and .NET Framework must be 4.8 or higher. One site means one Microsoft SQL Server database. Older releases have other requirements, which are listed in the documentation of that very release.
Image and licence
Every Windows image offered here carries a Trial label. A Windows licence is not mentioned in the image descriptions, so confirm the terms for long-term use with support before launching the project. The administrator password and remote desktop are set up just like on any Windows machine.
The IIS site and permissions
Create an IIS site that points at the folder with the unpacked platform. The account it runs under, for example IIS AppPool\poolname, needs Modify rights on that folder (Full Control also works). Do not hand out rights to the whole disk without need.
The database
Set up a blank database with a login of its own. Backups are taken with SQL Server Management Studio. Put a memory ceiling on the database server, or it will take everything.
Upgrading
From release 10.2.0 onward the upgrade runs from the panel: sign in as a superuser, open Settings → Servers → System Info → Upgrades and upload the package. Older releases follow a different order: the package is unpacked over the web folder and the upgrade wizard is started, so follow the guide for your version. Before that, copy the site files to a place outside its folder and save the database. If something goes wrong afterwards, restore files and database together, having cleared the site folder first. Follow the recommended chain of versions: first move to the closest listed version rather than jumping in one go.
Protection
Brute-force attempts against Windows remote desktop are common. Let in only trusted addresses, use a long password and patch the OS regularly. Keep the SQL port closed to the internet; a locally running site connects without it.
Speed
A DNN site benefits from caching and a responsive database. An NVMe VPS server with DotNetNuke can help SQL Server on large queries and index rebuilds; how many people can browse at the same moment still comes down to RAM.
Mail and disk
Route mail through an external provider, since mail ports on fresh servers can be shut. SQL data files and IIS logs keep growing, so check free space regularly. A panel disk can only be enlarged, never shrunk.
First start of Windows
When the image finishes installing, give it two or three minutes to set up the network and password. Then connect over remote desktop, bring the system up to date, enable the IIS role and make sure .NET Framework 4.8 is installed (older images may need it added separately). Only afterwards copy the platform and create the data store, so a failure is not buried among half-done settings.
Backups
The backup set is the site files copied outside their folder plus a database backup made in SQL Server Management Studio. Store the pair off the machine and try restoring it on a test box. Unchecked, it is only files.
Who it suits
- businesses whose DNN site must be relocated;
- .NET integrators maintaining client projects;
- teams wanting a staging copy beside production;
- owners of an inherited SQL Server and IIS site who prefer not to rewrite it.
Choosing a plan
Begin with the platform release, its .NET version and the SQL edition. If you mean to buy DotNetNuke VPS hosting, budget memory for the site and the database alike. Whoever wants to rent DotNetNuke VDS hosting must work out beforehand who patches Windows and runs backups. A VPS/VDS for DotNetNuke expands with the project, and cheap DotNetNuke VPS hosting is one where the database has room beside the site.