Getting 404 Error for most US based users

Hi,

This page is getting 404 error for mostly those inside US

I’ve noticed in my google analytics people within the US are getting 404 error. I am also getting 404 error. When I go on my server which is outside of US I see that the page works. It doesn’t matter if its “www” or not as well.

Thanks

US requests seem to load fine

sitemeer.com/#https://www.fanrankings.com/nfl/articles/top-10-strong-safeties-in-nfl-2021-rankings/

Can you post a screenshot?

Hi,

Either from search engine or directly going to page I will go to 404 error

When I go to server and access page it works fine no problem. This is outside US

This is from google analytics

Thanks

I’m in LA. I didn’t get a 404, but I ended up a blank content area after the header. And now it shows something.

1 Like

Yeah, it seems I can reproduce that, however it’s not only the US, but also Canada, so I’d assume it might be all of North America.

Actually, there’s no 404 in that case but rather a 302 redirect to /404?aspxerrorpath=/nfl/articles/top-10-strong-safeties-in-nfl-2021-rankings/. That does come straight from your server however and I guess you have some IP check there. I would check the log files why it sends that 302.

You either send that redirect for all North American addresses or only in the context of Cloudflare, possibly with their North American addresses. The redirect itself does not come from Cloudflare though.

2 Likes

Hi,

I only have this redirect going

<rule name=HTTPS force enabled=true stopProcessing=true>
<match url=(.*) />
<conditions>
<add input={HTTPS} pattern=^OFF$ />
</conditions>
<action type=Redirect url=https://{HTTP_HOST}{REQUEST_URI} redirectType=Permanent />
</rule>

And one page rule

fanrankings.com/*
Forwarding URL (Status Code: 301 - Permanent Redirect, Url: https://www.fanrankings.com/$1)”

I didn’t find any issue in the logs. What do you think should be next steps? I don’t understand why this page is the only one giving 302 error. I tried republishing and custom purge for this page as well

Page rules are not relevant in this context as this redirect comes from your server, as mentioned.

image

I am afraid I can’t tell you what exactly is sending that redirect, that will be primarily a job for your web developer. The log files were merely a suggestion, as they should contain that redirect.

The query string would indicate it might be an ASP error, but that would be beyond the scope of the forum here (as it’s not Cloudflare related) and best discussed in an appropriate forum.

2 Likes

Hi,

So I figured out the issue so I’m almost there. It is the forward slash at the end of the url that is causing the 302 error. If you had a 404 error page earlier you can try it without the slash here https://www.fanrankings.com/nfl/articles/top-10-strong-safeties-in-nfl-2021-rankings
I tested this out with other urls and this is the only webpage having this issue for some odd reason.

So I added this rewrite rule

                             <match url="(.*)/$" />
                             <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
                                  <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
                                  <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
                             </conditions>
                             <action type="Redirect" url="{R:1}" redirectType="Temporary" />
                        </rule>
type or paste code here

This works for all pages except

for some reason. I still get taken to 404 error page. I recycled app pool, cleared my cache, and custom purge on the page.

It doesn’t make sense to me. Can this be done in page rules? I already have one page rule. I don’t think two can work at the same time

Thanks

You can certainly try something of the sort of *fanrankings.com/*/https://www.fanrankings.com/$2. You could also try to rewrite the path

This is untested and you might need to adjust it and generally I’d really advise to rather fix this on the server, though I am not sure why your configuration issue should only fire for US requests. Apparently it does work for non-US requests.

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