That’s an interesting tidbit. I wonder if the @MVP group has heard this. Usually we only hear about any connection that goes to the old site. That it only happens with HTTPS enabled is a twist I hadn’t heard of, but it makes some sense.
It’s usually tied to a SSL for SaaS feature where a host would add a client’s domain to the host’s Cloudflare configuration so the client could get SSL. At this point, see if they can ask the old host to completely remove the domain from their system, including any Cloudflare integration.
If that doesn’t work out, please email [email protected] with the subject Cannot remove custom host name and details of the issue. Once you’ve done that you’ll receive an automatic response with a ticket number. Please post that here so we can escalate it. Once you have reached out to Support they will ask you to verify domain ownership of the domain by adding a txt record to the domain in order to verify domain ownership.
I lost track of that bit and was thinking of an old host. An old account shouldn’t affect anything if the domain is activated on a new account. It’s the recommended approach for people who lost access to their old account.
connection that goes to the old site. That it only happens with HTTPS enabled is a twist I hadn’t heard of, but it makes some sense.