How to create a website redirect and prevent redirect loops

A redirect sends a browser from one URL to another. Use it when you move a page, change a site's preferred hostname, or enforce HTTPS after the certificate works. DNS changes alone do not redirect a browser to a different URL.

Redirect management remains in Virtualmin or the application. From the Control Center, open Control panel access → Hosting login, sign in, and select the source domain. Adding a DNS record in DNS & SSL does not create a redirect rule.

Add a redirect in Virtualmin #

1. Select the domain that visitors will arrive at first.
2. Open Web Configuration → Website Redirects, then Add a new website redirect, if available.
3. Enter the source path, such as /old-page, and the intended destination URL.
4. Review how the rule treats subdirectories. Decide whether /old-page/item should keep a corresponding path or go to one fixed destination.
5. Choose the HTTP redirect type offered by your form. A temporary redirect suits a test or temporary move; use a permanent redirect after confirming a permanent change.
6. Review whether the rule applies to HTTP, HTTPS, or both, then save. Virtualmin redirect guide

For HTTP-to-HTTPS redirects, first verify that the HTTPS destination has a valid certificate and works without a redirect. An HTTPS request needs a valid connection to the source hostname before the browser can receive its redirect.

Test the complete behavior #

Test the source URL in a private browser window, a nested path, and an unrelated page. Inspect the browser's network panel when you need to confirm the status code or redirect sequence. Check query parameters when forms or tracking links rely on them.

Keep a record of the original rule so you can undo the change. Permanent redirects can remain cached, which can make a corrected rule appear unchanged on your device. HTTP redirect semantics

Troubleshooting #

For “too many redirects,” check for opposing rules across Virtualmin, the application, .htaccess, and any proxy or CDN. A common conflict sends the visitor to HTTPS in one layer and back to HTTP in another.

For the wrong destination path, review the subdirectory behavior. For an unchanging result, check browser and CDN caches after inspecting the saved rule. Do not stack more redirects onto a loop; disable the last change and identify the conflicting layer.

Related: aliases and additional names, caching.