RootsSearch and FamilySearch

Question

For the last few days I have been unable to access FamilySearch directly through RootsSearch. All I get is a blank screen. I have cleared my cache, etc and am using Mozilla Firefox. I have used it successfully up until now.

RootsSearch still works for other sites like Ancestry, MyHeritage, FindMyPast, FindAGrave etc so I think it is not my software.

I have read that this has been a problem in the past too.

I prefer to use FamilySearch for sources, so this is a nuisance and is slowing me down.

Comments

It's likely not you or your computer, it's the Family Search website.   Something like this happens with them every few years and they always manage to restore it to the way it was.  Hang in there, it's affecting me and many others as well.  I'm just working on other things until it is restored.  Good luck!

Answer 1

You mean the LDS website? Why not go directly to www.familysearch.org?

Comments

I have my bookmark to go directly to familysearch site 

https://www.familysearch.org/search/

---

Because then I have to re-enter all the data and that takes time. I would rather spend my time writing profiles.

---

I find entering birth and death at same time doesn't show all sources as when only birth is entered, have to change name for death usually if they married

---

Also using exact birth or death years instead of a range can give different results

Answer 2

Hi Margaret,

Is it a completely blank page or an error page?  If you get an HTTP 500 error, try pressing the RELOAD button.  I just tried and got the HTTP 500 error, but the FamilySearch page loaded after I pressed RELOAD (using Chrome).

Same thing with the HTTP 400 error.  That appears to mean you're not signed in, but it should take you to the sign-in page after you RELOAD.

Comments

I get a blank page after I have signed in. Reloading does not change that. The problem is that the site is not secure, and that is why it will not load. I change the settings and then can get it, but it reverts every time I switch to someone else. It's a nuisance.

---

Have you tested it with a different browser?