Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Aug 15, 2017 - 21:01 BST
Scheduled
Note that this is a brownout - which means we'll make the change, then reverse it at 8am the day after. This gives you the breathing space to fix any problems before the change goes live permanently.
** What is happening? **
For those customers who access FLG using the flg360.co.uk domain name (for example hostname.flg360.co.uk), we'll start redirecting connections from http://hostname.flg360.co.uk (insecure) to https://hostname.flg360.co.uk (secure).
** Why are you doing this? **
Because of advances in technology and security practices, it's now the norm for services like FLG to be accessible over HTTPS (secure connections) only. This means that all traffic between the user and our servers will always be encrypted and secure.
You can already use FLG over a secure connection, it's just that we'll be making this mandatory.
** Will it affect me? **
This change will apply to both users accessing the user interface, and requests to the API. It's unlikely to cause issues for users, as they will be silently redirected and proceed as normal over a secure connection.
Our API will also attempt to redirect traffic, but the redirect is likely to cause an error in most cases. The next section explains how to fix this.
Custom domain names pointing to the service via a CNAME are unaffected by this change and will continue to work over both HTTP and HTTPS.
** What do I need to do? **
If you're making API calls through the flg360.co.uk domain name, make sure the URL starts with https:// and not http://. You'll need to make this change before Tuesday 15th August.
If you are using the flg360.com domain name, please contact us so we can arrange to swap it.
** Where might I be using FLG domain names? **
There are various places where you might find requests to FLG domain names that need switching over to HTTPS:
- From your website (including Web Form, iFrame and API integration methods) and other systems that post into FLG.
In partner deliveries where you send leads to other FLG users.
- In requests to the FLG API within code you've written for your plugins or webhooks.
So it's important that you audit your systems carefully, and also note that this affects requests to your own FLG account as well as any other FLG accounts you make requests to.
** When will the change happen? **
We're currently scheduling the change to happen on Tuesday 15th August at 9pm.