These are all the troubleshooting steps you can follow in order to resolve any issues experienced with Domain Mapping System.
Before contacting support with any questions about how domain mapping, DNS, or server configuration works, please read the guide in detail below. We don't expect everyone to know the ins-and-outs of these complex details, but this guide will help you.
If you still can't get the plugin working, feel free to reach out by reviewing the details below. However, sometimes a quick question can save hours of time. We're here to provide as much valuable knowledge as possible.
In some cases, more advanced diagnosis is required to determine the cause of any issues, for which we request your patience. This is a complex plugin and there are thousands of server environments, WordPress configurations, and potential conflicts with 3rd party plugins or themes.
If you have purchased the plugin, we promise to provide priority support and fully determine the exact cause of any issues via the troubleshooting steps below and/or with developer support, if necessary. We request that you attempt as many of the steps below as possible and fully read through the troubleshooting guide, as it provides a wealth of information in a condensed format.
If you have not yet purchased the plugin, we will still do our best to help you resolve any issues, but this troubleshooting guide should be adequate in 99% of cases for both free and paid customers.
Generally, any issues with the plugin fall into a few major categories, which we've tried to describe in a relatable way in each title below. You might want to start by reading the section most relevant to any issues you're experiencing. Please be sure to read about Caching first.
Before proceeding with the troubleshooting steps below or making any kind of change and then running a test, it's important to ensure you clear the cache at all levels (server, website, CDN, or browser) prior to running a test. An even better alternative is to altogether disable caching while configuring Domain Mapping System.
Some hosting companies (like WordPress.com) may not allow you to clear your cache or control caching, depending on the plan. If they don't offer the option, it's not a requirement in order to run tests, but just be sure to deactivate caching at all levels where you have access to do so.
Once you have everything working with Domain Mapping System, you can always re-enable caching, and you should not have any issues keeping caching enabled moving forward.
Please proceed through these troubleshooting steps to ensure everything is configured properly:
- 1.Check your DNS settings for both your primary domain and any mapped domains. The A Records should match exactly.
- 2.Ensure that you have configured your mapped domain as an Alias Domain or Addon Domain in your server configuration settings (cPanel, etc).
- 3.Double check your mapping settings in the Domain Mapping System plugin settings area.
If you find that your mapped domain is redirecting to your primary site domain or you are getting an insecure website warning in your browser, please attempt the following:
- 1.Clear cache at all levels, including Server, Website, CDN, and Browser, and then open the website in an incognito window to test if the issue persists.
- 2.Ensure you have SSL set up properly for all domains. Run a test by accessing your site via "http" and "https" independently in the URL bar. Sometimes the SSL certificate may not be configured properly, causing a redirect when using the secure version, and perhaps not when using the insecure version.
- 4.Attempt to rename the index.php file to see if it's causing undesired redirects.
If you find that your mapped domain is improperly displaying your primary site and your DNS settings are properly configured, it indicates a server misconfiguration:
- 1.Ensure that your domain is set up as an Alias Domain.
- 2.Ensure that your WordPress platform, all plugins, and all themes are updated to their latest versions.
- 3.Ensure there is not a second website installation for your mapped domain and delete any "extra" directories specifically set up for any mapped domains. All domains should be rooted to the primary site's WordPress installation. Be careful not to delete the primary website folder, and always ensure you have a full backup before deleting anything.
- 4.Contact your hosting company to check if the configuration settings are setup properly for your mapped Domain. Ask them: "I want to ensure that my Alias or Addon Domain is properly rooted to my primary domain website folder. Is there anything that would be preventing this from happening on my server?"
Some other causes of conflicts can be plugins, themes, or .htaccess configuration.
- 1.Reverting to the default WordPress configuration can resolve many issues.
- 1.Take a full backup of your website.
- 2.Attempt to deactivate all other plugins except Domain Mapping System and activate a default WordPress theme. If you're mapping to Products or a post type generated by another plugin, keep WooCommerce or that plugin activated.
- 4.If you've used previous versions of Domain Mapping System, select the option to "Delete plugin, data, and settings (full removal) when uninstalling." and then fully delete the plugin from your site. Install the latest free version or paid version from your Account area (this portal can be accessed using the original email address used for purchase) and set up your mapped pages again. This will ensure data stored in some previous database entries utilized by the plugin are not causing issues.
- 5.Clear your cache at all levels and check if the issue persists in an incognito window.
- 2.If the issue persists, open a support ticket by following the steps at the end of this guide.
- 3.If the issue is resolved:
- 1.Reactivate each plugin one by one, clearing the cache after each activation and running a test each time. Activate your theme and any plugins it requires at the end of the process. Following this process will indicate which plugin or theme is causing the conflict.
- 2.Open a ticket by the following the steps below and inform us about which plugin or theme is causing the conflict. We'll see what we can do to get it resolved. Usually, there are a few possible options:
- We can release a fix in our plugin, or
- Contact the other development team behind the conflicting theme or plugin to see if they can release a fix, or
- In rare situations, we can suggest another plugin or theme to use. However, this should not be necessary, and in most cases there is a workaround solution of some kind. It is our goal to reduce these conflicts with the proper code so you can use any combination of plugins and themes you want.
If the troubleshooting steps above don't resolve the issue, share the requested details below with our support team. If you're already in contact with us, feel free to reply to any existing emails with the details below - there is no need to open a new support ticket.
Open a ticket through this page if you haven't contacted us yet:
Be sure to provide the following information:
- The primary domain of your site.
- A full list of alias domains you wish to map to your site.
- Explain your goal(s) as clearly as possible. What should each mapped domain display?
- Share simple instructions on how to reproduce any issues you're experiencing on the site so our team can repeat the procedure as quickly as possible.
- To clearly indicate the issues you're experiencing, share all error messages you see, capture screenshots of the issue, or record your screen in an explanatory video. Any "visual evidence" you can provide will help us "see what you're seeing."
- If possible, in order to ensure you're capturing all possible errors, activate debugging by replacing the line of code:
define( 'WP_DEBUG', false );in your wp-config.php file with these two lines, which will display errors on the frontend of your site:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', true );
- Your hosting provider.
- WordPress Version.
- Plugin Version.
- PHP Version.
- FTP login details (required).
- If requested, provide a full backup of your site and database so we can implement it locally and run our own testing.
We cannot be held responsible for any issues resulting from sharing website access, so be sure to take a full backup of your website and database before providing any access to your site. Website access or backup data you provide is only used by our support team or development team, if necessary, to diagnose support issues. Security is our #1 priority and we do not store information anywhere outside of our ticket system. Website backups are fully deleted after resolution or closure of a ticket and all other data can be deleted immediately upon request.
By sharing all of the information above, you will allow us to determine with exact precision the cause of any issues and what can be done to resolve them.
We appreciate your patience, as these details are highly informative to resolving potentially complex issues.