Chrome and 500 errors (weird)

Status
Not open for further replies.
Joined
Mar 16, 2025
Messages
112
Reaction score
95
Weird situation here.

One of my sites loads perfectly with firefox, opera, etc.
But when someone using Chrome clicks a link... They get a 500 error.

What happens is the URL gets screwed up.
So the URL is supposed to be https :// site .com /pods but in chrome it becomes https :// site .com /main/pods

This problem is driving me crazy
 
Check your .htaccess (Apache) or nginx.conf (Nginx) or cloudflare (page rules) for any redirects forcing /main/ on certain conditions?
It could also be cache related aswell?
are you testing on chrome without any plugins/addons?
 
Check the software's component to see if it can detect phishing
 
Check your .htaccess (Apache) or nginx.conf (Nginx) or cloudflare (page rules) for any redirects forcing /main/ on certain conditions?
It could also be cache related aswell?
are you testing on chrome without any plugins/addons?

All checked and everything works.

I'm wondering if the problem is the site map for SEO. I started getting complaints when I did some SEO work.
 
All checked and everything works.

I'm wondering if the problem is the site map for SEO. I started getting complaints when I did some SEO work.
This is a technical problem, it has nothing to do with the sitemap URL(s),
Most probably due to the browser cache, as it's using/rendering an older redirect that no longer exists,
Double check if the same occurs in Chrome incognito mode, if not, clear the browser (or website's) cache
 
This is a technical problem, it has nothing to do with the sitemap URL(s),
Most probably due to the browser cache, as it's using/rendering an older redirect that no longer exists,
Double check if the same occurs in Chrome incognito mode, if not, clear the browser (or website's) cache

The 1st thing I did was clear cache, disable plugins, etc... etc...
The 2nd thing I did was use different devices to test the problem.
The 3rd thing I did was ask friends and a family member to test it on their devices.

All.. The ... Same.. Result....

The ONLY thing that's changed is that apx. 24hrs ago I updated my SEO and that's when the problem started. Logically it's got to be something related to that. Chrome is built by google and it's the only browser having this problem.

So, what other conclusions can I come to?
 
The 1st thing I did was clear cache, disable plugins, etc... etc...
The 2nd thing I did was use different devices to test the problem.
The 3rd thing I did was ask friends and a family member to test it on their devices.

All.. The ... Same.. Result....

The ONLY thing that's changed is that apx. 24hrs ago I updated my SEO and that's when the problem started. Logically it's got to be something related to that. Chrome is built by google and it's the only browser having this problem.

So, what other conclusions can I come to?
sitemap has nothing to do with how google (or your browser) renders a website.
So, you still came to the wrong conclusion.

A sitemap is primarily a tool used to inform search engines like Google about the structure of your website, helping them index your pages more efficiently. It does not affect how a browser renders or displays a website.... ok enough about sitemaps.

Have you checked your JavaScript and Redirects scripts?
check for HSTS or SSL Issues
have you looked in your server logs? find what exactly is causing the 500 since it may show what is failing
How about checking your relative or absolute paths?
 
Have you checked your JavaScript and Redirects scripts?
check for HSTS or SSL Issues
have you looked in your server logs? find what exactly is causing the 500 since it may show what is failing
How about checking your relative or absolute paths?


Javascript = Checked
Redirects = Checked
SSL = Checked
Server logs = Checked
Paths = Checked

Please don't think that I'm being a troll. I assure everyone that I'm just trying to figure this out because none of it is making any sense to me.
It's because I'm stumped that I've posted my problem.

The ONLY place there's a problem is with Chrome. I've put the site back to the way everything was 2 days ago and the 500 error is gone. Right now I'm doing one small change at a time and seeing what happens after each.
 
Javascript = Checked
Redirects = Checked
SSL = Checked
Server logs = Checked
Paths = Checked

Please don't think that I'm being a troll. I assure everyone that I'm just trying to figure this out because none of it is making any sense to me.
It's because I'm stumped that I've posted my problem.

The ONLY place there's a problem is with Chrome. I've put the site back to the way everything was 2 days ago and the 500 error is gone. Right now I'm doing one small change at a time and seeing what happens after each.
how did you "change" your SEO
through a SEO plugin?
 
Weird situation here.

One of my sites loads perfectly with firefox, opera, etc.
But when someone using Chrome clicks a link... They get a 500 error.

What happens is the URL gets screwed up.
So the URL is supposed to be https :// site .com /pods but in chrome it becomes https :// site .com /main/pods

This problem is driving me crazy
This issue might be caused by URL rewriting or redirects in your server config. Check your .htaccess file or server settings for any incorrect redirects or URL mappings specifically affecting Chrome. Clear browser cache or try in incognito mode to rule out cached data issues.
 
It looks like chrome is adding "/main" to your url, which could be due to a redirect or a misconfiguration in your .htaccess file or site settings. check your redirects and permalink structure to fix it.
 
how did you "change" your SEO
through a SEO plugin?

I do it all manually. There are zero plugins of any kind on the site.

My research is showing that it's a common problem with Chrome browser. They literally list one of the solutions as "USE A DIFFERENT BROWSER."

The problem didn't exist before I did the SEO update. So, something is triggering Chrome but I've got no clue what it might be.
 
I do it all manually. There are zero plugins of any kind on the site.

My research is showing that it's a common problem with Chrome browser. They literally list one of the solutions as "USE A DIFFERENT BROWSER."

The problem didn't exist before I did the SEO update. So, something is triggering Chrome but I've got no clue what it might be.
what EXCATLY did you change then...
we can't help you
if you don't help us understand what has been changed
this is why a "changelog" exist.
 
what EXCATLY did you change then...
we can't help you
if you don't help us understand what has been changed
this is why a "changelog" exist.


OK here's the FYI.
95% of the problem is Chrome re-interpreting location.href javascript functions. The issue can be resolved by using location.assign()
Unfortunately, I have no control over how other sites handle javascript on their end.
 
OK here's the FYI.
95% of the problem is Chrome re-interpreting location.href javascript functions. The issue can be resolved by using location.assign()
Unfortunately, I have no control over how other sites handle javascript on their end.
then clearly it's your code of what you changed
it's not SEO at all.
it's your custom code.
I told you to check javascript at the start :s
 
then clearly it's your code of what you changed
it's not SEO at all.
it's your custom code.
I told you to check javascript at the start :s

Here's the problem.
I wrote that code a year ago and it has worked perfectly until the SEO changes.

So for shits and giggles, I rolled back my SEO changes and the original code went back to working without a problem.

I don't know what the connection is or if there's actually a connection.
But I'm also pretty sure that Chrome development team are clueless too, if they're even aware of the correlation.

The site is working now and that's all that matters
 
Instead of blindly trying things, see the logs first. Those 500 errors must have generated error logs. See what the log says. Perhaps give us the some of the logs (be sure to remove sensitive info from it) if you are not 100% sure what they mean.
 
Instead of blindly trying things, see the logs first. Those 500 errors must have generated error logs. See what the log says. Perhaps give us the some of the logs (be sure to remove sensitive info from it) if you are not 100% sure what they mean.

I did all that there's nothing of usuable information.

But I've said... The problem has been fixed.
 
Status
Not open for further replies.
Back
Top