Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why can't I or my clients view my own website on FireFox?

  • 17 replies
  • 1 has this problem
  • 434 views
  • Last reply by jscher2000

more options

Hello everyone, I am going to share a video here with you on what is going on to better explain it. Please watch carefully.

https://youtu.be/ryPPctB8iJg

For those unable to view, in basic, even with all add-ons disabled, I am still unable to log in or view websites that I created. This list of websites please visit: http://wgu.tactivelearning.com/

Do so to find out if you too are having the same problem.

Chosen solution

Alright, interesting fix, it turns out that WP SlimStat was the culprit for some, while simply deactivating and re-activating Peter's Login Redirect and Login Screen Manager fixed the others.

Strange, strange errors... In some cases, disabling all plugins and re-enabling all plugins even worked.

Thank you Mozilla Team and Contributors for your very valued support! I do hope that this information does help in some way for future releases!

If anyone involved with Mozilla is interested in taking a deeper look at my websites, I invite them to walk around in the control room with me!

Have a great day everyone!

Read this answer in context 👍 0

All Replies (17)

more options

hello, i can certainly replicate this in newer versions of firefox - in fact the error console shows a "HTTP/1.1 500 Internal Server Error" when loading your site. maybe there are some log files on the server that can provide more clues what is failing?

otherwise you might also want to try filing a bug about it - the regression range when the issue first appeared in firefox is https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f547cf19d104&tochange=54217864bae9. i cannot find any obvious change in that list though that would obviously be responsible for the issue...

more options

Alrighty, check this out!

[Thu Oct 02 20:34:47 2014] [error] [client xxx.xxx.xx.xx] File does not exist: /var/www/vhosts/tactivelearning.com/wgu.tactivelearning.com/index2.html, referer: http://wgu.tactivelearning.com/ [Thu Oct 02 20:43:41 2014] [error] [client xx.xx.xx.xxx] File does not exist: /var/www/vhosts/tactivelearning.com/wgu.tactivelearning.com/OBC1, referer: http://wgu.tactivelearning.com/OBC1/course-directory/materials/cohort-sign-up/ [Thu Oct 02 20:43:41 2014] [error] [client xx.xx.xx.xx] File does not exist: /var/www/vhosts/tactivelearning.com/wgu.tactivelearning.com/OBC1,

WOW right?

Files not existing? I am now very confused, because I am still accessing from chrome, and also, it turns out, a colleague is able to access it with firefox. Very interesting error set. Any ideas? I can provide the full log for the day if you would like.

more options

are these from today? - maybe it's worth a try fixing the time on the server then. i'm probably not knowledgeable enough to interpret any server logs, but you could provide them nevertheless (you can use a site like pastebin.mozilla.org for that) - maybe someone else here knows more about it...

more options

Yes, those would be from today, also thank you for the suggestion, I am trying that now. I am pasting the error log in the pastebin as well.

https://pastebin.mozilla.org/8826368

There is the pastebin link. I am not sure why they are all reading as Oct. 2nd, but I did go ahead and modify the server time. I will probably be taking this to my server host as well. Thank you for your continued support Philipp.

more options

I'm not seeing anything suspicious at the moment in the Web Console when I load the site on Linux. I see this request for the index2.html file in the page source that is supposed to be a CSS file, so you may want to check this out.

<link href="index2.html" rel="stylesheet" type="text/css">
more options

Thanks for the bug, Cor-el. I removed that, but unfortunately still no dice.

Are you able to actually view the linked sites?

more options

The problem is related to user agent detection. When I spoof my user agent in Firefox to a Chrome user agent, the site works fine. Something on the server is reading the user agent, and changing it's behavior. The case where it sees a Firefox user agent causes the error.

For reference, the user agent I used was "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89 Safari/537.36"

more options

Update: I ran basic access testing on the following browsers with the following results:

Internet Explorer - Working
Opera - Working
Safari - Not Working
FireFox - Not Working
more options

Alright, that helped me narrow the problem significantly!

So something in the code somewhere is trying to render something differently somehow based on the user agent.. 

I wonder how I might go about repairing that. I will need to dig around I suppose.

Any ideas anyone?

more options

If I use the ua-site-switch extension to pretend that I'm using Chrome (I used "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.154 Safari/537.36") then the redirect works properly.

Were there any recent updates to any templates or plugins on the back end of the site that you could revert?

If not, is it possible the site was hacked by very incompetent hackers?

more options

Nothing has been modded for the themes or plugins for awhile but I am duplicating the package and am going to attempt to pinpoint the error source.

more options

with a faked useragent for firefox 35 the site still works:

Mozilla/5.0 (Windows NT 6.3; rv:35.0) Gecko/20100101 Firefox/35.0

but it's failing with firefox 36 onwards - this also corresponds with the regression window dug up originally, since the version change on nightly from 35 to 36 happened on october 14. strange...

more options

Yeah, it really is, perhaps WordPress's agent manager was unable to support the new changes made? I will come back with what information I can once I get back from the store. Thank you all for your wonderful support! :)

more options

As far as I know, it's not a general problem with WordPress 4.1.1. Certainly my blog is not doing this.

If you can do it without breaking important functionality, I suggest investigating whether you can isolate the problem by disabling individual plugins.

more options

That is what I am going to be doing, thank you Jscher2000.

Hopefully it's not an important one! I will inform the community as soon as I isolate it to ensure it is understood!

more options

Chosen Solution

Alright, interesting fix, it turns out that WP SlimStat was the culprit for some, while simply deactivating and re-activating Peter's Login Redirect and Login Screen Manager fixed the others.

Strange, strange errors... In some cases, disabling all plugins and re-enabling all plugins even worked.

Thank you Mozilla Team and Contributors for your very valued support! I do hope that this information does help in some way for future releases!

If anyone involved with Mozilla is interested in taking a deeper look at my websites, I invite them to walk around in the control room with me!

Have a great day everyone!

more options

Thank you for reporting back!

I noticed WP SlimStat was updated March 10th (3.9.8), March 17th (3.9.8.1), and March 18th (3.9.8.2). It incorporate an array of browser identification data from browscap.org that it uses to recognize different browser versions. Perhaps that is the underlying link between finding this issue in different plugins? Anyway, I don't enjoy reading PHP so I'll set this aside for now.