SSL and domain configuration

A production DotwebApps web application should normally use the intended production domain or subdomain and a valid HTTPS connection where required by the product.

The exact domain, DNS, SSL, and application URL settings vary by hosting provider and by DotwebApps product. Follow the product-specific installation documentation whenever it provides exact configuration instructions.

Configure the production domain #

Your production domain or subdomain must point to the hosting or server environment where the application is installed.

The exact DNS records, nameservers, and control-panel steps depend on your domain registrar, DNS provider, and hosting provider. DotwebApps does not use one universal DNS configuration for every customer.

A typical setup sequence is:

1. Prepare the hosting or server environment.
2. Point the intended domain or subdomain to that environment using the method supplied by your domain/DNS provider.
3. Confirm that the domain resolves to the correct server.
4. Configure HTTPS with a valid SSL/TLS certificate.
5. Confirm that the site loads correctly over HTTPS.
6. Configure the application’s domain or base-URL setting using the product-specific method where required.
7. Test login, redirects, APIs, external services, and other integrations that depend on the production URL.

DNS changes can take time to become visible across different networks. Because propagation behavior depends on DNS providers and caching, do not rely on one fixed propagation time.

Why HTTPS matters #

HTTPS protects data in transit between the customer’s browser or another service and the web application.

A valid HTTPS configuration may also be required for features such as authentication flows, API connections, browser security requirements, payment or third-party integrations, or other external services used by a particular product.

SSL/TLS certificates may be provided or managed through your hosting provider, server-control panel, or another certificate service. Use the method appropriate for your environment and the product’s documented requirements.

Avoid common configuration mistakes #

Before completing installation, verify that:

• the intended production domain points to the correct server
• the SSL certificate is valid for the domain being used
• the site loads over HTTPS without certificate errors
• the application is configured for the intended production URL where the product requires that setting
• HTTP/HTTPS redirects and integrations behave correctly
• an old, temporary, staging, or unrelated domain is not being used accidentally as the production installation

Do not copy DNS records, redirect rules, web-server directives, or application URL settings from unrelated products. Exact values depend on the environment and product.

Choosing hosting #

If you need hosting for a DotwebApps web application, you can also explore DigiHostPro as an optional hosting choice. Always confirm that the chosen hosting plan meets the requirements of the specific DotwebApps product you intend to install. Using DigiHostPro or any other provider does not by itself guarantee compatibility with every product.

If domain or SSL configuration remains unresolved, contact your hosting or domain provider for environment-specific assistance. If the DotwebApps product’s own configuration is unclear, contact DotwebApps support with the relevant product and sanitized error information. Never send passwords, private keys, API secrets, or other credentials.