Moving Sendy to subdomain

patrickmau

Referring to this article:
https://sendy.co/forum/discussion/4710/how-to-migrate-sendy-to-another-server#Item_2&gsc.tab=0

I am trying to migrate Sendy from https://domain.com/sendy/ to https://edm.domain.com/ but am not getting the desired result despite following the instructions in the above article.

Problem:

• despite making the advised changed, once I open a tab with https://edm.domain.com I get redirected to the previous https://domain.com/sendy/ address

Steps taken:

• verified subdomain DocumentRoot is correct
• ensured /includes/config.php is updated
• tried to reset the cron but cannot do so on the new address due to the above
• tested by placing a "hello world" index.php into the root of https://domain.com/sendy and can confirm that despite all relevant files being present in https://edm.domain.com/, I am still getting redirected. This suggests there is some sort of validation happening on an app-level I am not aware of

Version: 6.1.0
Hosted on: AWS Lightsail
Email service: Sendgrid
Server: Ubuntu 24.04 LTS

Could it possibly be that I have to announce a domain change to Sendy even though its just a subdomain?

Thank you,
A2k

Ben

Hi,

This redirection behavior is usually caused by hardcoded references to the old URL inside one or both of the following:

1. Sendy’s config.php

You said you’ve updated this, but double-check this block inside includes/config.php:

// Make sure this is the correct new subdomain
define('APP_PATH', 'https://edm.domain.com');

Even a trailing slash or missing HTTPS can affect it.

NO trailing slash — it should not be https://edm.domain.com/

Correct:

define('APP_PATH', 'https://edm.domain.com');

2. .htaccess Redirects (Apache only)

Check if your original install or server config added any redirects:

In both:

• https://domain.com/sendy/.htaccess
• https://edm.domain.com/.htaccess (or Apache virtual host config)

Look for lines like:

Redirect 301 /sendy https://domain.com/sendy

Or conditional redirects using mod_rewrite.

Remove any hardcoded redirect rules pointing back to the old URL.

3. Browser or CDN cache

Sometimes after migration:

• Your browser might cache a 301 redirect.
• A CDN like Cloudflare could be caching redirects.

Test in:

• Incognito window
• curl -I https://edm.domain.com (to inspect response headers for redirects)
• Try disabling any CDN temporarily

Thanks.

Best regards,
Ben