Lewati ke konten utama
    My redirect is not working, what should I do?
    If your GA.NU subdomain redirect isn’t working, check your configuration, DNS and nameservers, and test the HTTP status with curl. This guide walks you through quick checks, deeper troubleshooting, and examples to resolve common redirect problems.
    redirectstroubleshootingdns

    My redirect is not working, what should I do?

    A redirect that doesn't behave the way you expect is usually caused by configuration, DNS, certificate, or caching issues. This guide walks you through quick checks, deeper troubleshooting, and practical examples to get your GA.NU (.ga.nu subdomain) redirect working.

    Quick checks

    Before diving in, verify these basics:

    • The target URL is correct and reachable (visit it directly in your browser).
    • You selected the intended redirect type (301 permanent vs 302 temporary).
    • You’re testing the exact hostname you configured (e.g., yourname.ga.nu vs www.yourname.ga.nu).
    • You’ve waited for propagation (DNS and certificates can take time; see timing section below).
    • Your browser or CDN cache isn’t serving old responses (try an incognito window and clear caches).

    Step-by-step troubleshooting

    1) Confirm your GA.NU redirect settings

    Open your GA.NU dashboard and review your subdomain’s Redirect settings:

    • Source subdomain: Ensure you’re editing the correct host (e.g., yourname.ga.nu).
    • Destination URL: Use the full URL with scheme, e.g., https://example.com.
    • Redirect type: Choose 301 for permanent, 302 for temporary.
    • Path and query forwarding: If you need yourname.ga.nu/blog?id=42 to end up at https://example.com/blog?id=42, enable path/query forwarding.
    • Additional hosts: If you also want www.yourname.ga.nu to redirect, add a separate redirect for that hostname.

    Common misconfigurations:

    • Using http://example.com when the destination only supports HTTPS.
    • Forgetting to include path forwarding, so all requests land on the destination homepage.
    • Typos or missing trailing slashes causing unexpected paths.

    2) Check nameservers and DNS

    If your nameservers do not point to GA.NU or you created conflicting DNS records, GA.NU’s redirect feature may not apply to your host.

    • If you changed nameservers to a third-party (e.g., a CDN or hosting provider), verify that your redirect is configured there instead.
    • Remove conflicting records for the same hostname (e.g., an A or CNAME pointing to a different service while also enabling GA.NU redirect).

    You can check DNS from your terminal:

    # Replace with your subdomain
nslookup -type=NS ga.nu

# See what your host resolves to
dig +short yourname.ga.nu

# Inspect record type
dig +noall +answer yourname.ga.nu

    If you see the hostname resolving to a third-party IP or CNAME, the redirect may be controlled outside GA.NU.

    3) Inspect HTTP status with curl

    Use curl to see whether you’re getting a redirect and where it points:

    # Follow redirects and show headers only
curl -I -L https://yourname.ga.nu

    What to look for:

    • A 301 or 302 response from yourname.ga.nu that includes a Location: header with your destination.
    • The final response (after -L) should be from your destination domain (likely 200 OK).

    Example output:

    HTTP/2 301 
location: https://example.com/
...
HTTP/2 200 
...

    If you see 200 OK on yourname.ga.nu without any redirect, the redirect is not applied. If you see 404 or 403 on the destination, the redirect worked, but the destination returned an error—fix the destination.

    4) Resolve HTTPS and certificate issues

    Browsers may block or warn if:

    • The certificate for yourname.ga.nu is missing or invalid.
    • You’re redirecting from HTTP to HTTPS but the destination has certificate or TLS issues.

    Actions:

    • If you require HTTPS, ensure the source and destination have valid certificates.
    • Do not force HTTPS until certificates are ready.
    • If you changed providers recently, allow time for certificate issuance and renewal.

    5) Clear caches and avoid loops

    • Browser cache: Test in a private/incognito window or clear cache.
    • CDN/Proxy cache: Purge page rules or caches if your domain is proxied through a CDN.
    • Redirect loops: Ensure the destination does not redirect back to the source (A → B → A). Use curl -I -L to detect repeated hops or errors like “too many redirects.”

    6) Wildcards, path forwarding, and host variants

    • If you need all paths to move, enable path forwarding (e.g., /blog/post-1 → /blog/post-1).
    • If the destination expects or rejects trailing slashes, be consistent (e.g., redirect to https://example.com/ rather than https://example.com).
    • If users visit www.yourname.ga.nu but you only configured yourname.ga.nu, add a redirect rule for www.yourname.ga.nu as well.

    7) Propagation and timing

    • DNS changes typically propagate within minutes but can take up to 24–48 hours globally, depending on TTLs and resolvers.
    • SSL/TLS certificates, if auto-issued, may take several minutes to become active.

    During this window, behavior can be inconsistent across networks.

    Practical examples

    Example 1: Move all traffic to a new site

    Goal: Redirect everything from yourname.ga.nu to https://example.com.

    • Source: yourname.ga.nu
    • Destination: https://example.com
    • Type: 301 Permanent
    • Path/query forwarding: Off (all traffic goes to the homepage of example.com)

    Test:

    curl -I -L https://yourname.ga.nu
# Expect: 301 to https://example.com/, final 200 OK from example.com

    Example 2: Preserve paths and queries

    Goal: Redirect yourname.ga.nu/blog?id=42 to https://example.com/blog?id=42.

    • Source: yourname.ga.nu
    • Destination: https://example.com
    • Type: 302 Temporary (use 301 if permanent)
    • Path/query forwarding: On

    Test:

    curl -I -L 'https://yourname.ga.nu/blog?id=42'
# Expect: 302 to https://example.com/blog?id=42

    Example 3: Include www variant

    Goal: Redirect both yourname.ga.nu and www.yourname.ga.nu.

    • Create redirect rule for yourname.ga.nu → https://example.com
    • Create redirect rule for www.yourname.ga.nu → https://example.com

    Test:

    curl -I -L https://www.yourname.ga.nu
# Expect: 301/302 to https://example.com/

    Common causes and fixes

    • Nameservers changed: If you point nameservers away from GA.NU, configure redirects at the new provider instead, or switch back to GA.NU.
    • Conflicting DNS records: Remove A/CNAME records that conflict with redirect rules.
    • Destination errors: The redirect works, but the destination returns 404/403—fix routing or content at the destination.
    • HTTPS mismatch: Destination forces HTTPS without a valid certificate—fix certificate or remove HTTPS forcing temporarily.
    • Cloaked/iframe redirects blocked: Modern sites use security headers (CSP, X-Frame-Options) that break “masked” redirects—use standard 301/302 instead.

    What to include when contacting support

    If you still need help, share:

    • The source hostname (e.g., yourname.ga.nu) and the exact destination URL.
    • A description of current behavior vs. expected behavior.
    • Recent changes (DNS, nameservers, CDN, SSL).
    • Output of:
    curl -I -L https://yourname.ga.nu

dig +noall +answer yourname.ga.nu

    These details help us identify whether the issue is in configuration, DNS, or the destination.

    FAQ

    • 301 vs 302: Use 301 for permanent moves (SEO-friendly). Use 302 when the change is temporary.
    • How long does it take? DNS and certificates can take minutes to hours. Test periodically and allow up to 24–48 hours for global DNS propagation.
    • Do I need www? Only if you expect traffic to www.yourname.ga.nu. Add it as a separate redirect if needed.

    If you’ve followed this guide and the redirect still doesn’t work, contact GA.NU Support with the details in the “What to include” section. We’re happy to help.

    My redirect is not working, what should I do? | GA.NU