member login fails
Hey Natalie Martinkus,
One thing you could look at is the network traffic on the users end. You can do this by opening the developer tools (F12 in most browsers) and then clicking on the network tab. It looks like this:
Then when the user tries to login they will be able to see the requests being made and potentially where the issue is being caused. You would be looking for timeout errors here or 4xx errors.
Happy to discuss further!
Thanks,
Ben
If this answer was helpful please mark it as helpful. If this answer solved your question please mark it as the answer to help others who have the same question.
Hi Ben,
Thanks so much for the quick reply. I am very much NOT an IT person, so you may need to speak slowly and use small words with me 
Do I hit F12 from the web browser my client is using? What would an error look like, and how would I go about fixing it?
Natalie
You will need to run the developer tools on the machine that is having the issues logging in.
Error messages in the network console should show up in red. You will be looking primarily in this column:
Status codes of 304 mean it has already loaded these pages into cache so it doens't need to redownload them to the browsers. 200 code means it was able to successfully download them. Anything starting with a 4xx is normally an error that means the browser can't access the web url.
The network traffic can be quite long as every component of the web page that is retrieved will be in here but you can quickly scan for any red error messages. If you see any take a screenshot and post them here and I'm happy to have a look.
Thanks,
Ben
