Is there a known cause for the 500 Internal Server Error coming up on every person page?
I had a slew of ppl open, as as I finished working w one subset and looked at others, they all briefly showed me the person page, then reloaded to the 500 Internal Server Error.
I'm also getting the 'person page keeps reloading' problem.
(Win 10, Chrome, probably too many tabs open.)
답변들
-
I wonder if you are right about too many tabs open. I'm not seeing this issue. You can try clearing cache , rebooting and all that too. It usually helps my computer shake some cobwebs out. If it's still giving you issues, would you post this here Family Tree — FamilySearch Community to see if anyone else if having the issue?
Hope it's cleared up!!
Sam 😊
1 -
It may be that you happened to be using FamilySearch while some maintance or updates were being done. With all the changes that have been made (and apparently continue), some things may have to be taken off line in the system for them to make the updates/changes. I've had some weird errors such as that and other things lately that I knew were not local and weren't occurring on other websites. So I just give it a few minutes, and if it doesn't clear up I go do something else, and when I come back all seems to be doing well again after a complete log-off, browser closing, clearing of cookies and history (I've set my browser to automatically clear cookies and history upon closing), and then trying again from scratch. That's worked virtually 100% of the time recently.
Chris
0 -
Certainly makes using FS a huge frustration.
They could at least put up a better error message letting us know they're doing maintenance. My response is to close FS and not return for a few days or weeks. No sense pounding my head against that particular brick wall.
Thanks for the info. I hope they fix the website.
0 -
Note that I said it may be due to some maintenance or changes they're doing. We don't know what's causing it. In any case, I've rarely or never experienced FamilySearch going down for more than a few minutes, so doing something else, taking a break for a few minutes if it doesn't quickly clear up, etc., isn't something that would seem to warrant not continuing to do our own work for days or even weeks. It may not even be anything they have any direct control over anyway.
--Chris
1 -
This is hitting me every single time I use FS for more than about an hour, and I can almost guarentee at this point it's due to having too many tabs open and the fact that FS is now trying to continually update information in background tabs. The browser console shows that the 500 errors are happen after certain resource calls get rejected with a 403 error -- trying to load those resources directly shows that Imperva blocked them. This problem is now almost a year old: https://community.familysearch.org/en/discussion/135001/access-denied-error-15/p1
0 -
@RTorchia , I have a hunch that you may be on to something. I suspect we've gotten so advanced in potential capabilities, and our use of high level computer languages that the massive sub-surface infrastructure is resulting in, as you basically say, "too many things trying to happen at once." A computer can still only really process one command at a time, though extremely high speeds of today, massive infrastructure compressed into small boxes, and graphical programming makes things too easy to pile one task upon the next, etc., etc., etc. Eventually, it simply doesn't work.
Just my 2¢ ....
--Chris
1 -
@--Chris, I've worked in tech for 25 years and definitely think you're on to something with the dev culture here. Certainly the fact that it's impossible for end users to communicate with the dev team except through an intermediary is pretty telling.
I think in this case, from a security perspective, the servers receiving a high volume of repetitive data requests (i.e. the background tab refreshes) that look suspiciously like malicious activity. The dev team added the auto-refresh functionality (at nobody's request), and the web security team added some third-party security service (Imperva), and in some cases, these two things just don't get along. Add in that my ISP is a small, local one (rather than Comcast, AT&T, Spectrum, etc.) so it's probably either viewed with suspicion or has an exotic configuration of its own that Imperva can't handle.
0
