Redirect Rule for All Incoming Requests partially working, but not for https://www

General Rules
1

What is the name of the domain?

connormckee.art

What is the error message?

This site can’t be reachedCheck if there is a typo in www.connormckee.art. DNS_PROBE_FINISHED_NXDOMAIN

What is the issue you’re encountering

I setup a Redirect Rule for all incoming requests to my domain. I have tested that Redirect Rule in six patterns. Five are getting redirected correctly, but the sixth (https://www.*) is not.

What steps have you taken to resolve the issue?

Tested six patterns:

connormckee.art
www.connormckee.art
both of the above with http://
both of the above with https://

Confirmed the first 5 Redirect as expected but #6 (https://www.connormckee.art) fails.

Checked my rules to confirm only one Rule exists. In cloudflare this one Redirect Rule is my only Rule of any type.

Checked in GoDaddy (from whom I bought the domain) to confirm no other forwarding setting were enabled. None were.

What are the steps to reproduce the issue?

Navigate to https://www.connormckee.art and observe the error compared to the other paths, such as just connormckee.art

2

That one is working for me at this time:

% curl -svo /dev/null https://www.connormckee.art 2>&1 | egrep "< |> "
> GET / HTTP/2
> Host: www.connormckee.art
> User-Agent: curl/8.6.0
> Accept: */*
> 
< HTTP/2 301 
< date: Sun, 30 Jun 2024 21:59:13 GMT
< content-type: text/html
< content-length: 167
< location: https://connormckeeart.etsy.com
< cache-control: max-age=3600
< expires: Sun, 30 Jun 2024 22:59:13 GMT
< report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=TYGov3sYKIfETIT14QrxrBiiNpcx%2BTchD9fsq6pGG0K5WoRvhUoh7u979fRXnQb7yjWXGDtx1Ns6roo9egYhM1wEZoX9MFNXo8vhcGZiQbbBsQB9PN4ZLreoBv6dWOtEWRHdAezcqfSahF945iRXyMsf"}],"group":"cf-nel","max_age":604800}
< nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
< server: cloudflare
< cf-ray: 89c16c13ad5c2f7a-LAX
1 Like
3

Well damn, I don’t know if I was just impatient or something else, but yes, it does appear to be working now. Thank you for the quick response!

2 Likes
4

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