We are doing SSL certificate verification using Chilkat. T-Mobile enforces IPV6 in iOS 10.2. SSL socket connection using Chilkat always fails for us on this particular operator / OS combination. However, when we open an HTTP connection from the same device to the server (also on IPV6), it seems to connect fine. Our server is not IPV6 ready, but i'm kind of curious why the http connection works fine on IPV6 and the socket does not.
Unable to connect: ChilkatLog: Connect_Socket: DllDate: Mar 6 2015 ChilkatVersion: 18.104.22.168 UnlockPrefix: AUGMENSocket Architecture: Little Endian; 64-bit Language: IOS Objective-C VerboseLogging: 0 objectId: 3 Connect_Socket: hostname: api.hostname.com port: 443 ssl: 1 maxWaitMs: 10000 socket2Connect: connect2: connectImplicitSsl: connectSocket: connect_ipv6_or_ipv4: socketErrno: 51 socketError: Network is unreachable --connect_ipv6_or_ipv4 --connectSocket --connectImplicitSsl ConnectFailReason: Connection rejected --connect2 --socket2Connect Failed. --Connect_Socket --Connect_Socket --ChilkatLog
Does anyone have insights on why this may be happening?
did you fix your issue already? I have same issue under tmobile,http fine but ftp not
We ended up using the CocoaAsync socket library instead of Chilkat for our needs and that fixed our problem. Not sure if that supports ftp though.
Your error log (LastErrorText) shows version 22.214.171.124. Did you test with the latest version of Chilkat (v126.96.36.199)?
If the problem is only with FTP w/ data transfers, then it's likely an issue with a firewall blocking the data connection.