Mac OS 9 Lives

Classic Mac OS Hardware => General Hardware Discussions => Topic started by: chrisNova777 on June 24, 2021, 04:17:29 AM

Title: "Future home of something quite cool."
Post by: chrisNova777 on June 24, 2021, 04:17:29 AM
"Future home of something quite cool.
If you're the site owner, log in to launch this site

If you are a visitor, check back soon."

some of you may or may not have noticed this landing page come up when trying to access the site from top level domain in a web browser.
i just noticed macos9lives.com is showing this on the landing page when u try to type in the domain name into chrome

i've been getting the same error from the same combination of using httpS (secure http)
and the domain name itself (oldschooldaw or macos9lives.com for example)

stil havent figured out how to get rid of this problem 100%
thinking of finally ditching godaddy..  because im pretty sure this is their passive agressive way of geting people to upgrade their SSL certificate ie: pay them an extra 100$ bucks a year

theres other hosts that give the SSL certificate for free by comparison
Title: Re: "Future home of something quite cool."
Post by: GaryN on June 24, 2021, 01:52:06 PM
i just noticed macos9lives.com is showing this on the landing page when u try to type in the domain name into chrome

I think the issue may be related to Chrome, Chris. I don't get anything like that using either Safari or Firefox.
Manually typing "HTTPS" will generate a security warning but that's all.
Title: Re: "Future home of something quite cool."
Post by: chrisNova777 on June 24, 2021, 02:42:22 PM
i just made it happen on OSX Lion using firefox version whatever (cant be bothered to check lol)
by typing in https://domain.com
it only seems to happen on the top level of the domain and using httpS protocol specifically
chrome seems to be the most common way to achieve that - the error definately is happening there most of all - but it is happening elsewhere aswell
it has to do with GODADDY + httpS + SSL certificate being set up "properly" according to their (godaddys) system
i was missing in my public_html top level dir a "index.html" which was making the problem worse then it is now (for me on my domain)
im also using GoDaddy - this problem ive only been aware of for the last week or so but i just now observed that it was affecting macos9lives.com site aswell as my own site hence the thread

the older browsers are set up to default to query the old http:// normal methods which dont seem to be affected by this
chrome is leading the charge to default to httpS i guess

https://macos9lives.com
https://oldschooldaw.com
http://macos9lives.com
http://oldschooldaw.com
https://www.macos9lives.com
https://www.oldschooldaw.com
http://www.macos9lives.com
http://www.oldschooldaw.com
https://www.macos9lives.com/index.html
https://www.oldschooldaw.com/index.html
http://www.macos9lives.com/index.html
http://www.oldschooldaw.com/index.html

out of all these urls only the ones with https show me the "future home of something quite cool" landing page


Quote
NET::ERR_CERT_COMMON_NAME_INVALID
Subject: *.prod.iad2.secureserver.net

Issuer: Starfield Secure Certificate Authority - G2

Expires on: Jan 14, 2022

Current date: Jun 24, 2021

lol "Starfield Secure Certificate Authority - G2" that sounds very "beam me up scotty" lol
Title: Re: "Future home of something quite cool."
Post by: GaryN on June 24, 2021, 06:57:02 PM
OK… I fingered it out. I was able to see the "something cool" splash by enabling "HTTPS-Only" mode in Firefox prefs.
That's probably selected by default. Deselecting it eliminates the redirect.
Safari (naturally) does not have a user-selectable HTTP/HTTPS mode selector.
I suspect if you look in Chrome prefs, you'll find it on - if it's selectable at all.

Amusingly, in Ffox, manually typing -HTTPS://macos9lives puts up a warning page telling you that horrible things will happen should you continue down the path to Hell you have selected. You can however, elect to go there anyway but that drops you at the "something cool" page and that's as far as you can get.
Title: Re: "Future home of something quite cool."
Post by: FBz on June 24, 2021, 08:31:28 PM
Dunno ‘bout no future home of something cool
as it is already the home of something very cool…
and has been… at least for now anyway.  :)
Title: Re: "Future home of something quite cool."
Post by: teroyk on June 26, 2021, 02:01:47 PM
Answer is in this attachment:
Title: Re: "Future home of something quite cool."
Post by: Knezzen on June 27, 2021, 07:08:21 AM
Chrome has deprecated http completely in one of the latest releases. A good idea would be to get a SSL certificate to offer both http and https for the same website (like we do for the garden and System 7 Today etc).
Title: Re: "Future home of something quite cool."
Post by: teroyk on July 03, 2021, 10:44:52 AM
Chrome has deprecated http completely in one of the latest releases. A good idea would be to get a SSL certificate to offer both http and https for the same website (like we do for the garden and System 7 Today etc).

Or deprecate Chrome.
Title: Re: "Future home of something quite cool."
Post by: chrisNova777 on September 19, 2021, 01:13:35 PM
so getting (paying extra for an) SSL certificate is the only way out of this basically?
Title: Re: "Future home of something quite cool."
Post by: DrNo7 on September 20, 2021, 10:39:37 PM
so getting (paying extra for an) SSL certificate is the only way out of this basically?

Getting a certificate is the requirement to activate HTTPS traffic. The paying part usually helps avoid the security verification error with self-signed certificates. But with the Let's Encrypt initiative, I think you can get a certificate for free in some circumstances (to be checked on their site).