Version 3.7 of our Cloud Platform released

Posted on July 5, 2016

Today we released another update to our cloud platform. Our latest update includes additional SSL enhancements as well as back-end improvements to the way we monitor customer devices and route traffic around congestion on the Internet.

Here are the most notable changes and bug fixes in this version:


General System/Account Changes:

  • User Primary Email: We changed the validation of email addresses when creating new user profiles to ensure that the email entered is legitimate. Some users were entering known bad addresses and were then curious why it was impossible to reset their password.
  • Minimum Alerting Feature: A newly added feature in alert lists to minimize the number of messages received would completely prevent some users from receiving alerts if multiple users were on the email list and at least one of them had SMS enabled. This has now been corrected, and it properly sends to all users exactly as created.
  • MySQL Monitor: We corrected a bug in the MySQL monitor that would not let a user save a custom SQL query into a newly created monitor.
  • HTTP-CONTENT Monitor: We corrected a regression that affected the HTTP-CONTENT monitor that would not allow saving the Receive String. You can now enter the string again for the content you wish to find on the page when using this monitor type.

DNS Changes:

  • TXT record improvements: We have further enhanced how we manage very long TXT records. Users can now enter a very long text record and the back-end API will automatically break it into the necessary, RFC-compliant, 255 character chunks. If a user wishes greater control and wants to break the record up manually, then double quote marks (“”) can be utilized to pre-break the sections as desired.
  • GEO Zone Pool creation: We corrected a bug where users who had subscribed to Geo Zone capability were unable to create a new Geo Zone Pool.
  • Web Redirect Enhancement: We enhanced how web redirect records are loaded into our redirect clusters around the world to improve the speed with which they are deployed. On occasion, users would see a delay of up to 15 minutes for these to propagate. They now complete deployment within 60 seconds.
  • DNS Failover Alerts: We corrected a bug where email alerts would not be sent if a user had attached an alert list to a failover pool entry, but did not have one attached to the failover pool itself, even if the failover pool list was not being inherited or used for the list entry.
  • DNS Failover Pool Entry IP Addresses: We enhanced the IP address validation in the API when users create (or edit) servers to disallow RFC 1918 space (private, non-routable IP addresses). Many customers were entering these for testing purposes which really served no purpose other than to show a server quickly go into “down” status.

Networking Changes:

  • Server Name Indication (SNI) SSL certificate support added: We now allow you to attach multiple SSL certificates to a cloud IP using a feature of the TLS protocol called SNI. Among other things, this could now enable multiple SSL websites on a single cloud IP by simply attaching a SSL certificate for each site. This is especially handy given the cost of IPv4 addresses and will allow some of our users with dozens of sites to consolidate them.
  • IPv6 enabled servers: We improved the way IPv6 servers/devices are created and managed when used for Cloud Networking solutions. Now you can front-end IPv6 only servers with an IPv4 address/cloud IP. This will be handy as IPv4 is approaching worldwide exhaustion and some clients may only be able to obtain IPv6 enabled devices from cloud providers in the near future.
  • IPv6 Cloud IP fix: Some users would obtain an error when attempting to purchase and utilize an IPv6 address in Cloud Networking Solutions. This has been corrected now.
  • Attaching SSL when multiple server groups are used: We corrected a bug that would prevent a SSL certificate from being attached to a pack if the SSL port was utilized in the second server group and not the first.
  • Max Clients and Max Requests not clearing properly: We corrected a bug that made it difficult to clear/remove the values for ‘Max Clients’ and ‘Max Requests’ in a server. Previously, if you had a value in these fields and you wanted to clear them, you had to enter a zero (0). This has been changed to accept a zero or a blank value.
  • Adding port to existing server with disabled monitoring: We corrected a bug that would incorrectly enable monitoring if you added a new port to a server where monitoring was disabled. Now when adding a new port, the monitoring is correctly set.
  • Server Weight options: The weight select boxes in the load balancer were always visible, even though they might not be functional with some load balancing methods. We have now disabled the boxes unless one of the following approved load balancing methods are used: Least Connection, Round Robin, Least Response Time, Least Bandwidth, Least Packets. This will hopefully eliminate some confusion when it appears that the weight settings are having no effect.
  • Firewall Policy Settings: We corrected a bug whereby some customers who had multiple firewall policies would not see the correct profile in the select menu when editing existing policies, even though it was correctly applied on the back-end.