Why isn't my domain name working?
There are a few reasons why your custom domain may not be working as expected:
- You do not own the domain that you are trying to add. To be able to add a domain name to your store you need to have purchased your domain from a registrar such as iwantmyname.com.
- Once the domain has been entered, it may take up to 48-72 hours for the redirect to take effect, although it’s normally a lot faster than that
- You are no longer on a paid plan. Did your plan payment fail? Did you downgrade to a free plan? To use your own domain name you need to be on one of our paid plans. If we've tried to bill your card but have been unable to take payment, then your plan will expire and your domain will no longer be valid in your store. You'll need to update your credit card in Settings > Billing to start-up billing again.
- Problem with SSL due to mixed content or old browser (see below)
Please note that custom domains cannot contain 'selz.com' ie: mystoreselz.com
If you or your buyers are having trouble viewing your store or receive an error message after going through the above steps - this could be due to the following reasons:
- Old DNS Setup
- Old browser
- Mixed content
Old DNS Record
If the information that you set at your DNS record is using our old deprecated setup, you will be presented a notification suggesting that you update it using the current DNS records indicated below to prevent having SSL downtime.
Arecord and point it to
CNAMErecord for web address that points to
Please take note that some older browsers do not support the security standards required by SSL certificates.
Here is a list of unsupported browsers:
- All versions of Internet Explorer on Windows XP
- Internet Explorer versions older than 7
- Firefox versions older than 2.0
- Safari versions older than 2.1
- Any Google Chrome version older than 6
Unsupported mobile browsers include:
- All versions of Safari running iOS older than 4.0
- Any Android browser running on a version older than 3.0 (Honeycomb)
- Any Windows Phone browser running on a version older than 7
Buyers that go to your store may have trouble loading the secure, HTTPS version of your site and may not be able to load it at all.
Mixed content occurs when a page is loaded over a secure HTTPS connection but third-party content, resources, and customizations (like images, videos, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content is being loaded on the same page, and the initial request was secure over HTTPS. Your buyer, upon reaching your site will receive a warning about this type of content.
Solution: To avoid this, update the linked content within your store to an HTTPS URL. If this does not work and you are unable to source the content elsewhere, you have the option to disable the SSL within your domain panel as a last resort.