dedicated server module not working on windows

Bug #1090433 reported by Nasenbaer on 2012-12-14
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

After anouncing the shutdown of my dedicated server _aD told me, that he was unable to start a dedicated server on Windows. The problem seems to be, that Widelands (in dedicated mode) does not even try to connect to the metaserver. In normal (gui) mode connection to the metaserver works as it should.

I have not been able to take a closer look at this bug, as I have no Windows installation available at the moment.

Related branches

_aD (ad-simplypeachy) wrote :

Just to confirm that Wireshark shows no Internet activity from Widelands at all during attempts to start a dedicated server. The config the server uses works in the Widelands client - it has the user name and password for the metaserver saved and automatically logs in. The server does read the config file (confirmed by using Process Monitor to watch file I/O).

The error report is:
Caught exception (of type '7warning') in outermost handler!
The exception said: Widelands has not been able to connect to the metaserver.

This should not happen. Please file a bug report on version build-17(Release).
and remember to specify your operating system.

This was tried on Windows 7 x64 with build 6440 using --registered=false and without.

Tino (tino79) on 2012-12-30
Changed in widelands:
assignee: nobody → Tino (tino79)
status: Confirmed → Fix Committed
Changed in widelands:
milestone: none → build18-rc1
SirVer (sirver) wrote :

Released in build-18 rc1.

Changed in widelands:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers