I am on vacation and not using Logos everyday as I usually do, but today, after several days away from comp., I tried to log in and can not. Do not get anything. I am on a mac, logos is updated (I think)....any help?
Normally, you don't need to "log in" since the app is designed for a single user. Do you just mean you can't start the app, or is the log in box appearing? If the former, try opening the app via the applications folder. If that doesn't work, download the newest engine and install it manually. Links in my signature line. If you are actually having log in troubles, check a different Internet connection
A few days ago, Logos had a glitch that required rebooting their log in system. This meant everyone had to log in again, even if they hadn't logged out.
As to why you can't log in, there could be many reasons, including a firewall in the internet connection you're using (some block 'religious' sites). But you should also check your log in name (usually the email you used when you first set up your Logos account), and password (also easy to mess up or forget). Can you log on to Biblia.com with that user name & password and see your stuff? If so, it should work in Logos as well. You should also check any firewall on your computer that might have updated itself and blocked logos.com for some reason.
These are just some basic steps and your issue could be more complicated, but it's always best to start with the simplest solutions.
the log in page does not even come up. I click on the logos logo in my dock and it will not come up.
I can log into biblia.com on my user name and pw....
Check your settings to ensure that you have "Use Internet" set to "Yes."
In Windows you can force a log on by holding the CTRL key as Logos starts. I assume that with a Mac, CMD does the same thing. You could also try that. (I'm not a Mac user, so I'm guessing here.)
Your issue appears to be unrelated to the one Rich describes. Did you try my suggestions above?
thx bama. Went and uninstalled old version and reinstalled engine and that is the fix. Apparently there is a bug in last update that causes this and some will have to trash old engine and reinstall.
Thx for all the help!
