Shuffle iT Forum

Dominion => General Discussion => Topic started by: Brucifer on 05 September 2023, 03:52:38 AM

Title: I can't be the only one suffering from lack of servers
Post by: Brucifer on 05 September 2023, 03:52:38 AM
My access to other web sites is fast as ever. Dominion can take a minute just to load the game, and then fails to load images, leading to a partial user interface throughout the game, or just loads images really slowly. Often it disconnects, and then seems to chide me, offering the chance to disconnect and resign, as if its problems were my fault.
Title: Re: I can't be the only one suffering from lack of servers
Post by: Ingix on 05 September 2023, 06:43:18 PM
Slow or not loading pictures seem to happen very sporadically but may of course depend on usage times and location in the world. The developer has created a test server that tries to address the issue: https://webserver.dominion-online.com/

The message that it has detected a disconnect is inform the player, in case the reason is on their end (which it isn't for you).
Title: Re: I can't be the only one suffering from lack of servers
Post by: Brucifer on 17 January 2024, 02:51:38 AM
So tonight, it's the Websocket server not answering. On the JavaScript console, I see:

connection.js:14 WebSocket connection to 'wss://metaserver-new.dominion-online.com/' failed
failed:
(stack dump)
165: Metaserver connection error (id: 0, currentId: 0). Event {isTrusted: true, type: 'error', target: WebSocket, currentTarget: WebSocket, eventPhase: 2, ...}isTrusted: truebubbles: falsecancelBubble: falsecancelable: falsecomposed: falsecurrentTarget: WebSocket {url: 'wss://metaserver-new.dominion-online.com/', readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, ...}defaultPrevented: falseeventPhase: 0returnValue: 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: 844.6999999992549type: "error"[[Prototype]]: Event
raven-3.7.0.min.js:49
Title: Re: I can't be the only one suffering from lack of servers
Post by: Brucifer on 17 January 2024, 02:54:27 AM
Traceroute says I'm getting three hops out of Comcast's network and not reaching the host.

traceroute to metaserver-new.dominion-online.com (54.212.185.49), 30 hops max, 60 byte packets
 1  OpenWrt.lan (192.168.1.1)  10.283 ms  10.575 ms  10.555 ms
 2  192.168.10.1 (192.168.10.1)  10.505 ms  10.486 ms  10.824 ms
 3  96.120.95.1 (96.120.95.1)  18.794 ms  19.126 ms  20.747 ms
 4  po-307-1239-rur101.pinole.ca.sfba.comcast.net (68.85.191.205)  19.081 ms  19.635 ms  20.296 ms
 5  be-224-rar01.pinole.ca.sfba.comcast.net (162.151.78.185)  31.160 ms  31.679 ms  31.660 ms
 6  be-298-ar01.santaclara.ca.sfba.comcast.net (162.151.86.57)  31.640 ms  23.653 ms  17.262 ms
 7  be-36341-cs04.sunnyvale.ca.ibone.comcast.net (96.110.41.77)  29.066 ms be-36321-cs02.sunnyvale.ca.ibone.comcast.net (96.110.41.69)  29.055 ms be-36331-cs03.sunnyvale.ca.ibone.comcast.net (96.110.41.73)  29.037 ms
 8  be-3211-pe11.529bryant.ca.ibone.comcast.net (96.110.33.86)  29.023 ms  29.005 ms be-3111-pe11.529bryant.ca.ibone.comcast.net (96.110.33.82)  24.781 ms
 9  66.208.232.62 (66.208.232.62)  26.237 ms 50.242.150.122 (50.242.150.122)  47.548 ms 66.208.232.58 (66.208.232.58)  26.197 ms
10  52.93.141.223 (52.93.141.223)  58.306 ms 52.93.141.155 (52.93.141.155)  58.335 ms 52.93.141.133 (52.93.141.133)  26.622 ms
11  54.240.243.17 (54.240.243.17)  26.610 ms 150.222.111.5 (150.222.111.5)  26.117 ms 54.240.243.81 (54.240.243.81)  36.892 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
Title: Re: I can't be the only one suffering from lack of servers
Post by: Brucifer on 17 January 2024, 02:57:03 AM
That last address is in Amazon Web Services, so naively I guess there's something wrong with your AWS server tonight.