Start with the application requirements
Record the runtime version, required extensions, database engine and writable directories. For PHP, check the supported version range; for .NET, identify the target framework and deployment mode. Another working site on the same server does not establish compatibility for this application.
Set the document root to the application’s public publish directory. If a framework uses a public directory, avoid exposing the whole project root. Separate source, backups and secrets from publicly served files.
Selecting PHP versions and limits
Inspect installed PHP versions and assign a suitable version to the site. Distinguish per-site settings from server defaults: a global change can affect other applications using the same version.
Evaluate upload size, execution time and memory limits against actual requirements. Increasing PHP limits alone may not help if IIS or an upstream proxy has a lower limit. Measure the result with a real upload and application logs.
Deployment checks for ASP.NET and Classic ASP
- Prepare a production publish output, rather than copying only the source project.
- Verify the required IIS components and runtime.
- Select the appropriate ASP.NET, Classic ASP or mixed hosting configuration.
- Give the application pool read access and write access only where required.
- Configure production environment values and database connections securely.
- Test the homepage, authentication, database operations and static assets through the real HTTPS address.
Where should you start with a 500 error?
| Symptom | Investigation |
|---|---|
| Application does not start | Publish output, installed runtime and startup log |
| Database connection fails | Engine, address, account permissions and connection configuration |
| Uploads fail | Application/PHP, IIS and proxy limits; directory permissions |
| Page works but routes or CSS fail | Document root, static files and URL Rewrite rules |
Testing a runtime upgrade
Back up application files and the database together. Test a new PHP or .NET version on a separate site and check plugins and dependencies. Retain the previous deployment package for rollback. If the application changes its database schema, copying older files back may not be a complete recovery procedure.
Frequently asked questions
Must every website use the same PHP version?
The panel supports assigning a PHP version to a site. Available choices depend on installed versions and application compatibility.
Why does the site fail after uploading the files?
The runtime, IIS handler, document root, permissions and application connection settings must also be correct.