! Image Currently Unavailable (Forbidden).
I get the above error message everyday. When I open a project If I don't finish the project I get the above error message within 30 to 45 minutes. I am unable to see the data that I am Inputting from. For example If I am indexing and say I have gone down 20 entries and then need to leave the project I use to be able to come back and pick up where I left off. Now when I go back I can see the work I have done but am unable to see what I need to finish inputting. If anybody has any solutions please send me back a message. Thank you.
Many times our computers get overloaded with cookies and browsing histories. If you clear the cookies and browsing history often it will usually clear up this problem.
If you clear all cookies, it can affect your access to other websites. Try these steps first:
- Make sure you use a supported Internet browser.
- Delete just the cookies that FamilySearch uses.
- Go to https://FamilySearch.org/cookies.
- When the message Reset your cookies? appears, click Yes.
- If the problems still occur, clear all of your temporary files and cookies. Then restart your computer. Please search the web for instructions for your specific browser.
- If you still have problems, delete your autocomplete history. Search the web for instructions for your specific browser.
- (Optional) Reset your cookie preferences on FamilySearch.
Have you tried clearing your Browser History and cookies lately. If not, you can go into your browser settings and be sure and select "clear all" for the history and cookies. If you have not done this for a long time, it may take some time for this to complete.
If this is not done at least once per quarter each year. it can cause problems, with the browser running properly.1
@davidlloydfrandsen1 So you are saying this happens in ANY project or just a certain one(s)?
SOLUTION: Finish the project 🙄 😣 (because this idea would help this. I wonder how many more would participate if indexing a batch didn't take 'long')
If it is not an issue with the way a particular project has been setup - I would guess (no solution here) - that something has changed in your FamilySearch 'account'. As to what that might be I have no idea what goes on behind the 'account curtain'. I know they changed some reporting features recently but don't know of any other changes that might cause an account issue - so maybe it's not an account issue. Maybe it's all Project related. Maybe they are timing your indexing and only giving you so long to have a Project 'open on the screen without activity'. I don't know. If you are unable to open and continue editing that batch - I guess they reclaimed or took it back. There is a document:
There is also this:
"try closing the FamilySearch indexing program and reopening the batch. Security software (such as antivirus, internet security, antispyware, and similar software) might be blocking access to the FamilySearch indexing server. "
But I would guess you haven't changed your system configuration significantly. Could it perhaps be that your system goes to 'sleep' and loses Internet connectivity? It COULD be a connectivity issue but I would think closing out and going back into the batch would allow you to continue if that were the case. Unfortunately - though I try to continue learning about the FamilySearch Web Indexing process - I don't know everything about the 'built-in' processes, dependencies, connectivity requirements, etc that might be causing this 'situation'.
I think I have experienced something similar a couple of times but I just closed out of that batch and reopened it and it allowed me to continue. The behavior you are experiencing is different - the image is 'gone'? I would be interested to know what your Batch> About Batch menu option would have to say in this circumstance - if the image is gone does it still recognize the batch 'headers'? Or what happens if you use shortcut key Ctrl + G to 'Open or Close Image Gallery' ?1
If, after trying all these advised steps and the problem still persists, please call us at 1-866-406-1830 so we can take a "hands on" approach. Thank you for your dedication.4
Melissa S Himes ✭✭✭✭✭
I think I may have replicated the problem. I pulled up a batch at 8:00, entered a little data, and went off and did some other things. I left the program open and the batch open. (The post says, "If I don't finish the project I get the above error message within 30 to 45 minutes.") I came back at 9:00. The first image was still on my screen. But, the remaining images had the error message Image Currently Unavailable (Forbidden)!
The system had logged me out of the program while I was away. All that was necessary was to return to web-indexing. The screen had another message for me to the effect, you have been logged out and need to log in. So I logged in and there were all four images in my batch - readily available.
It appears that the system has an automatic time-out/log-out. Makes perfect sense. No sense having people online without any activity. You still your original batch, captured on the screen, but, you can't proceed to other images.
Resetting cookies and changing browsers has become the "go-to" solution when people are reporting problems, but, it isn't always necessary. I would use clearing my entire browser history as a last attempt. Although I do agree that a periodic cleaning is a great idea, even on the 1st of every month!5
I agree with Melissa here - but was doing a little searching about clearing cookies/cache yesterday. It appears there is no 'real harm' in clearing cookies/cache other than if the user wanted to retain some of their recent browsing history etc. Perhaps someone more familiar can comment on whether there are other/more current browser processes to save/store information for later retention - as genealogists we like to keep our history.0
A possible "solution" to the apparent root cause of the problem - identified by Melissa as being automatically logged out - is to tick the box "Keep me signed in for 2 weeks" when you log in. Only do this on your private computer.2
One possible "adverse" effect of clearing cache and cookies on a browser is the following: If you are using two-factor authentication, say on a financial website, and have told their system to "trust" your browser, then the cookie that manages that information may be deleted, causing that system to prompt for an authentication code when you next log in. That's why trying a different browser or just clearing FS cookies are good, conservative first steps to take if you have a problem. Doing a full cleanup by clearing cache and cookies can be done as a “last resort” if you want to avoid inconveniences like the one I described.2
@davidlloydfrandsen1 this happens to me all the time also - but it is not a problem and happily your work has not been lost. The first time I got the message I thought I had been very naughty and banned from indexing 😅 but no all is good.
As @Melissa S Himes has identified, you have simply been logged off the system. So to gain access to the batch again go back to the Web Indexing page by clicking the black arrow "Return to Web Indexing" and you will see the batch in your list of My Batches.
Just open it again and away you go.
I am also getting the message, "Image currently unavailable (Forbidden)"; but I get it when reviewing a batch where a record spans two images and the second image is outside of the batch. The "Reference Images" window will show the images in the current batch, but not any images before or after the batch. The batch I am currently working is MS3G-TQK. The original indexer could apparently open the next image, because information was indexed from it.
I've indexed and reviewed many similar batches, and never before had this problem. I have cleared my cookies and tried a different browser, as suggested in this thread, but the problem persists.0
If you haven't cleared cookies and cache, I would try that. If that fails, then I would contact FS Support using the ? in the upper right of the screen for some specialized help. As you may know, someone opening a shared batch can no longer access the reference images - so I just don't see them. Here is the link to an article on how to clear cache and cookies for various browsers.
Update: I reopened the batch a day later and now I can see the reference images. It must have been a temporary system problem.2