Using your own domain for your coapp community platform
With coapp you can run your community under your own domain as well to have a fully white-labelled customer experience.
If you want to use your own domain for coapp you need to be in the appropriate subscription and reach out to our customer support which will guide you through the setup process.
Preparations
Currently, it is only possible to set up a sub-domain of your own domain to use for your coapp community.
Make sure you are the owner and have access to the configuration of the top-level domain you want to use for your community. For example
yourbrandname.comDefine a sub-domain under which you want your members to reach your community. For example
community.yourbrandname.com.Create a CNAME record in your DNS for the domain you chose pointing to
domains.coapp.space
Create a CNAME record in your DNS for the domain you chose pointing to domains.coapp.space
Following the above example the record would look like this:
Type | Name | Value |
CNAME |
|
|
Reach out to the coapp customer support
Once all preparations are in place reach out to the coapp customer support in order to set up your custom domain. Provide the you chose before, in our example community.yourbrandname.com
You will receive a list of additional DNS-Records from the customer support to complete the setup on your side. Once you have made these records inform the support agent that you have done so.
The support agent will then complete the setup and your community will become fully available through your custom domain – in this example community.yourbrandname.com
Troubleshooting
SSL-Certificate issues
There a some technical requirements in your dns records that you should be aware of:
coapp issues a SLL certificate on your domains' behalf in order to secure all traffic in your community
A Certificate Authority Authorization (CAA) record allows domain owners to restrict issuance to specified Certificate Authorities (CAs). (Read more here)
To prevent issues with your SSL certifacte, you as the domain owner should make sure there are no CAA records (which means, allowing all CAs to issue certificates), or include CAA records required (to allow CAs to issue certificates). coapp's SaaS SSL-certificates are currently issued by Let's Encrypt or Google Trust Services, so these authorities need to be allowed. To allow these CAs add these records to your configuration:
# CAA records for Let's Encrypt
# issue "letsencrypt.org"
# issuewild "letsencrypt.org"
# CAA records for Google Trust Services
# issue "pki.goog; cansignhttpexchanges=yes"
# issuewild "pki.goog; cansignhttpexchanges=yes"
If you need help setting up the technical requirements for your domain, please contact our customer support.