Certificate not up to date?

[Shade]

Still not working properly: https://www.ut99.org

Unbenannt.png

Unbenannt.png

It should work. I am clueless right now.

[Barbie]

The host name

Code: Select all

www.ut99.org

cannot be resolved to an IP address:

Code: Select all

# nslookup www.ut99.org 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

** server can't find www.ut99.org: NXDOMAIN

[Feralidragon]

Yeah.

Before, it was just an HTTPS error, saying that the certificate was not configured properly or at all for www.ut99.org.
But now, this domain does not even resolve to anything...

[JackGriffin]

So for us non-web savvy people is this the beginning of the end? I mean the fact it's just not getting fixed and doesn't seem to be a priority is a bit disturbing. Lack of competition builds complacency I guess. I already see most of the discussion moving away from here and onto discord, a good hard nudge could really ghost this place. About all that gets put here now is screenshots and files. If someone makes that same channel it could end the use for that too. That would be a shame.

[Chamberly]

Seem to be working now on my end. Including it automatically change the http to https.

[sektor2111]

This is what I have right now...

[attachment=0]Connection_Less_Secured.PNG[/attachment]

Perhaps my "BugZilla" it's old and doesn't support more news (which I never asked).

[Feralidragon]

ut99.org is working guys, and has been working since the start, that's not the problem.
The problem is in its www variant: www.ut99.org .

@JackGriffin: Don't worry, it's nothing like that.
It's just that the www variant of the host (www.ut99.org) has issues, and it's a problem even because many links posted in other forums and even in google use the www variant.
The problem is probably just the DNS entry itself (which is either non-existent right now or is badly configured) coupled with the host configuration (where you set up the certificate and all), but that's something that only Shade can look at.

[papercoffee]

The problem is probably just the DNS entry itself (which is either non-existent right now or is badly configured) coupled with the host configuration (where you set up the certificate and all), but that's something that only Shade can look at.

That's exactly the reason.
We tried to fix it by adding the www variant as an A record into the DNS entries. But as it seems the gandy.net name-server doesn't like this.
We changed it back yesterday after we received the failure of "server not found" but DNS changes take up to 24-48 ours to be effective.

We will fix this problem via .htaccess now.

[Barbie]

This is what I have right now...

The message shown is

Parts of this page are not secure

PartsNotSecure.jpg

Take for example the image in a user's signature:

Code: Select all

http://cache.www.gametracker.com/server_info/198.12.77.35:7777/b_350_20_EB09A6_5F0396_FFFFFF_000000.png

Then you have elements on one web page where the transport is encrypted (https) and unencrypted (http). That is what your browser tries to tell.

[sektor2111]

Yes, but when certificate is expired a sudden warning shows up instantly asking me if I want to continue browsing or not, and then I have to add site as exception.

[Feralidragon]

Just want to shout out that the www.ut99.org is not available at all, and the site is been painfully slow at times.
Many folks are starting being unable to access this site at all.

[sektor2111]

Lol, it's very TRUE. WWW has no purpose. Simply

• https://ut99.org

will open forum.

[attachment=0]no_www.PNG[/attachment]

[Chamberly]

Yup, the ut99.org do fine while the http://www.ut99.org link does not give me anything.

A screenshot showing basically what it tells me.

[Gustavo6046]

Can't you use a redirect?