Author Topic: Cannot connect to metaserver: Certificate Date Invalid (Read 2547 times)

Dwedit · « **on:** 19 December 2019, 01:47:49 AM »

I see this message: "Server connection was closed or could not be established"

And in the Console, I see this:

WebSocket connection to 'wss://metaserver.dominion-online.com/' failed: Error in connection establishment: net::ERR_CERT_DATE_INVALID
n.connect @ objects.js:1545

Edit: Also looks like the certificate for dominon.games has 5 days left on it.

perception312 · « **Reply #1 on:** 19 December 2019, 01:54:35 AM »

Same issue for me: "Server connection was closed or could not be established." Clicking Kick & Resign results in a pop up asking for my login credentials, but there is nowhere to input login credentials.

RainbowChalice · « **Reply #2 on:** 19 December 2019, 02:07:52 AM »

Having the same issue. Says cannot establish connection.

vinay · « **Reply #3 on:** 19 December 2019, 02:20:00 AM »

"Server connection was closed or could not be established" is the message I get when I go to dominion.games

uooq · « **Reply #4 on:** 19 December 2019, 02:28:20 AM »

Same problem.

Are you guys going to refund us because you were too lazy to refresh your certs (but you're NEVER late in expiring subscriptions).

abarn · « **Reply #5 on:** 19 December 2019, 02:51:36 AM »

Having the same issue....

southard0410 · « **Reply #6 on:** 19 December 2019, 03:13:44 AM »

Same Issue...

rjh · « **Reply #7 on:** 19 December 2019, 03:21:44 AM »

Same issue. I'm surprised Shuffle iT hasn't addressed it yet.

janigan · « **Reply #8 on:** 19 December 2019, 03:31:12 AM »

I've been trying to connect for hours - always same results - cannot connect to server!

aharte · « **Reply #9 on:** 19 December 2019, 03:36:04 AM »

same boat here

ewz · « **Reply #10 on:** 19 December 2019, 03:43:16 AM »

Same issue

holeypants · « **Reply #11 on:** 19 December 2019, 04:00:55 AM »

I'm also getting "Server connection was closed or could not be established." I don't see any complaints about the certificate in my Firefox console, though.

I've tried restarting the browser and clearing my cookies and cache.

Could Dominion Online please let us know if someone is looking into this issue?

Console log:

0: Opening metaserver connection (metaserver.dominion-online.com:443) raven-3.7.0.min.js:49:121

Firefox can’t establish a connection to the server at wss://metaserver.dominion-online.com/. dominion-webclient-body-1.4.6.min.js:17:26902

290: Metaserver connection error (id: 0, currentId: 0).
error { target: WebSocket, isTrusted: true, srcElement: WebSocket, currentTarget: WebSocket, eventPhase: 2, bubbles: false, cancelable: false, returnValue: true, defaultPrevented: false, composed: false, … }
raven-3.7.0.min.js:49:121

294: Metaserver connection closed (id: 0, currentId: 0).
close { target: WebSocket, isTrusted: true, wasClean: false, code: 1015, reason: "", srcElement: WebSocket, currentTarget: WebSocket, eventPhase: 2, bubbles: false, cancelable: false, … }
raven-3.7.0.min.js:49:121

296: Close event code: 1015 raven-3.7.0.min.js:49:121

296: Close event string: TLS_HANDSHAKE raven-3.7.0.min.js:49:121

297: Meta Connection closed; game isn't connected so resetting raven-3.7.0.min.js:49:121

Philothea · « **Reply #12 on:** 19 December 2019, 04:01:40 AM »

Ditto

strongpoet · « **Reply #13 on:** 19 December 2019, 04:06:08 AM »

same issue

Megas_Droungarios · « **Reply #14 on:** 19 December 2019, 04:34:13 AM »

Same issue here, too.

rob2e · « **Reply #15 on:** 19 December 2019, 04:36:49 AM »

I see a refund in our future? Or a free month?

eclecticactress · « **Reply #16 on:** 19 December 2019, 05:06:34 AM »

Same here (at 11:06PM EST)

twsb · « **Reply #17 on:** 19 December 2019, 05:14:27 AM »

I am having this same problem.

xtruffles · « **Reply #18 on:** 19 December 2019, 05:20:19 AM »

This is a known issue, Stef is working on it.

It has to do with SSL certificates, so if you want to get around it [for now], you can set your computers date to be yesterday. That will be temporary solution if you want to play right now.

eclecticactress · « **Reply #19 on:** 19 December 2019, 05:27:19 AM »

How do you reset your clock?

Stef · « **Reply #20 on:** 19 December 2019, 05:52:22 AM »

Sorry people, that took way longer then I wanted it to. Issue has been finally resolved now. Sorry to the people who tried to play in the last ~5 hours.

eclecticactress · « **Reply #21 on:** 19 December 2019, 05:03:14 PM »

It worked for a bit with the date change on my computer but now it doesn't work at all - with a past date or the current date.

Ingix · « **Reply #22 on:** 19 December 2019, 05:13:20 PM »

I just logged in and there was no problem.

I'd reset your clock to the current correct time, then maybe reboot the PC or at least close and reopen your browser. That should clear up any wrong time the browser may be using.

pablominion · « **Reply #23 on:** 07 February 2020, 08:40:43 PM »

I'm still seeing the issue (or a similar one) even after rebooting. It's been at least 3 days that I cannot access the system.

Ingix · « **Reply #24 on:** 07 February 2020, 11:58:09 PM »

Are you using Chrome? It seems the new version of that browser is giving these errors (not sure what the technical reason is and what can be done about it). You might try another browser in the mean time.

grep · « **Reply #25 on:** 11 February 2020, 01:52:41 AM »

Chrome Version 80.0.3987.87 (Official Build) (64-bit)

It was failing in metaserver, and now it fails to set up websocket connection on game start.

Stuck in "Reconnecting..."
Got this in debug console:
connection.js:10 WebSocket connection to 'wss://tokyo.dominion-online.com/' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID

Tried from different networks, most likely not a firewall

Ingix · « **Reply #26 on:** 11 February 2020, 04:10:06 PM »

@pablominion, @grep:

Since Chrome takes the root certificates from the OS, it looks like the used OS may play a role in wether someone is affected or not. Stef has for example also upgraded to Chrome Version 80.0.3987.87 (Official Build) (64-bit) and has no issues.

Could you state the OS's you are running under, with major version number if you know it (like Windows 10, or macOS Mojave).

pablominion · « **Reply #27 on:** 12 February 2020, 06:32:55 AM »

I have Linux (Debian), kernel version 5.2.17.

Ingix · « **Reply #28 on:** 13 February 2020, 11:32:56 AM »

At the moment it seems that Linux users are affected and upgrading Chrome to version 80.0.3987.100 has fixed the issue for 1 player and another player who 'started' with that version never had the problem.

So I'm cautiously optimistic that this may help.

It would be nice if affected players could post their results here, once they have switched.

pablominion · « **Reply #29 on:** 13 February 2020, 11:09:43 PM »

I've updated past version .100 and the issue seems resolved indeed. I could login, start a game and buy a card on my first turn. Console looks clean. Now, let's finish that game.

Ingix · « **Reply #30 on:** 14 February 2020, 09:07:58 AM »

Thanks for the reply <3

Let's hope those problems don't come up again.

fuse9 · « **Reply #31 on:** 31 March 2020, 05:04:29 PM »

With the new server, I can't connect to the game lobby anymore

KingTheodenII · « **Reply #32 on:** 31 March 2020, 05:32:56 PM »

I can't connect either. Now it says to refresh/retry for a new server, but when I do, I get the same error again.

Ingix · « **Reply #33 on:** 31 March 2020, 07:41:11 PM »

There was a short time when a "bad" version was sent oout. Players who had loaded that version were stuck if they couldn't delete their cache.

At around the time of the previous posting in this thread Stef made a change so that it should be corrected for everyone. A reload should be enough now. At least that's the hope

Stef · « **Reply #34 on:** 31 March 2020, 07:56:46 PM »

Quote from: Ingix on 31 March 2020, 07:41:11 PM

There was a short time when a "bad" version was sent oout. Players who had loaded that version were stuck if they couldn't delete their cache.

At around the time of the previous posting in this thread Stef made a change so that it should be corrected for everyone. A reload should be enough now. At least that's the hope

I'm afraid not. For most people it's enough, but for some people it's not.
My best guess at the moment is it has something to do with the very new name of the new server.
It's only ~10 hours old, and nameservers are only guaranteed to propagate this after 24 hours.