Updated: 15 November 2026 · Applies to: DirectAdmin (Evolution skin), Apache 2.4

To remove a redirect in DirectAdmin, open Site Redirection, tick the redirect and click Delete. The address then shows its own content again. If the page still jumps somewhere else afterwards, the redirect is coming from another place (your browser's cache, a .htaccess rule, the domain's force redirect setting or your website's own code), and the checks below find it.

Steps

  1. Log in to DirectAdmin (usually https://your-server:2222; the address is in your welcome email).
  2. Open Site Redirection (in the Evolution skin it is usually under Account Manager; you can also type its name in the menu search box). If you have several domains, select the right one.
  3. Find the redirect in the list. Each entry shows the local path (for example /old) and where it sends visitors.
  4. Tick it and click Delete.

Where DirectAdmin keeps these redirects

According to DirectAdmin, Site Redirection writes its rules into the .htaccess file of the domain's public_html folder, and deleting the entry removes the rule again. A rule of this kind looks like this:

Redirect 301 /old https://www.example.com/new

The number is the redirect type you chose when you created it: 301 (permanent), 302 (temporary, the default) or 303.

Check the redirect is really gone

Browsers remember permanent (301) redirects, so a normal browser window can keep sending you to the old target after the rule is removed. Test in a private window, or ask the server directly with curl, which never uses the browser's cache:

curl -sI https://www.example.com/old/

In a lab test on Apache 2.4.69 with a rule like the one above, the request answered like this while the redirect was active (lab example, not a Ucartz server):

HTTP/1.1 301 Moved Permanently
Server: Apache/2.4.69 (Debian)
Location: https://www.example.com/new

After the rule was removed, the same request returned the page itself:

HTTP/1.1 200 OK
Server: Apache/2.4.69 (Debian)

If you still see a 301 or 302 with a Location line, the redirect is set somewhere else.

If the redirect is still there

  • A manual rule in .htaccess: open public_html/.htaccess in File Manager and look for Redirect, RedirectMatch or RewriteRule lines with R=301 or R=302. Plugins and earlier edits often add these. Save a copy of the file before you change it.
  • Force Redirect for www or HTTPS: according to DirectAdmin, Domain Setup › your domain has its own Force Redirect option (www or non-www) and a Force SSL with https redirect checkbox. These do not appear in Site Redirection. Change them there if they are the cause.
  • A redirect domain pointer: if a whole second domain jumps to your main site, it is a domain pointer, not a site redirect. See How to Remove a Domain Pointer in DirectAdmin.
  • Your application: WordPress and other CMSs redirect to the address saved in their own settings (in WordPress, the Site Address). Check there if only one site keeps redirecting.

To create a new redirect later, see How to Redirect Your Website Using DirectAdmin. For writing redirect rules by hand, see How to Set Up a Permanent (301) Redirect in Apache.

Official documentation: DirectAdmin, VirtualHost level help and redirect type option.

Related services

Server management

on-demand administration, hardening, migrations and monitoring.

KVM VPS hosting

NVMe SSD and full root access, with Free Basic Managed Support.

Was this answer helpful?

Still stuck? Open a ticket