Announcement: Logos 8 is now unsupported
Now that Logos 9 Basic is available for free to all users, support for Logos 8 has been retired. This means that it will no longer receive updates for bug fixes and new resource types, and you'll need to update to Logos 9 before Customer Service can help with troubleshooting.
FAQ
Do I have to purchase an upgrade?
That’s an option, but you don’t have to. Our promise is that you’ll always have a free, supported option to access your Logos investment. If you’d like to grow your library and add new features, consider upgrading to Logos 9 base package at a custom price, based on what you already own.
Will I lose any of my resources if I get the free Logos 9 Basic?
No, you will never lose any books or software features that you’ve paid for. Whenever you upgrade to a new version of Logos, anything new will be added to what you already have.
Can I still use Logos 8?
Yes, but it is no longer eligible for troubleshooting support by our Customer Service team. If you still have Logos 8 installed, it will keep working in its current state for the foreseeable future. However, as your operating system and other software on your computer continue to be updated, it will inevitably cause compatibility issues with Logos 8 in the future.
What if my computer has an older operating system, and won’t install Logos 9?
You can keep using Logos 8 unsupported (as described above), or you can access your resources on the Logos web app at app.logos.com.
For more detail on the support lifecycle, please see About Free Support.
How to get Logos 9
A paid Logos 9 upgrade is packed with new tools like Sermon Manager and Counseling Guide, and adds new resources to your library.
Even the free Basic version has more Bibles and other valuable reference works, and includes features like Dark Mode and the new Factbook.
And of course, every option will receive updates for bug fixes and improvements every six weeks.
Find more posts tagged with
Comments
- In Firefox, open faithlife.com.com, go to the certificate (via location bar icon),
and download PEM Chaim (yes, look for the options, takes while) - Open (=insert) that certificate with keychain
- in KeyChain, set the certificate to Trust Always.
- start up Logos again
- Time Machine backup of your Mac
- Check where youre latest Logos8.dmg file is, to be able to re-install later.
- Remove Logos with this app "AppCleaner". (removes all related library files, etc..)
- Clean install Logos8.dmg and log-in
- Let it all download your resources
- Check the status of your Personal Books
- Pray! (that's how my killed old Mac came alive again!)
It's a bad thing Logos 8 has no more support.
Welcome, Kees.
And you're right. I have an older PC ... probably will run W10, but I don't bother. Logos is it's only client, and I'd have to rework some older software. So, purchasing from Faithlife is considerably reduced (good for me).
But software and computers change so quickly, any app developer has to decide old or new? And often the system itself is unsupported. FL tends to look at its user computers/systems, to try to keep a balance. Sometimes, since ministers are especially wealthy, FL can be a bit aggressive.
If you have a Macbook 2009, you need to buy a new one.
I googled "iOS obsolete" and found this article: https://www.makeuseof.com/tag/4-signs-time-replace-mac/
says "This means that in general, you can expect about 10 years of life from a Mac, barring any unforeseen hardware issues. Now let's look at some signs your Mac is at the end of its life."
I know hardware purchases are costly AND I know OS upgrades are necessary because of security challenges! Personally, I believe Faithlife support has to keep moving with the majority of its user base.
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
I solved the thing this way: https://community.logos.com/forums/t/203183.aspx
Earlier this year, Logos 8, which I run on an elderly 2009 iMac running El Capitan stopped synchronising with the Logos servers, meaning I could no longer download new books. I accept that I will get no support from Faithlife as Logos 8 is no longer supported. Getting a new computer is however not an option, and given my internet connection, the Web Application is nowhere near as useful as having a desktop application.
I tried the trick Kees Parlevliet posted, but that did not solve my problem. Do any Mac users of Logos know of any way to get Logos 8 to once more synchronise with the servers?
Earlier this year, Logos 8, which I run on an elderly 2009 iMac running El Capitan stopped synchronising with the Logos servers, meaning I could no longer download new books. I accept that I will get no support from Faithlife as Logos 8 is no longer supported. Getting a new computer is however not an option, and given my internet connection, the Web Application is nowhere near as useful as having a desktop application.
I tried the trick Kees Parlevliet posted, but that did not solve my problem. Do any Mac users of Logos know of any way to get Logos 8 to once more synchronise with the servers?
If we cannot or do not want to update the software, we lose the ability to download new purchases? That is a scary thought to me! Is there a way to sideload new purchases?
If we cannot or do not want to update the software, we lose the ability to download new purchases?
That is rarely true although when you get enough versions behind the formats may change and create problems. Ken's problem is not representative of most people's experience.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
What kind of failure are you getting? If you don't know, set the program to create logs and enter the command "Update now" to try to capture the error. Then we may be able to work through the problem.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
I've done that. There's a file in the LogosLogs folder called LogosError.log which is quite long. The start of it is:
Program Version: 8.17 SR-3 (8.17.0.0022)
Mac OS Version: 10.11.6
Architecture: x86_64
Model: iMac9,1
Processor count: 2
Time: 2022-04-19 13:27:17 +10:00 (2022-04-19T03:27:17Z)
Installed memory: 8,192 MB
Install path: /Applications/Logos.app/Contents/Frameworks/FaithlifeDesktop.framework/Versions/8.17.0.22/Frameworks/ApplicationBundle.framework/Versions/Current/Resources/lib/Logos.dll
Free install space: 504,520 MB
Data path: /Users/Kenneth/Library/Application Support/Logos4/Data/ct3nz0nu.u2s
Free disk space: 504,520 MB
Temp path: /var/folders/vb/kvkbljx55gb1n1dss4bs53s40000gn/T/
Free temp space: 504,520 MB
Swap usage: total = 2048.00M used = 574.00M free = 1473.00M
Program Version: 8.17 SR-3 (8.17.0.0022)
Time: 2022-04-19 13:27:17 +10:00 (2022-04-19T03:27:17Z)
Retrieving the list of groups for resource LLS:JBL106, 2017-03-07T20:35:14Z failed.
Program Version: 8.17 SR-3 (8.17.0.0022)
Time: 2022-04-19 13:27:17 +10:00 (2022-04-19T03:27:17Z)
Error building request (GET https://api.faithlife.com/community/v1/askauthornotes/destinations?resource=gnssgdvlrgsnbbl&resourceVersion=2020-01-14T21:21:15Z).
System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> Mono.Security.Interface.TlsException: CertificateUnknown
at Mono.AppleTls.AppleTlsContext.EvaluateTrust () [0x000c6] in <b65344d8ea5f4c718b4dd6fb4f5020c4>:0
at Mono.AppleTls.AppleTlsContext.ProcessHandshake () [0x00075] in <b65344d8ea5f4c718b4dd6fb4f5020c4>:0
at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x000da] in <b65344d8ea5f4c718b4dd6fb4f5020c4>:0
at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool)
at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <b65344d8ea5f4c718b4dd6fb4f5020c4>:0
at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000fc] in <b65344d8ea5f4c718b4dd6fb4f5020c4>:0
--- End of inner exception stack trace ---
at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication
--------------------
Does this shed any light, or should I look at another file in the generated folder?
You really need to zip the entire folder and upload it -- the fact that this has a security certificate failure is a major hint that security is the issue.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
Here's the zipped log:
8712.LogosLogging.zip
Something is happening - it is informing me that I have 2.2 GB of updates, which is about what I would expect given the length of time it has not synchronised with the server. However, it is telling me I have a certain percentage downloaded, then bombs out saying download has failed. However, when I keep on clicking on download, the amount downloaded increases, going from 10% initially to - at the moment - 35%. I will keep on clicking on download to see whether I can get 100% downloaded and added to the library.
From your description, I suspect I know how to track it down and fix it on a PC but someone who speaks Mac is going to have to step in.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
As you can see, the error is on a GET to faithlife.com SSL connection. Meaning the certificate is not working/present. Just as you did in my recent instruction about logos.com .pem, now do the same with for faithlife.com. Install with KeyChain and let me know.
Thus:
Please let me know if it works. Attached the Certificates, if you cannot get them with Firefix.
I downloaded both certificates and installed them, but the following happened:
- It said it was downloading 3.9 MB of updates, then after a few minutes said the download had failed
- When I tried downloading again, it said it was downloading 2.2 GB of updates but my network traffic monitor showed I was not downloading anything
I have the same results when using the certificates you included in your post.
make a loggin zip, as explained here (goto Mac part).
then upload resulting .ZIP here, so I can check it.
Here's the log file:
0207.LogosLogs.Kenneth.20220421-082717.zip
The error log indicates no problem with the certificates this time. But error in retrieving from internet Logos resources, maybe Personal Books? Or an unsolvable dis-sync between local and internet resources.
"Status code not handled. Request: GET https://api.faithlife.com/community/v1/askauthornotes/destinations?resource=dicthintbbl&resourceVersion=2021-07-07T21:15:58Z (status ServiceUnavailable"
I don't know the solution for this one. I have same Mac and Logos versions as you (but also bought other new Mac this year)
This is what I would do, allthough never done yet with Logos, blind-eye, no succes warrant:
Kind regards - Kees
Thank you ever so much for all your assistance. The prospect of deleting my Logos 8 installation and trying a fresh re-install worries me just in case it doesn't re-install my existing library and I lose that. (39,000 resources). I have Windows 7 in Boot Camp so I will see if I can get Logos 8 there to work, and wait until I can get a new Mac and solve the problem that way.
Once again, thank. 
I've downloaded Logos 8 for windows, installed it under BootCamp, and have successfully downloaded my entire library including the resources I purchased after Logos 8 for Mac stopped synchronising. Now that I have my library back I'll be happy to completely delete the Logos 8 installation in the Mac side and see if reinstalling it solves the problem.
My vast library definitely needs a new Mac, but that's not on the menu for a little while. By then, I expect Faithlife will have a native Apple Silicon Logos application. Can't wait to see how the M1 handles Logos natively.