You need to sign in to do that
Don't have an account?
Neil Chelliah
How do you use a custom domain when enabling Communities?
How do I assign a custom domain when enabling Communities? The Salesforce Help article states that it's possible but doesn't explain how and tech support hasn't been able to resolve it either. I've gone to Domain Management>Domains and added a new domain (ex. community.company.com). We've updated our domain controllers to include the appropriate CNAME records as required. But when going to Customize>Communities>Settings and checking Enable Communities, it still forces you to select a domain that ends in ".force.com", not your custom domain. We're building an external site which our company cannot include the ".force.com" ending.
I know that this is supposed to be supported, based on documentation and first-hand feedback from Salesforce.
Have you enabled HTTPS custom domains for your organization? This is required.
Are you testing this in a sandbox or in Production? Custom domains are supported only in non-sandbox instances.
Do you have more than one community on the domain? If so, you'll need to use Custom URLs.
Can you post a screenshot of the domain details?
Thanks,
Phil
Our web developer (not Salesforce specific) can't do it, and we had a pro bono request from Salesforce (we are a non-profit) come back with the following response:
I further worked on it and below is my analysis:
- Remote address is throwing the 404 response
Status code: 404
Remote Address: 217.160.0.196:443
- On accessing the workspace for the community " Website " also, I am getting the same error 404 response
- If I access the community on site.com platform with force.com domain, it is working fine without any issue
https://noisesolution.force.com/website/s/
- For confirming that the issue is from CDN side, I added host to the network traffic and the workspace is getting loaded without any issue.
- For reference, please find the attached video
- So the issue is coming from the CDN side and you need to reach out to them as we do not have access to the CDN configuration.
This is way outside our skillset! Can anyone help? We would potentially be happy to pay someone to fix this for us too. We just need it sorted!