English

Migration of Load Balancers and Domains

As mentioned in our changelogs, the migration of load balancers and domains introduces significant improvements to the way these configurations are managed in smoxy.

To streamline smoxy's infrastructure and reduce duplication, we have migrated load balancers and domains to new, centralized locations. While this migration ensures continued functionality of your configurations, it has introduced some changes that you should be aware of. Below, we’ll explain what changed, how the migration was handled, and steps you can take to review and clean up your configuration if needed.

Load Balancer Migration

What Changed?

Previously, load balancers were configured at the site level, making it necessary to define them for each site individually. This has now been centralized, and load balancer configurations have moved to a new account-level load balancer management page. This change reduces duplication and allows you to use the same load balancer across multiple sites or rules.

Migration Details

The migration process involved the following steps:

  1. Copying Load Balancers: All existing load balancers were copied to the new load balancer management page.

    • If a load balancer with the same name already existed, the migrated load balancer received a numbered suffix (e.g., LB (1), LB (2), etc.) to ensure no conflicts.

  2. Creating Origins: Every member (server) that was previously assigned to a load balancer was converted into a standalone origin.

    • The configurations of these origins match the server details, including protocol, IP address, and port.

    • The name of each new origin is a combination of these values (e.g., https_192.168.0.1_443).

  3. Seamless Transition: Load balancers and origins were linked appropriately to ensure no disruption to your existing setups.

Cleaning Up Your Load Balancers and Origins

The migration may result in duplicate load balancers and origins depending on how your configurations were previously set up. To tidy up:

  1. Review the new Load Balancer Management Page and identify duplicates.

  2. Consolidate configurations by updating Page Rules and Conditional Rules to use a single, dedicated load balancer where applicable.

  3. Once all rules point to the correct load balancer, delete the duplicates safely.

We understand this process might seem intimidating for complex setups. Our team is here to assist with cleaning up configurations, and we’re proactively supporting accounts after deployment to ensure everything is streamlined.

Domain Migration

What Changed?

Previously, domains were assigned directly to sites, which occasionally led to misuse of domains and hostnames. To align with proper domain and SSL certificate handling, we’ve introduced a clearer distinction:

  • Domains: Represent root domains (e.g., example.com) and are used for wildcard SSL certificate generation.

  • Hostnames: Represent specific subdomains or site-related entries (e.g., www.example.com, api.example.com) and are now assigned to sites.

Migration Details

The migration process for domains included:

  1. Copying Domains: All domains previously assigned to sites were moved to the new Domain Management Page, even if they were not root domains.

    • This approach ensures SSL certificate generation remains functional without any manual intervention.

  2. Creating Hostnames: For every domain assigned to a site, a corresponding hostname was automatically created and linked to the site. This guarantees that the functionality of your smoxy configurations remains unaffected.

Cleaning Up Your Domains

The migration may result in unnecessary entries in your domain list due to the 1:1 copying process. Here’s how you can review and clean up:

  1. Identify domains in the Domain Management Page that are not actual root domains.

  2. Consolidate configurations by verifying and updating hostnames linked to sites.

  3. Remove redundant domain entries if they are no longer needed.

Post-Migration Support

We recognize that the migration, while necessary for long-term improvements, can create some initial confusion or clutter in your configuration. To simplify this process, our team is ready to assist you with:

  • Reviewing your configuration for duplicates.

  • Consolidating load balancers, origins, domains, and hostnames.

  • Ensuring your rules and site configurations point to the correct targets.

This proactive support aims to help every smoxy account maintain an optimized and clean setup post-migration. If you have any questions or concerns, feel free to reach out to our team for dedicated assistance.

Last updated