I am migrating my website from A Blue Star {page name} to https://blog.abluestar.com/ {page name}
I have both sub-domains passing thought the Cloudflare DNS
I have setup the following page rule
Matching: https://blog.abluestar.com/*/
Forwarding URL: https://blog.abluestar.com/$1
I would expect that the old URL would be redirected to the new URL. See example below.
Old URL: The Giant Claw Game! - Relay H-Bridge and Circuit Design - A Blue Star
New URL: The Giant Claw Game! - Relay H-Bridge and Circuit Design - A Blue Star
But instead I get the following error message ( ERR_NAME_NOT_RESOLVED
) when I click the old URL link.
What have I done wrong?
Thank you for your time.
I also double check to see if the Cloudflare DNS was working from external sources and it appears to be. I used https://mxtoolbox.com/ for this check
www.abluestar.com
blog.abluestar.com
sandro
March 21, 2019, 5:23am
3
That must be a DNS resolution issue on your side.
Your www
host works for me as well as on http://sitemeer.com/#https://www.abluestar.com/
I’d suggest to wait a bit more until your resolver flushes its tables and gets the updated records, after which it should work for you too.
Also, unless the first page rule really should be specific only to your blog
host you could enabled HTTPS site-wide in the SSL/TLS settings and save that one page rule.
Thank you, this worked as you described.
You are correct, Eventually the page started producing a 404 error
instead of a ERR_NAME_NOT_RESOLVED
Next problem:
I am hosting blog.ablustar.com on github pages and I have configured www.abluestar.com to be an alias of blog.abluestar.com . I incorrectly expected that the page rules would override the DNS alias.
The issue is that this request The Giant Claw Game! - Relay H-Bridge and Circuit Design - A Blue Star hits the github pages server and 404s because the domain www.abluestar.com does not exist there.
So there a way to “park” a domain with cloudfront. so that the “page rules” get a chance to run on the url?
This article says that the page rules should be running as long as the domain is proxied by Cloudflare in the DNS settings.
So why is the old url not redirecting to the new url ?
The number one reason that a Page Rule isn’t working, such as URL forwarding, is that the Page Rule you created is on a record that is not proxied by Cloudflare in your DNS settings .
Example: You have a Page Rule that redirects a subdomain (subdomain.yoursitename.com ) back to your root domain (yoursitename.com ). If you do not have that record proxied in your DNS settings for the subdomain record (orange cloud), Cloudflare’s proxy is not running over the record and a Page Rule will not work because it is going direct to your server.
https://support.cloudflare.com/hc/en-us/articles/200172356-Why-isn-t-a-Page-Rule-working-
I figured it out. I needed two page rules to resolve both issues that I was having. See screen shot below.
Issue resolved
Thank you @sandro for your help
1 Like
system
Closed
April 4, 2019, 4:50am
7
This topic was automatically closed after 14 days. New replies are no longer allowed.