Hello! Does anybody have a way to get the GDB HTML to load correctly on google chrome? Mine has been jacked up for some time now, rendering the GDB largely unusable for me. And no I don't want to switch browsers.
https://gdb.armageddon.org/index.php/topic,56006.0.html
Yes, staff know about it, and they are still working on it.
Are you going to https or http ?
I had a problem with the html not loading when the https stopped working. If this is your problem, I tried a few things (I don't remember which fixed it) and then bookmarked the functioning page.
(During any of these steps if you get the unsecure message, you have to go to advanced and confirm.)
1.) Go to the mainpage http://www.armageddon.org/ (http://www.armageddon.org/) and connect to the GDB through the community dropdown.
2.) Type in the address manually (both https and http versions). https://gdb.armageddon.org/index.php (https://gdb.armageddon.org/index.php) http://gdb.armageddon.org/index.php (http://gdb.armageddon.org/index.php)
3.) You may need to clear your cache https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DDesktop&hl=en (https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DDesktop&hl=en)
Quote1.) Go to the mainpage http://www.armageddon.org/ and connect to the GDB through the community dropdown.
This works for me. Then it works fine for some indeterminate amount of time. Then I do it again.
I go to https://www.armageddon.org/ and use the link under Community Links on the main page. I've been doing that for a couple of years and works great every time.
The GDB looks like shit on Chrome and I get this message each time I go to armageddon.org
Your connection is not fully secure
This site uses an outdated security configuration, which may expose your information (for example, passwords, messages, or credit cards) when it is sent to this site.
NET::ERR_SSL_OBSOLETE_VERSION
This isn't going to get you many new players.
I get the error message once every few days. Not sure why it works most of the time, but doesn't work once in awhile, but that's what it does with me in any case. I'm using Chrome too.
Quote from: Malken on September 17, 2020, 05:17:02 PM
The GDB looks like shit on Chrome and I get this message each time I go to armageddon.org
Your connection is not fully secure
This site uses an outdated security configuration, which may expose your information (for example, passwords, messages, or credit cards) when it is sent to this site.
NET::ERR_SSL_OBSOLETE_VERSION
This isn't going to get you many new players.
I get that when I'm using Chrome on my phone (haven't tried on my computer as I'm using Firefox). It makes the game seem skeevy as heck...which isn't good!
I have got these errors for a while, I kept assuming they would update whatever is causing them, but I don't know if it's an easy fix.
Quote from: Kyviantre on September 18, 2020, 05:13:06 AM
Quote from: Malken on September 17, 2020, 05:17:02 PM
The GDB looks like shit on Chrome and I get this message each time I go to armageddon.org
Your connection is not fully secure
This site uses an outdated security configuration, which may expose your information (for example, passwords, messages, or credit cards) when it is sent to this site.
NET::ERR_SSL_OBSOLETE_VERSION
This isn't going to get you many new players.
I get that when I'm using Chrome on my phone (haven't tried on my computer as I'm using Firefox). It makes the game seem skeevy as heck...which isn't good!
I agree that gaining bran new player interest might be hampered by the sites issue with hTTPS and the certification not being secure at present.
Quote from: Malken on September 17, 2020, 05:17:02 PM
The GDB looks like shit on Chrome and I get this message each time I go to armageddon.org
Your connection is not fully secure
This site uses an outdated security configuration, which may expose your information (for example, passwords, messages, or credit cards) when it is sent to this site.
NET::ERR_SSL_OBSOLETE_VERSION
This isn't going to get you many new players.
That's only the GDB, it's not the rest of the website. The Armageddon.org website works just fine. I didn't even know the GDB existed when I first started playing. It was a couple of months until I realized there was a forum at all.
If they post the discord channel on the game's home page, then they will be able to get "live" updates from staff and players.
Quote from: Lizzie on September 18, 2020, 03:45:09 PM
Quote from: Malken on September 17, 2020, 05:17:02 PM
The GDB looks like shit on Chrome and I get this message each time I go to armageddon.org
Your connection is not fully secure
This site uses an outdated security configuration, which may expose your information (for example, passwords, messages, or credit cards) when it is sent to this site.
NET::ERR_SSL_OBSOLETE_VERSION
This isn't going to get you many new players.
That's only the GDB, it's not the rest of the website. The Armageddon.org website works just fine. I didn't even know the GDB existed when I first started playing. It was a couple of months until I realized there was a forum at all.
If they post the discord channel on the game's home page, then they will be able to get "live" updates from staff and players.
This is fine and all, but the issue has lasted quite a while. I posted in Ask the Staff about this issue more than 30 days ago. I posted because people were asking me to check the GDB for them because of how broken it has been. I like to be helpful, but all us players can do is squabble and bail water when we need the ship masters to fix the leaking hull.
I followed the solution presented in the below link and it has worked for me.
https://support.google.com/chrome/thread/60199452?hl=en
Quote from: DrunkenSalarr on September 18, 2020, 04:19:42 PM
I followed the solution presented in the below link and it has worked for me.
https://support.google.com/chrome/thread/60199452?hl=en
Thanks, per original post this is a workaround.
Workarounds are tedious and browser specific. The first person to ask me to check the GDB for them was a Software Engineer.
I am one as well and would like to emphasize another glaring technical issue here; the lack of an SSL/https redirect. It is not only a best practice, a change that would inspire confidence in new players, but it is also likely to prevent asset issues like what we are seeing with the site CSS.
Regardless, OP and other folks are right to raise it to staff's attention that workarounds (bailing water) are needed at present.