Dear Community,
this is a post for the network specialists or network administrators (like I am) and does not concern the Logos Software itself, more its update-mechanisms.
Ever since I got my new UTM firewall, Logos won't update. I had the same with some other products as well, for example Microsoft and Apple Updates. This is due to the fact that I use Web Filtering and Proxy Software as well as an Application Firewall. As this same Firewall will be used in our Church as well, a solution is a must :-(
Setup:
During Updates Installation I saw Logos connecting to cloudfront.net servers to get the updates. And I saw these Servers are "passed" through the firewall, so no block appearing here.
So, just as for Battlenet, Microsoft and Apple Updates and some others, I needed to setup some exceptions to my web filters, for example:
- Skip Authentication Checking
- Skip Caching
- Don't block by download size
- Don't AV scan
- Don't do MIME type blocking
- Don't scan SSL
- and so on.
But nothing does work. If I manually add my Mac to the "completely skip these hosts" list, it works without a problem. So I know it must be the Webfilters. These are the Servers I am skipping:
- logos.com : ^https?://([A-Za-z0-9.-]*\.)?logos\.com/ and ^http?://([A-Za-z0-9.-]*\.)?logos\.com/
- cloudfront: ^http?://([A-Za-z0-9.-]*\.)?cloudfront\.net/
Are there other Server/Hosts needed for the Logos Updater process? I haven't seen other connections:
-
Logos 1034 tomkat 297u IPv4 0x97239e1de49c4051 0t0 TCP imac.homezone.lan:55522->server-54-230-201-37.fra50.r.cloudfront.net:http (ESTABLISHED)
-
Logos 1034 tomkat 301u IPv4 0x97239e1de3d7c441 0t0 TCP imac.homezone.lan:55523->server-54-230-202-64.fra50.r.cloudfront.net:http (ESTABLISHED)
-
LogosInde 1046 tomkat 58u IPv4 0x97239e1df672f441 0t0 TCP imac.homezone.lan:55532->server-54-239-168-230.fra50.r.cloudfront.net:http (ESTABLISHED)
-
LogosInde 1046 tomkat 59u IPv4 0x97239e1df672f441 0t0 TCP imac.homezone.lan:55532->server-54-239-168-230.fra50.r.cloudfront.net:http (ESTABLISHED)
Any help is appreciated, as I want to role out features like Webscanning/Url-Filtering/AV Scanning in our Church and don't want every visitor or the Pastors coming at me for blocking their Logos ;-)
Blessings from Germany,
Thomas