Is www.mysqueezebox.com being replaced by www.squeezenetwork.com?

[sgmlaw]

Has www.mysqueezebox.com been replaced by www.squeezenetwork.com? More importantly, is the latter a legitimate site and ok to log into?

The www.mysqueezebox.com site now delivers a certificate error on its log in page. I have used that web address for many years without thinking about it much.

I won't log into a site with a certificate error for security reasons.

But looking at the certificate data, the certificate appears to have been issued to "www.squeezenetwork.com".

Entering www.squeezenetwork.com brings up an apparent mirror web site. I do know that squeezenetwork.com was changed to "mysqueezebox" some time ago. So perhaps this is just a certificate renewal flub.

But I am reluctant to log into it until getting confirmation that it is (still) a legitimate site.

[mherger]

> Has www.mysqueezebox.com been replaced by www.squeezenetwork.com? More

No, squeezenetwork.com had been replaced with mysqueezebox.com about 10
years ago :-).

> importantly, is the latter a legitimate site and ok to log into?

Yes.

> The original www.mysqueezebox.com now delivers a certificate error on
> its log in page. I have used that web address for many years without
> thinking about it much.

Are you using with or without www prefix? The certificate is ok on my
end, but would complain if you were using https://mysqueezebox.com
without the www prefix.

> I won't log into a site with a certificate error for security reasons.

Hehe... and we only added support for this very forum about a week ago.

> But looking at the certificate data, the certificate appears to have
> been issued to "www.squeezenetwork.com".

If you scroll down that window you'll see that mysqueezebox.com is in
there, too.

> Entering www.squeezenetwork.com brings up an apparent mirror web site.
> But I am reluctant to log into it until getting confirmation that it is
> a legitimate site.

It's the same web site, just it's legacy domain name still pointing there.

--

Michael

[SuperQ]

Yes, it looks like the Let's Encrypt cert issued on 2018-03-04 is missing "mysqueezebox.com", "squeezenetwork.com", and "squeezenetwork.net" from the SAN list. Redirects to "www..." for these will fail since the cert is invalid for those names.

[mherger]

> Yes, it looks like the Let's Encrypt cert issued on 2018-03-04 is
> missing "mysqueezebox.com", "squeezenetwork.com", and
> "squeezenetwork.net" from the SAN list. Redirects to "www..." for these
> will fail since the cert is invalid for those names.

What browser? I'm getting thumbs up padlocks in FF, Chrome, Safari.

--

Michael

[sgmlaw]

. . .
It's the same web site, just it's legacy domain name still pointing there.

--

Michael

Thanks Michael.

Based on what you wrote, it looks to be a flubbed certificate issuance. Mysqueezebox is definitely missing from the certificate.

I'll just start using the squeezenetwork address until the certificate is corrected.


And now . . . mysqueezebox is suddenly working under a valid certificate. That was fast. Thanks again.