Subset of Canadian customers cannot Sync classic .NET sites

Update timeline

1. resolved Jun 30, 2021, 01:21 PM UTC

   A recent security update has brought to light some misconfigured, Canadian classic .NET websites which were incorrectly connecting to the USA region content server. A configuration change is required to the web.config/appSettings.json to use contentserver-ca.agilitycms.com rather than contentserver1503.agilitycms.com

2. postmortem Jun 30, 2021, 01:22 PM UTC

   ## Incident After a security update was applied on June 17th, we received some reports from a subset of our Canadian customers that they could not synchronize content to their websites via our classic .NET integration. ## Cause A networking security update was applied to our environment which enforced rules that applications in our US datacenter could no longer communicate with databases in our Canadian datacenter. ## The Fix If you are experiencing any sync failures since June 17th and you are using a classic .NET integration, check your `web.config` or `appSettings.json` and ensure that the `contentServerUrl` is set to `https://contentserver-ca.agilitycms.com`. ## Outcome We were able to identify all customers who needed to update their settings in their website and have reached out to them and confirmed then have switched over. In the future, we will schedule maintenance windows \(through this Status Page\) and ask customers to subscribe to updates so they are aware ahead of time \(at least 1 week\) of any major changes in our platform that may require them to take action.