Login  |  Register

Author Topic: "Server connection was refused or could not be established" on Razer Blade 13  (Read 631 times)

Offline Carl242

  • Newbie
  • *
  • Posts: 4
    • View Profile
I just got a new Razer Blade Stealth 13, and on this laptop, no matter which browser I use, I get "Server connection was refused or could not be established". It works on my old computer that i'm replacing. It works on my phone. I'm not sure if Razer has some sort of proprietary firewall that is installed by default that blocks Dominion, but I'm hoping someone here can shed some light.

What i've done:
- Restarted PC
- Tried Chrome, Chrome in Incognito Mode, Edge, Internet Exploder
- Cleared my cache
- Added dominion.games to trusted sites
- Opened up Port 443 inbound and outbound
- Turned off Windows Firewall altogether

Any tips would be greatly appreciated.

Here is the console log:
0: Opening metaserver connection (metaserver-new.dominion-online.com:443)
connection.js:14 WebSocket connection to 'wss://metaserver-new.dominion-online.com/' failed:
s.connect   @   connection.js:14
C.open   @   connection.js:14
(anonymous)   @   login-controller.js:203
(anonymous)   @   login-controller.js:206
invoke   @   angular.min.js:493
l.instance   @   angular.min.js:1152
p   @   angular.min.js:834
a   @   angular.min.js:769
(anonymous)   @   angular.min.js:762
(anonymous)   @   angular.min.js:816
r   @   angular.min.js:776
f   @   angular.min.js:829
(anonymous)   @   angular.min.js:3829
$digest   @   angular.min.js:1962
$apply   @   angular.min.js:2007
(anonymous)   @   page-display-controller.js:60
raven-3.7.0.min.js:49 81: Metaserver connection error (id: 0, currentId: 0).
Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}
raven-3.7.0.min.js:49 82: Metaserver connection closed (id: 0, currentId: 0).
CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}
raven-3.7.0.min.js:49 82: Close event code: 1006
raven-3.7.0.min.js:49 82: Close event string: CLOSE_ABNORMAL
raven-3.7.0.min.js:49 82: Meta Connection closed; game isn't connected so resetting

Online Ingix

  • Global Moderator
  • *****
  • Posts: 2707
    • View Profile
Thanks for the report and the console log.

What I'm seeing in the list of browsers is Internet Explorer, which AFAIK this site never worked with, and then 3 Chromium variants. Of course, it should work with them, but maybe you can try Firefox as well, which has another engine.

In the log, 2 lines jump out to me that likely contain more info:

> Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}
> CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}

It could be that you can click on those lines and they then expand to give you more info, which could be helpful, especially as they seem to refer to the reason why the connection was closed. If you can try that and post the results of the expansion, that would help.

As a last question, do you have similar problems when connecting to other websites from that laptop?

Best regards,
Ingix


Offline yellowfive

  • Newbie
  • *
  • Posts: 3
    • View Profile
Hello, I am having the same error connecting as the OP, but I'm trying to connect from a chromebook. I tried a similar set of steps except for trying other browsers, because ... Chromebook (stable channel fwiw).

Strangely, I've used this chromebook before. I believe I used it a week ago and it worked fine, only in the past day or two have I had an issue. Meanwhile chrome on my windows laptop seems to work fine.

My dev console shows the same logs as OP, but I can expand out the errors:


0: Opening metaserver connection (metaserver-new.dominion-online.com:443)
connection.js:14 WebSocket connection to 'wss://metaserver-new.dominion-online.com/' failed:
s.connect @ connection.js:14
C.open @ connection.js:14
(anonymous) @ login-controller.js:203
(anonymous) @ login-controller.js:206
invoke @ angular.min.js:493
l.instance @ angular.min.js:1152
p @ angular.min.js:834
a @ angular.min.js:769
(anonymous) @ angular.min.js:762
(anonymous) @ angular.min.js:816
r @ angular.min.js:776
f @ angular.min.js:829
(anonymous) @ angular.min.js:3829
$digest @ angular.min.js:1962
$apply @ angular.min.js:2007
(anonymous) @ page-display-controller.js:60
raven-3.7.0.min.js:49

313: Metaserver connection error (id: 0, currentId: 0).
  Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}
    bubbles: false
    cancelBubble: false
    cancelable: false
    composed: false
    currentTarget: WebSocket {url: "wss://metaserver-new.dominion-online.com/", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}
    defaultPrevented: false
    eventPhase: 0
    isTrusted: true
    path: []
    returnValue: true
    srcElement: WebSocket {url: "wss://metaserver-new.dominion-online.com/", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}
    target: WebSocket {url: "wss://metaserver-new.dominion-online.com/", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}
    timeStamp: 4863.400000000023
    type: "error"
    __proto__: Event
raven-3.7.0.min.js:49

