Workaround for the dirtgame.com webpage not loading in Firefox

[green-K-]

Firefox doesn't open the page since its using an old TLS encryption. This method adds an exception for the page and lets you open it in Firefox.

1. Open about:config
2. Paste security.tls.insecure_fallback_hosts into the search bar
3. Right-click on security.tls.insecure_fallback_hosts and click on edit.
4. Paste www.dirtgame.com,accounts.codemasters.com
It shoud look like this now: http://i.imgur.com/jqMMKIb.png

Now you are able to load the page and log into your account. However I recommend the webmaster to update to a more recent version of the TLS encryption.

Edit: typos

[dgeesio & ronMctube]

the fire fox issue is annoying especially if you follow DiRT media often. "here check this new info " clicks on link broken pg ;( .

[Brigitte Bordeaux]

It works! Thanks

[kobeshow]

nice workaround !
Codies have stated that they have some issues with their servers and Firefox doesn't seem to like that, they are working on it.

[GRIM J1GSAW]

I have same problem with Chrome browser. Where could I find that same "config" to adjust it?

[green-K-]

Origineel geplaatst door red Larva™:

I have same problem with Chrome browser. Where could I find that same "config" to adjust it?

Open about:flags, search for #ssl-version-min and choose TLS 1.0. http://i.imgur.com/IkaMMMu.png

[GRIM J1GSAW]

Thx!

[Sir Phil]

This didnt work for me :(

[euronate]

Origineel geplaatst door green-K-:

Origineel geplaatst door red Larva™:

I have same problem with Chrome browser. Where could I find that same "config" to adjust it?

Open about:flags, search for #ssl-version-min and choose TLS 1.0. http://i.imgur.com/IkaMMMu.png

This didn't work for me on Chrome unfortunately.. Still looking for a fix! Thanks for the attempt though!

[GRIM J1GSAW]

Mine worked once a while ago. Now not working at all...

[green-K-]

This fix is no longer needed on the most recent versions of Firefox and Chrome since the website uses now TLS 1.2. It's still not the most recent encryption but it should work without any problems. Tested on Firefox 38.0.5 and Chrome 43.0.2357.81.