Now that's interesting. Note that the failed nslookup looked v6-ish. I wonder if Cox is doing some v6 stuff that I don't know about!

-----Original Message----- From: stunnel-users [mailto:[email protected]] On Behalf Of Vincent Deschenes Sent: Thursday, January 18, 2018 1:17 PM To: [email protected] Subject: Re: [stunnel-users] Re (2): Problems with stunnel and cox.net on Windows 7

From my experience, this relates to IPv4 vs IPv6.

127.0.0.1 is explicitly V4. While localhost can be V6.

Vincent Deschenes

-----Original Message----- From: stunnel-users [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, 18 January 2018 1:08 PM To: [email protected] Subject: [stunnel-users] Re (2): Problems with stunnel and cox.net on Windows 7

From: "Phil Smith III" [email protected] Date: Thu, 18 Jan 2018 12:47:47 -0500

while the output= wasn't accepted (it said it wasn't valid there),

Does the file exist? If not, can stunnel create it? Can you read it with an editor. Can you write into it interactively?

changing 127.0.0.1 to localhost seems to have fixed it!

What does "nslookup localhost" report?

Regards, ... P.