By default, your Eploy Candidate portals sit on an Eploy-owned URL (e.g. customerweb.eploy.net). Most customers point their own domain at it instead, so candidates stay on a familiar address throughout the application process.
The most common way to do this is with a subdomain - something like careers.yourcompany.com or apply.yourcompany.com. It is free, quick to configure, and used by most of our customers. We also support root domains and subfolders where your implementation requires it.
The three options at a glance:
Option | Example URL | When to use it |
Subdomain (recommended)
| Suitable for most customers.
Quick to set up, free, and works in almost every scenario. | |
Root Domain
| You have a dedicated careers domain and Eploy is building and hosting the whole site. | |
Subfolder
| Your existing site manages the main domain and Eploy needs to sit within a subfolder via reverse proxy. Less common - speak to your Implementation Manager. |
Your Implementation Manager will be happy to discuss the options with you and offer guidance on best practice based on your requirements.
📌 Note Your Agency/Vendor Portal will also run in a folder of the same domain. Your Hiring Manager Portal runs on a separate Eploy domain, independent of this setup. |
Subdomain (recommended)
A subdomain is the simplest and most popular option - used by the vast majority of Eploy customers. It creates a dedicated address for your careers content, like careers.yourcompany.com or apply.yourcompany.com.
You’ll need to create the new subdomain, and then to link up, you just need to add one DNS record:
Add a CNAME record - The value should be set to your Eploy system URL, which your Implementation Manager will give you. It will look something like: customerweb.eploy.net
That is it. SSL can be handled automatically via Let's Encrypt (free), or you can provide your own SSL certificate.
🤓 Tip Already using a subdomain for your careers site? Just let your Implementation Manager know - Eploy can either take over the existing address or run on a new one alongside it.
Root Domain
If your Candidate Portal will be using a root domain, you will need to do the following:
Add an A Record on the DNS with the target set to your Eploy system IP address (Eploy will provide the details to you).
Add a CNAME Record on the DNS for the www. version of the domain. This will create a subdomain that Eploy will use for Cloudflare, e.g. www.customer.com The target should be set to your Eploy system URL (your Implementation Manager will provide this to you). An example of this would be customerwebeploy.net
Subfolder (Reverse Proxy)
If your Candidate Portal will be using a subfolder, you will need to do the following:
A reverse proxy needs to be running on the root domain and forward subfolder requests to Eploy. How this is achieved depends on what you are using (e.g. Akamai/Nginx/Apache mod_proxy/IIS URL Rewrite)
Set the Edge Hostname - your Eploy Implementation Manager will provide this to you.
Set the Forward Host Header - your Eploy Implementation Manager will provide this to you.
If when clicking around the site you end up back on an eploy.net domain then this is not setup correctly. Places to test for this are:
Sign In > Register for Account.
Single Sign In > Linked In > Cancel.
Try to upload a cloud file. This won't work at all.
Try to select rows in a grid in the clientarea, if they select fine then it works.
📌 Note Each of these is a different test, if all 3 of these work then the Forward Host Header has been set up correctly. One common mistake is that instead of setting the Forward Host Header up you setup a hard replace on all content for systemnameweb.eploy.net to yourcompany.com. This will not work where Eploy encrypts the URL in links - such as with Single Sign On.
Ensure that the eploy.net SSL certificate is trusted (please be aware that this will change as we renew it). Please ensure you do not hardcode a specific SSL.
Example Config Issues with Proxy Software
Additionally, you may need to check and/or configure the following if using these:
IIS | IIS URL Rewrite must be installed. In IIS settings under "Application Request Routing" make sure that "Reverse rewrite host in response header" is unchecked. If there is no Application Request Routing option, install the extension. Create an empty folder for the subfolder being used. IIS will error without this. Make sure the presrveHostHeader setting is set to “true”. To stop proxy errors the following registry key needs to be set SECURITY_FLAG_IGNORE_CERT_CN_INVALID (0x00000100) |
Apache | mod_proxy – set ProxyPreserveHost to Yes |
Nginx | proxy_set_header Host to your root domain (e.g. yourcompany.com) |
Issues with Content Management Systems (CMS)
Please let us know what CMS you are using. For instance, there are some known issues with Umbraco. You will also need to make sure you have the subfolder listed in the Umbraco config option: umbracoReservedPaths.