Common installation problems

Installation problems usually come from a mismatch between the product’s requirements and the hosting environment, incomplete configuration, missing files, database issues, domain/HTTPS problems, scheduled-task setup, or software activation.

Because DotwebApps products can have different technical requirements, always compare the problem with the System Requirements and Installation documentation supplied for the specific product before applying a fix.

1. Server requirements are not met #

Installation may fail when the hosting or server environment does not meet the product’s documented requirements.

Possible causes include:

• an incompatible PHP or database environment
• a required PHP extension or server feature is unavailable
• the hosting plan does not provide a capability the product needs
• resource or server restrictions prevent part of the installation from completing

Review Server requirements and PHP and MySQL requirements, then compare those general checks with the exact requirements for your product.

Do not change PHP, database, or server settings based on assumptions from another application.

2. Database connection fails #

A database-related error may occur if the connection information is incorrect, the database or user has not been created correctly, the assigned user lacks the access required by the application, or the database service is unavailable from the application environment.

Check the database name, user, host information, and other product-required connection settings without exposing the actual password publicly.

See Database configuration for safe general guidance.

3. File or permission errors #

Problems can occur when:

• files were not uploaded completely
• application files cannot be read by the web server
• a location that the product requires to be writable does not have the required access
• file ownership or hosting permissions prevent the application from working
• permissions have been made unnecessarily broad and create a security problem

Use only the permissions required by the specific product. Do not make the entire application writable or apply a blanket permissive setting as a universal fix.

See File permissions.

4. Domain or HTTPS configuration is incorrect #

Check whether:

• the intended domain or subdomain points to the correct server
• the SSL/TLS certificate is valid for that domain
• the production site loads correctly over HTTPS
• the application is using the intended production domain where a product-specific URL setting is required
• HTTP/HTTPS behavior is consistent for login, redirects, APIs, and other integrations

See SSL and domain configuration.

5. Upload or extraction problems #

An incomplete or corrupted upload can result in missing files, installer errors, or unexpected application failures.

Possible causes include:

• an incomplete product archive
• an interrupted or corrupted upload
• hosting upload or file-size restrictions
• extracting files to the wrong web location
• failing to replace all required files during an update or migration

Download the package again from the DotwebApps account associated with the purchase if necessary, and follow the product-specific installation instructions. See Uploading and installing software.

6. Required cron or scheduled task is not working #

Some products require scheduled tasks; others do not.

If the product requires one, verify that:

• the task has actually been configured
• the exact schedule and task definition match the product documentation
• the hosting environment supports the required scheduling method
• the task is executing successfully

Do not guess a cron command, URL, or frequency. See Cron jobs for general guidance.

7. License activation fails #

Activation problems may occur when:

• the wrong license information is being used
• the license belongs to a different DotwebApps product
• the applicable production activation limit has already been reached
• the domain or environment is not the intended installation
• required connectivity for activation is unavailable

Review How to activate software and follow any product-specific activation instructions.

8. Server error or blank page #

A server error or blank page can indicate that the application encountered an error that is not being displayed directly in the browser.

Where appropriate, review the application or server logs available in your hosting environment. Look for the error related to the failed request or installation step.

Before sharing logs or screenshots, remove passwords, database credentials, license keys, private keys, API secrets, tokens, customer information, and other sensitive data.

Avoid unsafe troubleshooting shortcuts #

Do not attempt to fix an installation by:

• disabling security globally
• making every file or directory broadly writable
• exposing debug information publicly
• deleting production data without an appropriate backup and verified procedure
• resetting a database blindly
• running commands copied from unrelated products

A workaround that hides the immediate error can create a larger security or data problem.

If the problem remains unresolved #

Contact DotwebApps support with enough non-secret information to identify the issue, such as:

• product name
• general hosting or server environment
• the installation step that failed
• the exact error message with sensitive information removed
• a relevant redacted screenshot
• troubleshooting actions already attempted

Never send passwords, private keys, API secrets, full source code, payment-card details, or unrelated credentials.

If your current hosting environment does not provide capabilities required by the specific DotwebApps product, you may need to contact that hosting provider or choose another suitable environment. DigiHostPro is one optional hosting choice you can explore, but you should compare any hosting plan with the exact requirements of the product you intend to install. Moving to DigiHostPro or another provider does not automatically resolve an installation problem.