• Saturday, August 14, 2021

SSL/TLS Method (Basic / Advanced)

  • ISHost provides two different SSL/TLS Method, Basic and Advanced
  • SSL/TLS Basic is where one SSL certificate is issued for all domains under a web application. It is the same feature before this update, and all existing SSL before this update becomes SSL/TLS basic for backward compatibility. It is available for all paid plans.
  • SSL/TLS Advanced is where one SSL certificate can be issued for each domain under a web application. It is available for Business managed plan users.
  • SSL/TLS Advanced is ideal for a web application with multiple domains, ideal for SaaS/WaaS sites with multisite/multitenancy support.
  • You can switch SSL/TLS basic Basic <--> Advanced SSL from WebApp settings or SSL/TLS page.

AutoSSL

  • AutoSSL provides the ability to deploy Lets Encrypt SSL automatically after you create new web apps, add a new domain to the web app, cloning web applications, and WordPress staging.
  • AutoSSL option is available when you use SSL/TLS Advanced method. It is available for Business managed plan users.
  • AutoSSL will try to deploy LetsEncrypt for the added domain within 24 hours. A self-signed SSL certificate is provided as a fallback during the AutoSSL process. Please make sure that the DNS record of the domain should be updated and propagated within 24 hours. 
  • AutoSSL can be combined with Cloudflare DNS integration to make both updating DNS records and deploying Lets Encrypt SSL run automatically.
  • For the existing website, the AutoSSL option can be enabled/disabled anytime from the WebApp settings menu

SSL/TLS Improvements 

  • ISHost offers a new SSL option, to deploy a Self Signed SSL Certificate. It is useful for development/testing purposes, not for production use.
  • Self Signed SSL Certificate can be used for the ISHost test domain.
  • Deploy/Edit SSL page layout has been improved and is easy to use.
  • For advanced users, you can also change SSL chippers and EDCH curves if you need them.

Domain Types

  • Domain in web applications now is divided into 3 types domain: primary, alias, redirect
  • The primary domain is the main domain of your web application
  • Alias domain is an extra/additional domain of your web application
  • Redirect is the domain that
  • Redirect is the domain that will be redirected to the primary domain (301 redirects).
  • For backward compatibility, all of your existing web app domains become alias domains. 
  • You can set an alias/redirect domain as the primary domain in your web application. 
  • For WordPress web applications, when you change your primary domain, search & replace will be done to update the domain URL of your WordPress database.

WWW, Preferred Domain Version, and Wildcard

  • Previously, you need to add the www version or wildcard as another domain name, separated from the main domain.
  • Now, you can enable/disable the www version and/or wildcard from a domain directly from your Domain name menu.
  • If the www version is enabled, you can choose the preferred domain version, either www or non-www or no preference. 
  • When you set “www” for the preferred domain version, non-www to www redirection is applied automatically without extra config.
  • When you set “non-www” for the preferred domain version, www to non-www redirection is applied automatically without extra config.
  • For backward compatibility, don’t set the preferred domain version for all domains in your existing web app before this update.
  • You can enable the www version and select the preferred domain version when you create new web apps, add a new domain, and create cloning/staging.

Cloudflare DNS Integration

  • You can enable Cloudflare DNS integration when you create new web apps, add a new domain, and create cloning/staging.
  • When Cloudflare DNS integration is active, DNS record(s) will be added/updated automatically also when you add a new domain, enable www, and enable wildcard
  • You can disable Cloudflare DNS integration of a domain under the Domain menu in your Web App. It is useful if you want to add the same domain to another server with Cloudflare DNS integration. 
  • When you deploy Lets Encrypt SSL with DNS-01 authorization method with SSL/TLS Advanced and Cloudflare DNS integration is active, Cloudflare API key will be automatically selected.

Bug Fixes

  • Fixed: update Traffic Stats for OpenLiteSpeed web apps
  • Fixed: show correct Server Management plan under user dropdown profile.
  • Fixed: delete Apache log when not using Nginx-Apache Hybrid stack
  • Fixed: clear Nginx cache from RC panel will still work when there is the issue on WordPress site
  • Fixed: when cloning a web app for a static site, the index.html file should not get removed