Connecting to MP server is timing out

[darryl]

Afternoon, since about Monday 29th January, I'm unable to access the MP server from within Wesnoth. I'm getting a timeout issue. Trying to join the official server, it says 'Connecting to server...' with the logo and the little white dot running left to right. But it's timing out after about 1 minute. Error dialog comes up with 'Connection failed: Connection timed out'. Before this, it was fairly instantaneous to get to the MP lobby.

I can log on to the forums with no issue (with my username 'darryl').
I'm running openSuSE 15.5.

Following is my Info section from within Wesnoth:

The Battle for Wesnoth version 1.16.11 x86_64
Running on Freedesktop SDK 23.08 (Flatpak runtime) x86_64
Distribution channel: Flatpak

Game paths
==========

Data dir: /app/share/wesnoth
User config dir: /home/USER/.var/app/org.wesnoth.Wesnoth/config/wesnoth
User data dir: /home/USER/.var/app/org.wesnoth.Wesnoth/data/wesnoth/1.16
Saves dir: /home/USER/.var/app/org.wesnoth.Wesnoth/data/wesnoth/1.16/saves
Add-ons dir: /home/USER/.var/app/org.wesnoth.Wesnoth/data/wesnoth/1.16/data/add-ons
Cache dir: /home/USER/.var/app/org.wesnoth.Wesnoth/cache/wesnoth

Libraries
=========

Boost: 1.80
Lua: 5.4.2
OpenSSL/libcrypto: 3.1.0d-dev (runtime 3.1.0d-dev)
Cairo: 1.18.0 (runtime 1.18.0)
Pango: 1.51.0 (runtime 1.51.0)
SDL: 2.28.5 (runtime 2.28.5)
SDL_image: 2.6.3 (runtime 2.6.3)
SDL_mixer: 2.6.3 (runtime 2.6.3)

Features
========

Lua console completion: yes
D-Bus notifications back end: yes

Current video settings
======================

SDL video drivers: [x11] wayland offscreen dummy evdev
Window size: 1920x1080
Screen refresh rate: 60
Screen dots per inch: 81.551842x81.642860
Screen dpi scale factor: 0.849498x0.850446

Current audio settings
======================

SDL audio drivers: [pulseaudio] jack pipewire disk dummy
Number of channels: 2
Output rate: 44100 Hz
Sample format: signed 16 bit little-endian
Sample size: 1024 bytes

Installed add-ons
=================

Afterlife_random: 1.1.2b
Ageless_Era: 4.31.0
Ageless_Resources: 4.28.0
Era_of_Magic_Resources: 2.2.0
Extra_Advancements_for_Default: 0.1.0
Shards_Era: 0.2.8
Shards_Era_Resources: 0.0.8
Valley_of_the_Ancients: 2.10.0


Thank you,
Darryl.

[Pentarctagon]

Nothing went on with the server on the 29th and it is definitely still up and running, so most likely something changed on your end. You could try enabling debug network logging (in the advanced preferences) and then posting the log file after it fails to see if it has any useful information.

[darryl]

Battle for Wesnoth v1.17.16 x86_64
Started on Thu Feb 1 05:10:00 2024

Data directory: /usr/share/wesnoth
User configuration directory: /home/USER/.config/wesnoth
User data directory: /home/USER/.local/share/wesnoth/1.17
Cache directory: /home/USER/.cache/wesnoth

Setting mode to 1920x1080
Checking lua scripts... ok
20240201 05:10:15 info network: Resolving hostname: server.wesnoth.org
20240201 05:10:15 info network: Waiting for handshake
20240201 05:11:20 info network: wesnothd_connection::io_service::run() returned
20240201 05:11:20 error network: caught network error: Connection timed out
20240201 05:11:20 error general: Connection failed: Connection timed out

The above is what I received in the log for 1.17 after setting debug option for Network in Advanced Logging. I don't seem to have logs for version 1.16.

I do have Server disconnect timeout set to 60 - which is how long it seems to take for the timeout as shown above.

[Pentarctagon]

Are you able to connect to the add-ons server?

[darryl]

(Sorry, thought I replied to this about 8 hours ago). Yes, I can get to the add-ons from within the game, but it's taking a lot longer than it used to (over a minute), used to be seconds.

And I can 'dig' (unix command) both the add-ons and the MP server (server.wesnoth.org).

I set the Server Disconnect Timeout to 120 (in Advanced preferences), but it still timed out around 60 seconds (for MP server).

So I just don't know what happened - I changed nothing at my end (that I'm aware of). It's not asking for a password when I try to connect (should it?)

[Pentarctagon]

You could try directly connecting to port 14996 - by default it uses port 15000 and then redirects based on your client version. Otherwise, it does appear that something happened either on your end or somewhere between you and the Wesnoth servers since http://wesnothd.wesnoth.org/ shows that players generally are able to still connect and I'm also able to connect just fine using Mint.

[darryl]

That didn't work, and I've also tried to connect on a different computer (at home) on the same network - no good. So, it looks like something with our internet. We did upgrade from FTTN to FTTP about three weeks ago, but everything was working fine then, and up to end of January.

Any other ideas? (And thanks for your help).

[Pentarctagon]

You could try downloading Wesnoth either from Steam or from your system package manager, in case it's somehow a Flatpak issue.

[darryl]

Well, as you have it - I installed via Steam, and all's good! Add-ons load within seconds, and so also MP.

Again, I have no idea why it stopped working with native install.

Anyway, I use Steam for other games, so as it's the latest production build, I'll keep using it (and probably delete the flatpak build).

Thanks for your help!