Direct IP connection returns to the menu

[dapper oasis]

Hello, when trying a direct IP connection, the game loads and then returns directly to the main game menu without any error message.

[pliant finch]

Thanks for the report! Direct IP connections might require you to do extra setup, depending on your home network configuration. Dedicated server settings can be configured via ServerDescription.json.

• Known Issue: When using Direct IP, if you enter an incorrect password or there is a version mismatch, the game will return you to the main menu without displaying an error message.

If you are unable to connect via connectivity services and none of them work for you (we’ve seen cases where ISPs block everything related to Windrose), you can try connecting via Direct IP as a workaround.

Advanced feature: May require manual router configuration (port forwarding / NAT setup). This option is intended for advanced users.

[dapper oasis]

My server is hosted by Gportal. I have the correct IP address and connection port, but it automatically redirects me to the game menu. Perhaps I've missed something? I have a lot of players on Windrose, to the point where I'll have to open several new servers with 10 additional slots each. Therefore, I'd like to have several working connection solutions in case of problems with players, although for a first launch, I think the game is doing well, much better than a AAA title.

Just so you know, no French internet service provider is blocking your main connection system ^^

[weary hazel]

I just finished converting my server to direct connections and managed to get it working. Was pretty standard if you've done it for other services.

Direct connect disables other methods of connecting (Code based).

I use a docker container: https://github.com/indifferentbroccoli/windrose-server-docker

but alternatively you can specify the options directly in the ServerDescription.json file to enable it.

Make sure your firewall allows tcp/udp connections for port 7777 (default) or the port you choose.

ie: sudo ufw allow 7777 comment "Windrose"

make sure your router has port 7777 tcp/udp open and routing to your server's internal IP address.

While not strictly neccessary I don't think, I added a port definition and the recommended network mode setting in the docker-compose.yml.

services:
  windrose:
    image: indifferentbroccoli/windrose-server-docker
    restart: unless-stopped
    container_name: windrose
    stop_grace_period: 30s
    env_file:
      - .env
    volumes:
      - ./server-files:/home/steam/server-files
    network_mode: host
    ports:
      - 7777:7777

I just tested having several people connect, as well as myself on lan and it seems to work.

One thing of note is that if I'm on LAN with the server (I am), I must connect using the 192.168.2.xxx internal network address. Connecting with the computers hostname will intiate the connection but fail.

My friends are able to connect using my dedicated hosted subdomain for game servers via:

games.{mydomainname}.com without a problem.

while this won't immediately help you, I can confirm that the tools they are providing (windrose) are capable of facilitating direct connections. I have about 15ms latency, friends in the same city ~30ms.

your issues may be specific to GPortal

And this isn't a steam relay network connection, as the nearest relay node to us is virginia, which is ~55-60ms away.. games that force relay network use (enshrouded) result in us have a minimum latency of ~110ms, which we aren't observing here.