Remove a redirect when its source URL should serve content again or when the previous destination is no longer correct. The redirect may exist in more than one layer, so first identify the rule that DirectAdmin actually manages.
IN THIS ARTICLE
Prepare for the change
Record the source path, destination and status before deletion. Confirm there is suitable content at the source or an approved replacement rule. Keep a copy of relevant application or web-server configuration if you expect to adjust it separately.
01 Remove a website redirect in DirectAdmin
- Select the intended domain and open Account Manager > Site Redirection.
- Find the rule by its local path and destination. Check whether it affects one page or the whole site.
- Select only the obsolete rule and choose Delete. Read the confirmation before accepting.
- Refresh the redirect list and verify that the intended entry has gone.
- Test the source URL from a new client or an HTTP-header request. Check HTTP, HTTPS and any www variant relevant to the original rule. Review important inner pages if the rule affected the site root.
How do I confirm the old redirect is gone?
The source should now serve its intended content or replacement behavior without the removed redirect. Verify that unrelated site redirects still work and that the source has a valid HTTPS certificate.
If the change does not work
If the old destination still appears, a browser may have cached a permanent redirect. Test independently, then inspect application settings, CDN rules and other server redirects. Do not delete unrelated rewrite configuration just because the panel list is empty. Recreate the recorded rule if it was removed by mistake and verify the resulting behavior again.