I mentioned in this thread - http://community.logos.com/forums/t/25342.aspx - that I've been having issues syncing for 12+ hours now. I was getting a bit frustrated, as I have some notes that I created on my other laptop that I want to access. So I set about trying to figure out what might be happening.
As a longtime Fiddler user (www.fiddler2.com - I see it referenced in a few other threads here), I monitored the traffic that happened during my syncs. In case anyone is interested in doing this, at a high level, here's how I did it:
1) Quit Logos
2) Install Fiddler
3) Run Internet Explorer and use it to run Fiddler (Tools -> Fiddler2)
4) In Fiddler's Tools -> Fiddler Options menu item on the HTTPS tab, check "Decrypt HTTPS traffic" and accept Fiddler's creation of a root certficate.
5) Run Logos
6) Execute "sync now" in the Logos command window
When I did this, I could see that Logos was getting a "401 Unauthorized" error trying to sync. The only guess I had at that point was to try signing in again. It took me a bit to figure out how to do that (I'd seen the instructions before but couldn't recall that it was called "sign in").
Once I did that and Logos came up, when I entered "sync now" into the command window, syncing worked fine. I'd love to understand why Logos "lost" my sign in information.
Something that a lot of people here will find interesting is to watch the HTTP(S) traffic that happens during a sync. For example, I got a lot of updates to book covers. Fiddler will show you the images (Inspectors, Response window, ImageView). My sync involved a few hundred requests / responses.
Anyway, things seem to be working for me now. FWIW...
Donnie
Donnie Hale:Something that a lot of people here will find interesting is to watch the HTTP(S) traffic that happens during a sync. For example, I got a lot of updates to book covers. Fiddler will show you the images (Inspectors, Response window, ImageView). My sync involved a few hundred requests / responses.
This Fiddler program is quite interesting. I will have a look at my bank's security
Thanks for the details on 401 error & sign in.
Logos 7 Collectors Edition
As mentioned on the other thread, the 401 error is unusual, and (we think) due to problems with Logos' servers.
It certainly is interesting watching Fiddler traffic - I've been doing so off and on for several months, and rarely seen any problems, though it does give you a good insight into how Logos is working.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!