Internal
server error

An environment via the specified host could not be found.

Recommendations:

By default, all requests to Jelastic PaaS environments without external IP addresses are processed through the platform Shared Load Balancer. It redirects incoming traffic to the target instance, i.e. entry point of the required environment.

In order to bind custom domain name to such environment, a special CNAME (canonical name) redirect should be configured. It specifies an alias for a canonical name record of your environment in a Domain Name System (DNS) database.

Note: If your environment uses Public IP as an entry point, you’ll need to follow another instruction on setting up DNS A Record to bind your custom domain name.

So, to set custom domain for your project instead of the default env_name.{hoster_domain} link by means of CNAME, follow the step-by-step instruction below:

  1. Log in to your domain registrar and add canonical name (CNAME) for the preliminary bought external domain so it points to your Jelastic environment URL, e.g.:

    www.myexternaldomain.com CNAME env_name.{hoster_domain}

  2. Next, switch to the Jelastic dashboard and click the Settings button (the wrench icon) for the environment you need to bind this domain name to.

  3. Within the automatically selected Custom domains menu tab, use the Domain binding section to specify your domain name (e.g. www.myexternaldomain.com) and Bind it with the corresponding button.

    binding

Note: It may take up to several minutes until the new URL settings will take effect.

These steps will make your environment within Multi-Cloud PaaS for Java, PHP, Node.js, Go, Ruby, Python, Docker, Kubernetes accessible under its unique domain name.