319: Metaserver connection closed (id: 0, currentId: 0).
  CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}
    bubbles: false
    cancelBubble: false
    cancelable: false
    code: 1006
    composed: false
    currentTarget: WebSocket {url: "wss://metaserver-new.dominion-online.com/", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}
    defaultPrevented: false
    eventPhase: 0
    isTrusted: true
    path: []
    reason: ""
    returnValue: true
    srcElement: WebSocket {url: "wss://metaserver-new.dominion-online.com/", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}
    target: WebSocket {url: "wss://metaserver-new.dominion-online.com/", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}
    timeStamp: 4869
    type: "close"
    wasClean: false
    __proto__: CloseEvent
raven-3.7.0.min.js:49

319: Close event code: 1006
raven-3.7.0.min.js:49

320: Close event string: CLOSE_ABNORMAL
raven-3.7.0.min.js:49

325: Meta Connection closed; game isn't connected so resetting

Offline Carl242

  • Newbie
  • *
  • Posts: 4
    • View Profile
Thanks Ingix, this was very helpful. I downloaded Firefox and it worked--actually faster than i'm used to on Chrome on my other devices. So as long as I use FireFox i'm sorted!

In case it helps, here is the expansion of the console output on the lines you mentioned.

Code: [Select]
raven-3.7.0.min.js:49 0: Opening metaserver connection (metaserver-new.dominion-online.com:443)
dominion.games/:1 [DOM] Input elements should have autocomplete attributes (suggested: "current-password"): (More info: https://goo.gl/9p2vKq) <input type=​"password" name=​"password" placeholder=​"Password" ng-model=​"login.password" class=​"ng-pristine ng-untouched ng-valid ng-empty" aria-invalid=​"false">​
connection.js:14 WebSocket connection to 'wss://metaserver-new.dominion-online.com/' failed:
s.connect @ connection.js:14
C.open @ connection.js:14
(anonymous) @ login-controller.js:203
(anonymous) @ login-controller.js:206
invoke @ angular.min.js:493
l.instance @ angular.min.js:1152
p @ angular.min.js:834
a @ angular.min.js:769
(anonymous) @ angular.min.js:762
(anonymous) @ angular.min.js:816
r @ angular.min.js:776
f @ angular.min.js:829
(anonymous) @ angular.min.js:3829
$digest @ angular.min.js:1962
$apply @ angular.min.js:2007
(anonymous) @ page-display-controller.js:60
raven-3.7.0.min.js:49 15117: Metaserver connection error (id: 0, currentId: 0). Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}bubbles: falsecancelBubble: falsecancelable: falsecomposed: falsecurrentTarget: WebSocketbinaryType: "arraybuffer"bufferedAmount: 0extensions: ""onclose: ƒ (a)onerror: ƒ (a)onmessage: ƒ (e)onopen: ƒ (a)protocol: ""readyState: 3url: "wss://metaserver-new.dominion-online.com/"__proto__: WebSocketdefaultPrevented: falseeventPhase: 0isTrusted: truepath: []returnValue: truesrcElement: WebSocket {url: "wss://metaserver-new.dominion-online.com/", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}target: WebSocket {url: "wss://metaserver-new.dominion-online.com/", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …}timeStamp: 16011.800000000047type: "error"__proto__: EventAT_TARGET: 2BUBBLING_PHASE: 3CAPTURING_PHASE: 1NONE: 0bubbles: (...)cancelBubble: (...)cancelable: (...)composed: (...)composedPath: ƒ composedPath()currentTarget: (...)defaultPrevented: (...)eventPhase: (...)initEvent: ƒ initEvent()path: (...)preventDefault: ƒ preventDefault()returnValue: truesrcElement: WebSocketstopImmediatePropagation: ƒ stopImmediatePropagation()stopPropagation: ƒ stopPropagation()target: WebSockettimeStamp: 16011.800000000047type: "error"constructor: ƒ Event()AT_TARGET: 2BUBBLING_PHASE: 3CAPTURING_PHASE: 1NONE: 0arguments: nullcaller: nulllength: 1name: "Event"prototype: EventAT_TARGET: 2BUBBLING_PHASE: 3CAPTURING_PHASE: 1NONE: 0bubbles: (...)cancelBubble: (...)cancelable: (...)composed: (...)composedPath: ƒ composedPath()currentTarget: (...)defaultPrevented: (...)eventPhase: (...)initEvent: ƒ initEvent()path: (...)preventDefault: ƒ preventDefault()returnValue: (...)srcElement: (...)stopImmediatePropagation: ƒ stopImmediatePropagation()stopPropagation: ƒ stopPropagation()target: (...)timeStamp: [Exception: TypeError: Illegal invocation
    at Event.r (<anonymous>:1:83)]type: [Exception: TypeError: Illegal invocation
    at Event.r (<anonymous>:1:83)]constructor: ƒ Event()Symbol(Symbol.toStringTag): "Event"get bubbles: ƒ bubbles()get cancelBubble: ƒ cancelBubble()set cancelBubble: ƒ cancelBubble()get cancelable: ƒ cancelable()get composed: ƒ composed()get currentTarget: ƒ currentTarget()get defaultPrevented: ƒ defaultPrevented()get eventPhase: ƒ eventPhase()get path: ƒ path()get returnValue: ƒ returnValue()set returnValue: ƒ returnValue()get srcElement: ƒ srcElement()get target: ƒ target()get timeStamp: ƒ timeStamp()get type: ƒ type()__proto__: Object__proto__: ƒ ()[[Scopes]]: Scopes[0]Symbol(Symbol.toStringTag): "Event"get bubbles: ƒ bubbles()get cancelBubble: ƒ cancelBubble()set cancelBubble: ƒ cancelBubble()get cancelable: ƒ cancelable()get composed: ƒ composed()get currentTarget: ƒ currentTarget()get defaultPrevented: ƒ defaultPrevented()get eventPhase: ƒ eventPhase()get path: ƒ path()get returnValue: ƒ returnValue()set returnValue: ƒ returnValue()get srcElement: ƒ srcElement()get target: ƒ target()get timeStamp: ƒ timeStamp()get type: ƒ type()__proto__: Object
