The Servebolt Admin Panel comes with a few options to redirect traffic to a desired domain. Specifically we have the following redirect options available:

  1. Domain-based redirect
  2. http -> https redirect
  3. And lastly, though this is not part of Admin Panel, .htaccess  redirects

Domain-based redirect

On the individual site settings page in your Servebolt Admin Panel, you'll find a setting called Domain-based Redirect. This is a very useful setting when you want to redirect all traffic to one domain, or when you want to change the primary domain of the site. The Servebolt support team uses this setting, for instance, when we redirect from using a .no  TLD to .com  TLD, for instance.

When using the Domain-based redirect in our admin panel, the redirect rule is set in nginx, which is faster and safer than setting up the redirect with .htaccess .

http -> https redirect

The http -> https redirect feature redirects all http traffic to one specific domain name. This feature can be used in combination with the domain-based redirect feature.

Multisite configurations

When you're using a WordPress Multi-site configuration or a Magento 2 Multistore setup, you're relying on multiple URLs. Unfortunately this means you can not use the control panel feature, because it is limited to a single domain name use-case. 

To make all URLs redirect to the equivalent https address, add the following to .htaccess  right after the RewriteEngine On  line: 

RewriteCond %{REQUEST_URI} !/\.well\-known/?.*
RewriteCond %{HTTP:X-Forwarded-Proto} !=https
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Debugging redirects

  • Make sure the URL under which your application should be available at (with/without www  and/or https  versus http ), and check that the application is properly configured.
  • Check that the Servebolt Admin Panel redirect options are either empty or redirect to the desired URL.
  • Check that your .htaccess  does not contain any conflicting redirects or configurations from moved over from other servers.
  • Clear your browser cache when checking redirects. Especially Chrome can be very tenacious in caching your redirects. We recommend you trying a different browser as well when testing redirects.
Did this answer your question?