# Broken URLs in emails after domain change mautic.com to mautic.net

**URL:** <https://forum.mautic.org/t/broken-urls-in-emails-after-domain-change-mautic-com-to-mautic-net/6185>\
**Category:** Product Support\
**Created:** [October 11, 2016, 11:01am UTC](https://forum.mautic.org/t/broken-urls-in-emails-after-domain-change-mautic-com-to-mautic-net/6185 "2016-10-11T11:01:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rth](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@rth](https://forum.mautic.org/u/rth)\
**Post date:** [October 11, 2016, 11:01am UTC](https://forum.mautic.org/t/broken-urls-in-emails-after-domain-change-mautic-com-to-mautic-net/6185/1 "2016-10-11T11:01:23Z")

</div>

We are using the version of Mautic hosted at [mautic.net](http://mautic.net) with a custom subdomain, and had some issues with broken URL links in the outgoing emails, since the domain name change from [mautic.com](http://mautic.com) to [mautic.net](http://mautic.net). I am aware of the migration procedure,

Quote:

On September 23rd, at 10am EST, we will shutdown our .com IP address (107.178.241.138).  
  
So what does this mean? This means that wherever you reference ‘mautic.com’, you will need to change to reference ‘mautic.net’. That includes changes to the following:  
  
Tracking Pixels  
Landing Pages  
Forms  
  
In addition to the locations above, all references related to subdomains will need to change as well; from [subdomain].mautic.com to [subdomain].mautic.net.  
  
Also, if you're using a custom domain, please update either the CNAME record to mautic.net, or A record to 104.197.196.164 to prevent a disruption of service.

and have performed the steps above, however we are still getting 404 URL not found issues.  
  
Essentially, the situation is the following, when some link is entered in an outgoing newsletter, mautic encodes it with a custom domain `mautic.company-domain.com`, now this used to have a CNAME pointing at mautic.com, then it stopped working despite the CNAME change to mautic.net (as suggested above).  
  
In other words, outgoing email with links of the form, http://mautic.company-domain.com/  
return 404 not found error. This is not an DNS configuration issue on our end, since, even directly entering http://mautic.net/ or the required IP http://104.197.196.164/ , still produces a 404 error. The only thing that works is manually entering http://subdomain.mautic.net/ (which also resolves to 104.197.196.164) while redirecting mautic.company-domain.com to subdomain.mautic.net still fails. A more concrete example can be found here http://pastebin.com/xGYBLPRm  
  
This might be related to the "Custom domains not working issue" from 10 days ago https://status.mautic.com/incident/25 (which is now marked as resolved). Any help would be much appreciated! Thanks!

---

<div class="post-metadata">

**Author:** ![rth](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@rth](https://forum.mautic.org/u/rth)\
**Post date:** [October 11, 2016, 11:01am UTC](https://forum.mautic.org/t/broken-urls-in-emails-after-domain-change-mautic-com-to-mautic-net/6185/2 "2016-10-11T11:01:23Z")

</div>

We are using the version of Mautic hosted at [mautic.net](http://mautic.net) with a custom subdomain, and had some issues with broken URL links in the outgoing emails, since the domain name change from [mautic.com](http://mautic.com) to [mautic.net](http://mautic.net). I am aware of the migration procedure,

[quote] On September 23rd, at 10am EST, we will shutdown our .com IP address (107.178.241.138).

So what does this mean? This means that wherever you reference ‘[mautic.com](http://mautic.com)’, you will need to change to reference ‘[mautic.net](http://mautic.net)’. That includes changes to the following:

```
Tracking Pixels
Landing Pages
Forms

```

In addition to the locations above, all references related to subdomains will need to change as well; from [subdomain].mautic.com to [subdomain].mautic.net.

Also, if you’re using a custom domain, please update either the CNAME record to [mautic.net](http://mautic.net), or A record to 104.197.196.164 to prevent a disruption of service. [/quote]  
and have performed the steps above, however we are still getting 404 URL not found issues.

Essentially, the situation is the following, when some link is entered in an outgoing newsletter, mautic encodes it with a custom domain `mautic.company-domain.com`, now this used to have a CNAME pointing at [mautic.com](http://mautic.com), then it stopped working despite the CNAME change to [mautic.net](http://mautic.net) (as suggested above).

In other words, outgoing email with links of the form, [http://mautic.company-domain.com/](http://mautic.company-domain.com/)\<encoded\_url\>  
return 404 not found error. This is not an DNS configuration issue on our end, since, even directly entering [http://mautic.net/](http://mautic.net/)\<encoded\_url\> or the required IP [http://104.197.196.164/](http://104.197.196.164/)\<encoded\_url\> , still produces a 404 error. The only thing that works is manually entering [http://subdomain.mautic.net/](http://subdomain.mautic.net/)\<encoded\_url\> (which also resolves to 104.197.196.164) while redirecting [mautic.company-domain.com](http://mautic.company-domain.com) to [subdomain.mautic.net](http://subdomain.mautic.net) still fails. A more concrete example can be found here [http://pastebin.com/xGYBLPRm](http://pastebin.com/xGYBLPRm)

This might be related to the “Custom domains not working issue” from 10 days ago [https://status.mautic.com/incident/25](https://status.mautic.com/incident/25) (which is now marked as resolved). Any help would be much appreciated! Thanks!

---

<div class="post-metadata">

**Author:** ![ninjoan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ninjoan/32/1005_2.png) [@ninjoan](https://forum.mautic.org/u/ninjoan)\
**Post date:** [October 11, 2016, 12:08pm UTC](https://forum.mautic.org/t/broken-urls-in-emails-after-domain-change-mautic-com-to-mautic-net/6185/3 "2016-10-11T12:08:07Z")

</div>

@rth use the Help button in your instance since you are using Mautic Cloud PRO
