SSL connection not working for some people?

Jim Moe wrote:
> Pupkin wrote:
>> It looks like it might just be a case of extremely slow DNS propagation
>> (4 days!) -- as of the two replies in this group, one couldn't hit it
>> and the other could.
>>
> The host resolves fine.
>> host autodepot.merchantsecure.com
> autodepot.merchantsecure.com = 64.34.120.63
>
> There is no HTTP server running on either port 80 or 443. Or on any
> other port AFAICT.
>

Actually, there is, Joe. I can connect to it just fine.

Both ports are active, although Port 80 just puts up a message that you
need to be using https.

Very strange.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

In article <_7CdnZPm2NXaQ9fbnZ2dnUVZ_rPinZ2d@comcast.com>,
jstucklex@attglobal.net says...
> Jim Moe wrote:
> > Pupkin wrote:
> >> It looks like it might just be a case of extremely slow DNS propagation
> >> (4 days!) -- as of the two replies in this group, one couldn't hit it
> >> and the other could.
> >>
> > The host resolves fine.
> >> host autodepot.merchantsecure.com
> > autodepot.merchantsecure.com = 64.34.120.63
> >
> > There is no HTTP server running on either port 80 or 443. Or on any
> > other port AFAICT.
> >
>
> Actually, there is, Joe. I can connect to it just fine.
>
> Both ports are active, although Port 80 just puts up a message that you
> need to be using https.
>
> Very strange.
>

Surprise, surprise: their tech support told me for days nothing was
wrong, and then 10 minutes after another help ticket on the subject it
was magically working.

Thanks for confirming that the issue did not just lie in my own
incompetence!

Pupkin wrote:
> In article <_7CdnZPm2NXaQ9fbnZ2dnUVZ_rPinZ2d@comcast.com>,
> jstucklex@attglobal.net says...
>> Jim Moe wrote:
>>> Pupkin wrote:
>>>> It looks like it might just be a case of extremely slow DNS propagation
>>>> (4 days!) -- as of the two replies in this group, one couldn't hit it
>>>> and the other could.
>>>>
>>> The host resolves fine.
>>>> host autodepot.merchantsecure.com
>>> autodepot.merchantsecure.com = 64.34.120.63
>>>
>>> There is no HTTP server running on either port 80 or 443. Or on any
>>> other port AFAICT.
>>>
>> Actually, there is, Joe. I can connect to it just fine.
>>
>> Both ports are active, although Port 80 just puts up a message that you
>> need to be using https.
>>
>> Very strange.
>>
>
> Surprise, surprise: their tech support told me for days nothing was
> wrong, and then 10 minutes after another help ticket on the subject it
> was magically working.
>
> Thanks for confirming that the issue did not just lie in my own
> incompetence!

IOW they fixed their broken firewall... :-)

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================