Working from here, on what I believe is an FX connection. Also working over Skinny 4G.

That exact link works? Not the www, not the https, that exact link? It doesn't work in IE/Firefox/Chrome here. I get "failed to connect" using webpagetest.org - one, two, three, but strangely #4 works. I guess it could be browser or ISP related.

 works fine here as well, on chrome, redirects from http to https

timmmay: That exact link works?

Yep, that exact link redirects to https://www in Firefox and Safari.

 No reported issues here. Checked on IE, Chrome and FF. Should forward to https://www.2degreesmobile.co.nz/

Is it still an issue? 

^POB

Operating system:  Windows XP

Browser:   Firefox 46

ISP:   2degreesbroadband

URL:  https://www.2degreesmobile.co.nz/

              works OK

URL:   http://www.2degreesbroadband.co.nz/

             fails "The connection was reset"

URL:   http://www.2dm.co.nz/

             fails "The connection was reset"

More;

URL:   https://www.2degreesbroadband.co.nz/

generates the following error;

      SSL_ERROR_BAD_CERT_DOMAIN

"The certificate is only valid for the following names: *.2degreesmobile.co.nz, 2degreesmobile.co.nz "

Interesting output when I curl from my AWS linux server below. First time it gave me a 301. Second time it told me I was blocked by Red Shield, a security service.

This could be related to Red Shield, they're a WAF who could return different responses based on any number of criteria. I know for sure that with Chrome, IE, or Firefox on a Vodafone connection I get nothing but an error in my browser with that URL. My AWS server seems to be blocked now.

Something a bit unusual is going on. Not really a problem, I just noticed it when I tried to access the site and it didn't forward me.

Try #1

curl -v http://2degreesmobile.co.nz/
* Trying 118.148.5.25...
* Connected to 2degreesmobile.co.nz (118.148.5.25) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.40.0
> Host: 2degreesmobile.co.nz
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 301 Moved Permanently
< Location: https://www.2degreesmobile.co.nz/
< Server: BigIP
* HTTP/1.0 connection set to keep alive!
< Connection: Keep-Alive
< Content-Length: 0
<
* Connection #0 to host 2degreesmobile.co.nz left intact

Try #2

curl https://www.2degreesmobile.co.nz/

Your request has been blocked for security purposes. Please try again or click below to report any issues.<br/><br/><a href="mailto:support@red-shield.net &subject=Web Security Support ID: 13492687696730966159">Click here to email security administrators</a><br/><br/>Alternatively please email support@red-shield.net with the subject line "Support ID 13492687696730966159" for assistance.

ObidiahSlope:

 

More;

 

URL:   https://www.2degreesbroadband.co.nz/

 

generates the following error;

 

      SSL_ERROR_BAD_CERT_DOMAIN

 

"The certificate is only valid for the following names: *.2degreesmobile.co.nz, 2degreesmobile.co.nz "

 

Yup, this one is fubar. Trying to use SSL certificate for 2degreesmobile.co.nz 

jarledb:

 

ObidiahSlope:

 

More;

 

URL:   https://www.2degreesbroadband.co.nz/

 

generates the following error;

 

      SSL_ERROR_BAD_CERT_DOMAIN

 

"The certificate is only valid for the following names: *.2degreesmobile.co.nz, 2degreesmobile.co.nz "

 

 

Yup, this one is fubar. Trying to use SSL certificate for 2degreesmobile.co.nz 

 

https://www.snap.co.nz is also in same boat - it's trying to use the SSL certificate for *.snap.net.nz

The error seems to have been resolved.

Yep, seems fine from my home connection.

The SSL errors have been there since the 2degrees + Snap merger and I have advised them many times about it.

ObidiahSlope:

 

The error seems to have been resolved.

 

First link posted is still not working for me on Chrome, FF or Edge.