White Screen. Connection Timed Out

[zealous adder]

Game Version: 3.3.0
Grasscutter version: 1.4.6-70e448d8
Proxy type: Cultivation
Cultivation version: 1.0.10

I setup the server using grasscutter-docker from #resources: #resources message
(To make it work I modified the scripts to download and unzip the Genshin 3.3 Resources from the latest source, and also changed the config.json to be the default generated by the grasscutter jar -- notably disabling experimental real password)

When I login, I get a Connection Timed Out error.
I'm not sure what the issue could be.

Server log:

2023-01-22 20:12:12 03:12:12 <INFO:Grasscutter> Game version: 3.3.0
2023-01-22 20:12:12 03:12:12 <INFO:Grasscutter> Grasscutter version: 1.4.6-70e448d8
2023-01-22 20:12:12 03:12:12 <INFO:ResourceLoader> Loading resources...
2023-01-22 20:12:14 03:12:14 <INFO:ResourceLoader> Finished loading resources.
2023-01-22 20:12:14 03:12:14 <INFO:Language> Loading cached 'TextMaps'...
2023-01-22 20:12:15 03:12:15 <ERROR:GachaBanner> Redundant field found ... (cut due to discord msg length limit)
2023-01-22 20:12:15 03:12:15 <INFO:HttpServer> [Dispatch] Dispatch server started at 127.0.0.1:443
2023-01-22 20:12:15 03:12:15 <INFO:GameServer> Grasscutter is FREE software. If you have paid for this, you may have been scammed. Homepage: https://github.com/Grasscutters/Grasscutter
2023-01-22 20:12:15 03:12:15 <INFO:GameServer> Game Server started at 127.0.0.1:22102
2023-01-22 20:12:15 03:12:15 <INFO:Grasscutter> Done! For help, type "help"
03:12:40 <INFO:RegionHandler> [Dispatch] Client 172.21.0.1 request: query_region_list
03:12:56 <INFO:DefaultAuthenticators$PasswordAuthenticator> [Dispatch] Client 172.21.0.1 logged in as 10002.
03:12:57 <INFO:DispatchHandler> [Dispatch] Client 172.21.0.1 is trying to log in.
03:12:57 <INFO:DefaultAuthenticators$SessionKeyAuthenticator> [Dispatch] Client 172.21.0.1 succeed to exchange combo token.
03:12:57 <INFO:DispatchHandler> [Dispatch] Client 172.21.0.1 is trying to log in.
03:12:57 <INFO:RegionHandler> Client 172.21.0.1 request: query_cur_region/os_usa

Game version shown in client (confirming game version)

I tried creating a new account and logging into the new account, but still get a connection timed out.

I did install the RSAPatch and can confirm it is working. (A cmd window opens with the game. It defaults to using grasscutter keys)

[short steeple]

You're not reaching the game server, considering you are using a modified docker setup that means you likely have an issue somewhere in the connection settings or the game server is inaccessible

[zealous adder]

So the game server and the login server are separate? I can successfully login but just can't get into the game.

[short steeple]

Dispatch and game server are separate

The normal server runs in hybrid mode, where the dispatch and game server are hosted on the same host, but they are still accessed differently. Dispatch is on port 443, game server is on 22102

[zealous adder]

I see.

[short steeple]

Dispatch directs users to the game server specified in their selected region. In a normal case, that is just the same host address since there are no other regions

Unless you edited that, in which case you're being directed to the region in your config

Which likely won't be working unless it is the same as where dispatch is hosted

[zealous adder]

These are connection settings and the ports shown in docker.
In the config.json I have

    "game": {
      "bindAddress": "0.0.0.0",
      "bindPort": 22102,
      "accessAddress": "127.0.0.1",
      "accessPort": 0,
...
    "dispatch": {
      "regions": [],
      "defaultName": "Grasscutter",
      "logRequests": "NONE"
    }

[oblique widget]

i have the exact same issue

[short steeple]

You're running a docker container of grasscutter?

[oblique widget]

i dont think so

im having issue exactly with the grasscutter

i think

[short steeple]

Right. You don't actually have this same error. Read the most recent messages in #1025543438604710018

[oblique widget]

i will let u know if solved, thx

[short steeple]

Your ports are all forwarded/accessible? Need 80, 443, 8888, 22102

[zealous adder]

I did not port forward. I need to port forward even though I'm running and connecting locally?

[short steeple]

Being local doesn't necessarily mean the ports are open/accessible so you should ensure that they are.
If you keep having issues I'd suggest ensuring you can get grasscutter running and working/accessible outside of docker first, then use a docker setup. Also, if you want to use docker I'd suggest using Yuuki's DockerGS instead https://github.com/YuukiPS/DockerGS

[zealous adder]

Alright, I'll see what I can do, and try DockerGS

[zealous adder]

Ah, I figured out the issue.

In the docker-compose.yml the ports specified for grasscutter are:

  grasscutter:
...
    ports:
      - 80:80
      - 443:443
      - 8888:8888
      - 22102:22102

But not specifying a protocol will default it to TCP

22102 needs to use UDP

  grasscutter:
...
    ports:
      - 80:80
      - 443:443
      - 8888:8888
      - 22102:22102/udp

Works now. Thanks @short steeple !

I couldn't get YuukiPS's DockerGS working though.

[short steeple]

No problem, that's unfortunate I believe the resources download for it may still be a bit messed up but if you were to add the res manually, then the rest of it is significantly more 'ahead' than normal grasscutter. Since it has a mix of hartie's questing fork and some other improvements/built in stuff, but really is just beneficial to some open-world and questing stuff, other QOL stuff