Www redirecting old page

DNS & Network
#1

Hello there,

We used to use a different e-commerce system before. We updated our website and moved our hosting to a different server. We added our website with .com to the A record in dns settings. It works, but when we try to enter the website with www (although we update the new server IP with www) the old website comes up and we have a problem like this for 1 week. We do not have any other nameserver redirection from Cloudflare.
I added the Page rule but still the same problem continues.
We also moved from a cloudflare to another Cloudflare account, but the problem still persists.

Website: https://filadre.com
Problem: https://www.filadre.com

#2

Could you please share the DNS section of your Dashboard and the PageRules?
(you ofc can censor the last sectors of your IPs)

There is a 302 redirection from
www.filadre.com =( 302 )=> https://www.filadre.com/Expired.html
This redirection could (but unlikely) be made with a PageRule, or is implemented somewhere behind CloudFlare (the server with the IP which www.filadre.com points to) which is very likely.

Are you sure your Server also accepts www.filadre.com and not just filadre.com?

#3

Hi,

Firstly thank you for your reply.
Yeah we used a page rule to redirect www to the @
After deleted the rule nothing change.
I share with you the images you can check that.


#4

It looks like your site is configure to not use ‘www’.

Why did you delete the rule?

If you really want to troubleshoot this, use the “Pause Cloudflare on Site” option from the Overview page to see if both hostnames load properly.

#5

Hey there,

Looking at the request direct to the origin:

➜ curl -svo /dev/null https://www.filadre.com |& grep -i "HTTP\| location\|Trying "
*   Trying 78.40.224.xxx:443...
* ALPN, offering http/1.1
* ALPN, server accepted to use http/1.1
> GET / HTTP/1.1
< HTTP/1.1 301 Moved Permanently
< Location: https://filadre.com/

We can see that the redirect is happening there, the IP here is not a Cloudflare IP.

So while the request is accepted by the origin in the www hostname, the origin redirects to the root.

Using a special internal tool, I’ve issued requests from the edge to the origin, and there are only “good” 301s and 200s.

Could you provide screenshots of the unexpected vs expected behavior?

#6

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.