I get an "Internal Server Error" when I try to go to the Indexing pages or the "become an indexer"
Answers
-
The indexing site has definitely been working all the past year. I wonder what address you are using/going to:
https://www.familysearch.org/indexing/my-indexing
This link works for me.
0 -
Thanks -- what browser & version are you using? I have tried Chrome and Firefox. I have reset both to defaults and even deleted them and reinstalled.
0 -
I'm using Chrome and that link has worked just fine for me ever since FS switched completely to web indexing. I'm using the current version of Chrome. What you might want to do is clear your cache and cookies . In Chrome, go to settings, then search "cache" and make sure only the cache and cookies are selected. Click "Clear Date", then restart Chrome. You're going to need to log back into FS. Once logged back in, your landing page should look like this:
Then click on "Get Involved", then click on "Indexing".
That should bring you here, the link that @genthusiast posted. I recommend bookmarking this page.
You can start indexing by clicking the "Find A Project" button. This pop-up will appear (if you have a pop-up blocker, it may not, so make sure pop-ups are allowed on FS). Here you can sort by difficulty level, language or percentage completed. Since you haven't been able to index, i'd recommend the WWI Iowa project. It's simple and straight to the point. There are also batch limits. This started during the height of COVID when everyone was home, thus giving everyone a chance to contribute at least something to a project. Also, depending on where you are, you may have access to different projects. There is a Wisconsin Birth Records project, that myself, a resident of Illinois, does not have access to. If you have any questions on anything, feel free to ask.
0 -
Yup tried all that and more. What version Windows are you running -- I have a hunch maybe that is my problem
0 -
I'm running on Chromebook. I ditched Windows a few years back, but Windows 10 and 11 are still supported by Microsoft.
0 -
Yes that could be the problem - FamilySearch does not support older versions of OS - what version are you using? It works on Windows latest version.
0