GFI Software

Welcome to the GFI Software community forum! For support please open a ticket from https://support.gfi.com.

Home » GFI User Forums » Kerio Control » Can´t connect iTunes Update Server
Can´t connect iTunes Update Server [message #119756] Tue, 03 March 2015 16:11 Go to next message
FloFMS is currently offline  FloFMS
Messages: 8
Registered: November 2011
Hello @ll

I can´t connect to the iTunes Update Server when Proxy is aktiv on Mac OS X. In the Kerio Log File i can´t find what´s going wrong.
How can I Diag what´s happen with this error. With deactivated Proxy the Connection to iTunes Update Server works fin.

I installed the latest Kerio Control Appliance 8.5 build 3127 on VMware Server.

Regards Florian
Re: Can´t connect iTunes Update Server [message #119763 is a reply to message #119756] Wed, 04 March 2015 07:07 Go to previous messageGo to next message
mlee (Kerio)
Messages: 211
Registered: October 2012
Location: Sydney
I can replicate this, I will get back to you when I have more info.

M. 19998


PTSD. BP. OCD. ASPD. BPD. Certified.
Re: Can´t connect iTunes Update Server [message #119912 is a reply to message #119756] Wed, 11 March 2015 00:35 Go to previous message
mlee (Kerio)
Messages: 211
Registered: October 2012
Location: Sydney
Got some really good help and I got some info for you.

The first hint of the issue is that the user did not login:
{http_handler} [ 5727 ] User not found for IP 172.20.0.11 in request_read_header()

Normally, HTTP proxy should reply with HTTP status code 407 Unauthorized, but it failed in this situation. Digging deeper, it is because iTunes used FQDN (ending with dot) in request URI/Host header. Without last dot, 407 is returned by the proxy;

Then when a user is manually logged in using a web browser, request failed on DNS lookup:
{http_handler} [ 512 ] DNS lookup failed

Again, it is caused by FQDN in request URI.

And if the last dot from request URI/Host header is removed, HTTP proxy failed to connect with following message in the log:
{http_handler} S 513 PROXY https_connect_handler(): connect error 110

Up to this point, unfortunately we know that there is no immediate solution on this. (A bug report was created.) 15492

The workaround at this point is to not use non-transparent proxy I guess.

M.

Edit: Removed some wrong info.


PTSD. BP. OCD. ASPD. BPD. Certified.

[Updated on: Wed, 11 March 2015 00:44]

Report message to a moderator

Previous Topic: Kerio Control Box
Next Topic: DHCP Status Info
Goto Forum:
  


Current Time: Fri Feb 03 15:35:55 CET 2023

Total time taken to generate the page: 0.02128 seconds