Followup to bug 1296375: Please CNAME 'www.mozilla-campaigns.org' to 'unbouncepages.com'.
CNAME created, but FYI the site does not appear to work via the CNAME.
Status: NEW → ASSIGNED
I logged into unbounce to see if there was any configuration required from the app, and it gave me the following message: " The most common reason for this is that your host is just taking a while to update your new CNAME. Assuming your CNAME is setup correctly (see point 2 below), give it a couple of hours and it should start working. Double-check that your CNAME is pointing to unbouncepages.com and triple-check for any spelling mistakes. If your CNAME looks right, and you have waited a couple of hours for it to update, please email support and include a screenshot of your host's CNAME control panel so that we can get you up and running as quickly as possible. "
From bug 1296375 when we did this for campaigns.mozilla.com, it took about 24 hours to get everything working after the CNAME change. As soon as Unbounce recognizes the config change, they will start generating the SSL certificate and will automatically turn on SSL once it is ready.
FWIW, I still see "The requested URL / was not found on this server." when I hit www.mozilla-campaigns.org
(In reply to Eric Ziegenhorn :ericz from comment #4) > FWIW, I still see "The requested URL / was not found on this server." when I > hit www.mozilla-campaigns.org I don't know if that in itself is a problem -- we may not have published any pages here yet. Porfirio, can you login in to Unbounce and let us know what the custom domain status page says? If everything worked, SSL should be active by now and we can publish a test page to try it out.
I published a test page and it appears to be working: http://www.mozilla-campaigns.org/project-magnet-at-view-source/ The current status in the control panel is "Enabling SSL", so not sure how/when this happens, but it seems to be working otherwise.
Great, let me know if you need anything else then!
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.