The incident related to SSL provisioning for new domains in Unbounce is now resolved. Any new domains added into Unbounce will have SSL certificates provisioned normally as expected with no additional delays.
We apologize for any inconvenience caused by this issue. If any domains still do not have SSL enabled after being added into Unbounce please contact our support team at support@unbounce.com for assistance.
Posted Jan 22, 2018 - 11:08 PST
Update
We have now provisioned SSL certificates for all outstanding new domains delayed by this issue. Going forward SSL certificates should provision for new domains without any unexpected delay.
For new domains that have failed or still say SSL enabling after 15 minutes, these should resolve themselves by early next week. Alternatively, new domains without any associated pages can be removed and re-added to restart the SSL provisioning process.
We will continue to monitor SSL provisioning until we are confident this issue can be closed. Subscribe to this status page to receive notifications on updates as they are made available.
Posted Jan 19, 2018 - 16:19 PST
Monitoring
Our development team has deployed a fix to re-enable provisioning of SSL certificates for new domains. New SSL certificates have now started issuing to any domains waiting to be enabled.
Please note that there will still be a delay in provisioning as we work through the queue of outstanding domains. We expect to have cleared the backlog of domains within 5 days, at which point there will no longer be an unexpected delay in provisioning. Any newly connected domains will continue to function as non-encrypted HTTP pages before an SSL certificate is provisioned. We will continue to monitor this situation and update this space when SSL provisioning has returned to normal.
Thank you for your patience as we worked toward resolving this issue. Subscribe to this status page to receive notifications on updates as they are made available.
Posted Jan 17, 2018 - 12:55 PST
Investigating
Unbounce's SSL provisioner (Globalsign) has temporarily disabled all certificate provisioning on new custom domains due to a recently discovered vulnerability on January 11 at 9AM PST. This means that HTTPS pages on new domains created since then are unavailable.
Users may continue to create new domains and publish non-encrypted HTTP pages without an SSL certificate. In doing so, please be aware that any connections and sensitive information to your pages will not be SSL secured. Once this issue has been addressed, outstanding certificates will be provisioned and no customer action will be required.
Thank you for your patience as we work toward resolving this as soon as possible. Subscribe to this status page to receive notifications on updates as they are made available.