I tried to start working on a project. When I click on Index or Review, I receive Request failed with status code 403.
Does anyone know what that means, please?
This article may explain the reason for the error message
I keep getting error messages when indexing
The above article is really helpful for these problems, but, the first thing I would try is to re-set ONLY the FamilySearch cookies and temporary files and also check my browser settings. There should be no reason to clear your entire browser history or all the cookies if the only problem is with FamilySearch. This attached link with give you the link to clearing those cookies.
Here's an article that tells you which browsers are supported for indexing. If you are using Apple Safari, it really is key to check for updates pretty frequently - even if you have told it to update automatically because it doesn't! The current version of Safari is 15.4
I am not fond of doing anything that affects other programs. Mostly you do not have to. Resetting the FamilySearch cookies with familysearch.org/cookies, updating browser, simply going out of the program, browser or turning off the computer then going back in usually solves most problems. If those don't work then trying an different browser often solves any lingering issue.
I never delete all cookies or temp files on my computer for these issues. It causes too many other programs to get ticked off.
Thank you for your responses. However, none of the responses explain what this or other status codes actually mean.
Your responses suggest that Family Search software handles cookies inadequately and that these must be deleted from time to time to unconfuse Family Search.
Is there a list of the status codes and their meaning somewhere?
You can do a google search and learn all about individual HTTP status and error codes.
403 is a code that means that you are connecting with the server, but, it refuses to allow you rights to use the program. It could be confusion between your browser and the server. Thus, cleaning up your computer often fixes the problem as does exiting the program and starting over.
Thank you. That helps. I didn't realize that the Family Search status codes are HTTP status codes.
@Yogi Schulz Did you manage to solve it? I'm having same issue.
@Marina Melillo Braga Did you try the suggestions above (check your browser for compatibility and do some general housekeeping like clearing the familysearch cookies) ?
Your previous answer: "individual HTTP status and error codes" is the correct answer to my problem. Thank you.
The problem is that the phrase HTTP is missing from the descriptor that Family Search provides along side the error code.
I have since learned that FamilySearch includes the geographic location of the searcher in determining the result set for an Indexing Project search. Therefore, a given project is available for some countries but not others.
I appreciate you taking the time to answer. However, these actions "check your browser for compatibility and do some general housekeeping like clearing the familysearch cookies" are time wasters. Usually they're not helpful and on the rare occasion that they are, they point to software inadequacies at Family Search.
Have you every experienced Amazon, an airline or the IRS suggesting these actions in response to a problem?
@Melissa S Himes I have.
@Yogi Schulz Did you manage to review any batches?
I found out what my problem is: I don't have enough in the new web based system. I was seeing the totals that cound the old desktop version (which I liked way better by the way :D )
@Yogi Schulz I am glad you recognized the problem. It is interesting that you found that it was a problem with geography. Although I do recall a previous question where a US citizen was travelling and trying to index in a country where the IP address wouldn't allow access. It is rare to see projects to choose from that are restricted to other groups. For instance, Wisconsin projects are often for restricted audiences, and during the lock-downs Australia and NZ projects were limited to their citizens. But, they only appear on the selection lists of those who have rights to index them. Hopefully, you have been able to find other projects that allow you access.
The "time wasters" have fixed many problems for people who couldn't use FamilySearch Indexing. Most of the time it seems to be MAC users who are using old versions of Safari or their OS hasn't been updated. So, that has become the first response. However, with your investigation, we can add geographical location to the reason for error messages such as 403's. I don't think we can compare commercial websites with FamilySearch, but, no, I rarely experience a problem with access to the sites you mentioned.
@Marina Melillo Braga Best wishes on getting to 1000 records and obtaining your review rights. The Review button didn't use to pop up until you had completed the task. Maybe that has been changed? I also liked arbitration better than reviewing, but, the new program is really great once you get used to using it. There are several videos on YouTube that are helpful - especially, Indexing Discussion (Jason Pierson Live) The actual indexing demonstration starts about the 8 minute mark.
@Melissa S Himes
"Most of the time, it seems to be MAC users who are using old versions of Safari or their OS hasn't been updated" I believe you are correct. I expect web applications to recognize this problem and display a dialogue box that says something like: "Your OS version and/or browser brand/version are not supported. Please update." That message dramatically reduces time-consuming support calls and discussions.
@Melissa S Himes
"I don't think we can compare commercial websites with FamilySearch."
Given the near-global reach, an incredible volume of data, significant functionality and a vast end-user community of FamilySearch, I suspect most end-users expect FamilySearch to behave like a commercial website.
Yes, I agree with you, Yogi. But after 10 years of working with the program, both desk-top and web-indexing, I have learned that this program is significantly different from commercial sites. I will add that most transcription websites, or at least the 6 that I am involved in, do have the same types of issues for the end-users. So, I don't put blame on the FS engineers for this not behaving as one might expect.