Still cannot connect with RootsSearch

Question

I keep getting this message when I connect in any method.  

This site cannot be reached.

The webpage at https://rootssearch.io/search might be temporarily down or it may have moved permanently to a new web address.

ERR_HTTP2_PROTOCOL_ERROR

Comments

Well I know it is now a new month, all the postings here are Jan 2022, but I currently when trying to use RootsSearch, get in red print, "Unable to load the person. Check the ID and try again."  I can go to the help page and click on the "click here" link and enter profile ID, and it will work that way.  I have rebooted, logged out and back in, but still does it.  Just adding to this last posting of problems, if it is still getting worked on, just current two cents worth.

---

I have not been able to reconnect using rootSearch. I ended up switching over to the WikiTree Sourcer program that several in this thread have recommended. I am using my windows laptop with Chrome. It works really well. There are some aspects about research I really miss. But there are some things about Sourcer I really like better.

I suspect, after reading through a lot of comments in various places, that my virus scan program, Kaspersky, might be the problem with RootSearch. But I’m not a tech, so have not idea how to find out.

Hope that’s helpful.

Answer 1

Hi, Trudy --

It does look like RootsSearch is down right now. I'll add a tag to your post to make sure Jamie sees it. She might have more information.

Otherwise, you can continue checking to see if the problem resolves itself, and there is also a browser extension that might work for you. See "WikiTreer Sourcer" on https://www.wikitree.com/wiki/Help:Apps

Thanks!

Answer 2

Hi Trudy,

I just checked and it is working for me, is it working for you again or are you still having issues?

Comments

I cleared my cache in my browser, but as of this morning, I still cannot connect.

---

You might turn off your device and start it up again.

Are you using a VPN? If so, turn it off and see if that resolves the problem.  I have noticed that within the last month, several sites are not working when I have my VPN switched on (at least in some browsers).

---

I have had the same issue for a while, is it still not working for you Trudy?

---

I still cannot use RootsSearch.  I have been able to access FamilySearch on a separate tab, independently of RootsSearch.  But I will say I much prefer the convenience and the better search results of RootsSearch.  

I am not using a VPN.  I tried several different browsers.  It's weird.

---

I keep getting a message that the site cannot be reached.  "The webpage at https://rootssearch.io/search might be temporarily down or it may have moved permanently to a new web address.

ERR_HTTP2_PROTOCOL_ERROR"

---

Trudy - I have tried WikiTree Sourcerer recommended by Julie Ricketts, that works well instead of rootssearch.

---

Hi, Jamie -- I'm also having the same problem when I try to use RootsSearch. I haven't done any troubleshooting, so I suppose it could be another extension that is interfering. I'll try to dink around a bit and see if I find anything.

---

Julie got it to work after she disabled her virus software (Kaspersky), but just whitelisting the site did not work.

Answer 3

As of 13 Feb 2022,

• RootsSearch won't work on my iPad (iPadOS 15.3) using Safari.
  • I have used the Sourcer 1.1.0 Safari browser extension and it works for searching Ancestry.com
• RootsSearch does work on my laptop (macOS Big Sur 11.6.3) using the Chrome browser.

Comments

Are you getting the same "ERR_HTTP2_PROTOCOL_ERROR" error, will it not let you log in to the apps server, or is it some other issue?

---

It's working for me now. It was not working for me earlier today and for some days past.

After my above post, I did update to iPadOS 15.3.1, and the iPad was rebooted in the process. So, that is the state of my iPad at present.

---

I was able to log into the apps server prior to the update. I would then close the window. Then re-initiate a RootsSearch inquiry from the profile page and that's when it would just freeze. It would never completely load the RootsSearch form page in order to choose a site to search on.