raven-3.7.0.min.js:49 15117: Metaserver connection closed (id: 0, currentId: 0). CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}
raven-3.7.0.min.js:49 15117: Close event code: 1006
raven-3.7.0.min.js:49 15117: Close event string: CLOSE_ABNORMAL
raven-3.7.0.min.js:49 15117: Meta Connection closed; game isn't connected so resetting

Apologies for the lack of nesting - i'm not that savvy with chrome output/text editing :| If you need me to dig in any further don't hesitate to point me in the right direction. I hope this helps!

Offline bill68

  • Newbie
  • *
  • Posts: 1
    • View Profile
Same problem for me. I've been using Chrome on this PC, playing dominion, for over a year. Just today (haven't played in a week or two) I tried to log in and got this error message. Switching to Firefox fixed the problem, but I hardly every use FF so it would be great to fix the bug so Chrome works again.

Online Ingix

  • Global Moderator
  • *****
  • Posts: 2707
    • View Profile
Could you post the version number of Chrome you are using? It can be found clicking on the 3-dots menu in the upper right of the browser, then "Help", then "About Google Chrome".

Up to now the number of reports is very small, unlike last time Chrome broke some feature that resulted in many reports for something that was not that drastic. I'm 99.9% sure that the code was not changed and I'll ask again if any configuration changes were made, like switching a server for another one, or something similar.

So my current hypothesis is that either a configuration change occured with the servers that may have broken things for you, or something in Chrome changed that only affects a few people. But for the latter part to consolidate, I need to find out what version you are using, so I can find out what changed to earlier Chrome versions.

Offline yellowfive

  • Newbie
  • *
  • Posts: 3
    • View Profile
My Chrome version is Version 91.0.4472.114 (Official Build) (64-bit)

Again, this is a Chromebook. I actually did install the Firefox android app and ran it and the game worked, so... I don't really have words for this.

Google Chrome   91.0.4472.114 (Official Build) (64-bit)
Revision   4bb19460e8d88c3446b360b0df8fd991fee49c0b-refs/branch-heads/4472@{#1496}
Platform   13904.66.0 (Official Build) stable-channel nami
Firmware Version   Google_Nami.10775.123.0
Customization ID   sona
ARC   7441046
JavaScript   V8 9.1.269.36
User Agent   Mozilla/5.0 (X11; CrOS x86_64 13904.66.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36

Offline Carl242

  • Newbie
  • *
  • Posts: 4
    • View Profile
Version 91.0.4472.114 (Official Build) (64-bit)

Online Ingix

  • Global Moderator
  • *****
  • Posts: 2707
    • View Profile
Thanks @Carl242, @yellowfive for the info, so we are all using the same browser version, not something too old or a beta version.

Unfortunately all that emerges now is that the latest Chrome updates seems to cause some problems for some players, and apparently something on iPads, though it's less clear there.

Offline yellowfive

  • Newbie
  • *
  • Posts: 3
    • View Profile
I just tried again from my chromebook and it worked. I don't know if anything changed on the backend. Thanks.

Offline Carl242

  • Newbie
  • *
  • Posts: 4
    • View Profile
It is fixed! And I've never seen it log in so fast on Chrome.  8)

Online Ingix

  • Global Moderator
  • *****
  • Posts: 2707
    • View Profile
Thanks for the replies!

As far as I'm aware nothing was done on the servers, except fixing the "rating not updating on the in-game leaderboard", and it seems unlikely this had something to do with it.