Is anyone else having to keep signing in to Community or getting additional security check in?
Answers
-
Thank you explaining that the two posts had been combined, as I knew the original title of the post I originated was just, "Is anyone else having to keep signing in to Community?" as I still haven't experienced the "Incapsula behaviour".
I am not at all happy that a moderator / administrator has chosen to mix-up two separate issues. At least there should have been a notification of their action.
@Sam Sulser - perhaps you can look into this and ensure - unless the subject matter is exactly the same - posts should not be combined in future.
3 -
The "I am not a bot" issue includes being frequently logged out of FamilySearch - they appear to be part of the same issue.
For some reason, using Firefox, I cannot replicate the problem IF I stop using my VPN. It occurs 100% of the time when I use my VPN. Obviously, the security-check software at FamilySearch's end recognizes a non-standard server (no reverse DNS is my guess as to the problem), and believes the user is actually a bot trying to hack the system. But once I count the four busses, chimneys, crosswalks, etc., I should at least be able to remain logged in. Instead, every few minutes I have to log back in and count images again to prove I'm a human being.
0 -
In my experience, the two issues are definitely not connected. As stated previously, I have not encountered the "bot" issue at all, in using any part of FamilySearch.
Also, I do not have VPN and on switching to Chrome (from Firefox) yesterday, discovered the problem of being constantly timed / logged out was even worse. Coincidentally (I would imagine) my experience in using the main website (including Family Tree) appears to be quite the opposite - as I'm sure I've been leaving the PC for well over 40 minutes, yet still haven't been timed out when I return.
I don't want to have to copy / paste from Word when I'm only making relatively brief comments, but am getting in the habit of copying the text before clicking on "Post Comment", just in case what I have typed has not been saved as a draft.
2 -
Late yesterday, I was being signed out of the FS main site in a most troubling way. I was looking for a specific digitized, unindexed, reel in the catalog. The record set covers 27 pages. I was signed out, while actively working, between skimming one page for the number I needed, and flipping to the next page. It happened several times.
Firefox, Windows 10, all fully updated, no VPN.
0 -
Áine, could your image-browsing problem have been a recurrence of the viewing bug/throttle? This had appeared to go away for a while, but people have been reporting problems again in the last several days, and I experienced it yesterday. It's typically an error message ("Error loading image") rather than a log-out, though.
1 -
Another possibly related odd behavior I am seeing a lot this week, including today, is that I am apparently logged out but if I simply click a few links, I find I am still logged in. This is on both sites, FamilySearch and Community.
2 -
@Julia Szent-Györgyi I wasn't even trying to view an image, so I don't think it was the throttling issue. I did experience the throttling problem once I finally was able to get to the particular reel I wanted to view. And, it was after only viewing about 5 images on the reel. Quite annoying.
0 -
I still suspect the logging out issue is related to the CAPTCHA issue with them both showing up at the same time. I get both, some only get one, but they both started at the same time for me, as well as many others, it turns out. Some use a VPN, others don't and still have the issue(s), yet when I turn off my VPN the problem ceases for me (until I turn the VPN back on).
@dontiknowyou When I'm in FamilySearch I can move around as if I'm still logged in, but if I click on one of the people in my tree to see their person page, their little "info card" as I call it pops up with "UNKNOWN" in place of the person. I have to log back in to see the people in my tree at that point. Just weird behaviors!
--Chris
0 -
Hi All
I contacted FamilySearch Support for and answer to my original problem with Edge Browser and Incapsula interference when trying to log into FamilySearch and constant interference as I used the programme. They came back with a fix for me. and I enclose the following portion of their reply.
"The fact that this only occurs in Edge indicates that it is a browser issue and not a website issue. With the caveat that we are not able to support local hardware and software, we found this solution recommended by Microsoft to alleviate the issue when it occurred for us:
- Click on the 3-dot menu at the top right corner of the browser window.
- Select the gear icon for Settings.
- Select "Reset settings" from the left side menu.
- Click on "Restore settings to their default values"
- Click on "Reset"
If that does not resolve the issue, then you may need to search the web for other solutions which may include removing a Captcha add-on or extension from Edge or getting rid of an unwanted "passenger" in the browser. However, we experienced that issue coming up with the Captcha and "I am not a robot" checkbox just in the last few days. We think that the process above has fixed it but haven't had enough mileage to confirm for sure. The reset process did not affect our autofill or saved passwords."
I tried it and it worked. Thanks for all your input.
Regards
Graeme
0 -
@graemechambers This may be a Microsoft Edge issue for one person, but not everyone uses Edge, and this problem occurs with other browsers as well. As stated at the top of this thread, I use Firefox. So there's more going on here than simply an issue with the Edge browser. I believe in another place discussing this issue I also recall seeing someone that was using the Google Chrome browser.
-- Chris
0 -
Hi, is anyone else having problems loading pages? I can't open any profile. The same message comes up "Oops, something went wrong. Please refresh the page." Nothing else happens when I refresh, though.
0 -
Right now as of 9:30 am - the FamilySearch servers are slow responding.
0 -
@Stephanie Thomas Last night we had zero problems - never saw the Incapsula page at all. It remained logged in for the entire 1½ hours of the class without any interruptions.
However, this morning it showed the "I'm not a robot" page again, and then the visual window to find all of the "whatevers" in the frame. And within a few minutes it timed me out, requiring a new complete verification that included identifying the visual elements in the window. So, it's still "broke."
@C_Geek Are the problems you're having in the main FamilySearch website with Family Tree, or here in the Community Groups? I've had no such problems with either of them this morning, other than the Incapsula non-robot verification page. When you say you "can't open any profile," do you mean that if you click on any of our names/IDs associated with any of the above posts, you can't pull up that person's profile? If not, please explain further.
0 -
The problems I am having are on the main site, not this one. I cannot access any IDs/profiles. The "Oops…" message is the only thing that comes up.
0 -
@C_Geek Have you tried the usual basic troubleshooting? Using a different browser and/or clearing cache and site-specific cookies in your preferred browser?
0 -
I don't mind losing the session (being logged out) when the session cookies expire, that's good security. All I ask a enough time to take a comfort break or make a coffee. Up until recently it's been fine. No need to fix anything. So why change?
But .. It's hard enough to battle with the terrible "improved" search without getting further hindrance from those annoying captchas. Did we ask for them ? I don't think so.
And now, the search engine is completely busted.
0 -
On another thread we were told the following:
4 Dec from Ken Richins - NAO Tech Support Lead:
I believe as we transition from the routable IPs in the centers to the non-routable IPs this issue will resolve itself. As the transition will take until December 15, 2022, I suspect until your center is moved to non-routable IPs you will have the issue, but after the transition, the issue will be gone.
For home computers, the best option is to disable the force to use HTTPS for all sites, Until the engineers update the security settings on the new servers and the new hosting platforms of the FamilySearch sites. This will also take a few hours for the various DNS servers to update their information to match the tighter security that our updated browsers are requesting from the servers.
0 -
Google Chrome and Firefox browsers sent false messages about other sites, saying not safe even with secured https no matter what.
The sign in issue has nothing to do with the centers we have been having.
0 -
@Tiffany Nash Disabling force HTTPS is a very bad idea. It opens the door wide to data theft and man-in-the-middle attacks to both parties. While the world is in it's present state with regard to China and Russia I would strongly argue that nobody should be reducing their security settings. If there is an issue with IP routing then I would prefer to wait until the issues are resolved.
1 -
Whilst I am not complaining too much, my original post - which relates to the constant need to sign-in to Community - has now lost its focus. I would like to re-emphasise the problems this is causing me in having to remember to copy the text before I "Post Comment", as this is frequently being lost - even if I have only spent a few minutes typing my comments.
I don't know if it is FamilySearch engineers, or those from an outside organisation (as was the case with GetSatisfaction) who maintain Community, but this - together with the problem of images not sticking (unless you know the workaround!) - really needs urgent attention.
4 -
I find that the problem with staying logged in on the community has gotten much worse. I can barely finish reading a few comments on threads I'm following before I'm logged out. I am not experiencing a problem with staying logged on the main website or with encountering security captcha issues.
3 -
I know how frustrating this is. I work in the Community full time and get kicked out very often. Please know that FamilySearch is aware of the problem and it is being looked into. Please also know that when I hear about a fix, I will let you know.
Maile 🙄
3 -
"AT" Family History Library (SLC), automatic log off after 15 minutes inactivity. Same rule at Family History Centers.
Home? Should not log out for no reason. There's a setting when you sign in, click to keep logged in for 2 weeks. It won't log out by itself.
0 -
@W D Samuelsen contact me please
This is a known issue for 2-3 weeks now, and it most definitely is requiring multiple logins per active session. It appeared to be resolved for several days last week, but continues to be an occasional glitch. And I'm speaking only from the standpoint of home use, since we've not encountered it in our FamilySearch Center.
--Chris
0 -
Chris
check YOUR computer for AV/security issues.
I haven't had sign in problem since I looked into this about a month ago.
0 -
Been there, done that. It was the first thing I checked. I run two different pieces of security software. When it was the worst two weeks ago I discontinued use of my VPN, and at least while I was going directly through my ISP I did not have the problem. I've reported that to tech support, as I suspect that could be a factor, since the VPN reports differently than what would happen if I was using my ISP's server (no reverse DNS). But that was just my theory - insufficient knowledge of how all that works to be sure.
Note: after a nice clean day with only a couple of required proofs that I wasn't a robot almost all day today, I finally got logged out in the middle of something I was actively doing a couple of hours ago tonight, and had to log back in again - with no significant lapse in activity that should have triggered it (certainly less than 10 minutes, probably much less).
--Chris
0 -
Hi everyone-
Just touching bases to see how it is all going with the Community Log Out issue that we were all experiencing. Hopefully, it is back to business as usual. (As a reminder, this issue is completely separate from the other Captcha/Error 15 issues that the security update has been causing. It all just happened to hit at the same time.)
The engineers from both FamilySearch and our Forum tell me that they have made the necessary modifications to eliminate this issue as best as we can. We also have increased the session timeout to 6 hours which is the longest that we can safely set it. This means that you can work in the community for up to 6 hours without being logged out.
Hopefully, you are noticing a difference, as I am, when working in the community. I know how frustrating it has been. Thank you so much for your continued patience as we work through some of the technical issues that arise in this challenging digital world we live in.
-Stephanie😊
1 -
Everything seems back to normal (both problems) for me. Thanks for check up Stephanie!
1
