Players cannot log into my server

are the ports being forwarded tcp or udp? (flserver uses udp ports)

Just in case…
Go to www.whatismyip.com and make sure the IP it shows is the one you’re telling online players to log into.

Question, are you running it on W7 or, XP?

We have moved the UV several times over the years so I made a text file to help me not forget the smallest detail. These instructions are for a remote server. I have omitted the FLAC stuff since you are not using that. Adjust to your uses….

Installing the UnderVerse on a fresh dedicated server:

Install Remote admin or Team Viewer.
Set permissions.
Set reboot to ‘restart’, not ‘shutdown’.
Forward firewall ports UDP: 2300, 2301, 2302, 2303, 2304.
Set firewall exceptions for DirectPlay, Freelancer, FLServer, FLAC, Ioncross as they get installed.
Install WINRAR so you can extract files (rar and zip).

Make a directory C:\FreelancerUtilities.
Place the FLMM, FLAC and Ioncross install files into the above directory so they are easy to find.

Install FLMM version 1.3 to the C:\FreelancerUtilities folder. It will make a new folder and then open.
Open the Options tab and uncheck the box that says ‘Make modified files read-only when a mod is activated’.
Close the program without doing anything else.
Installing this now allows the .flmod extension to be associated with FLMM.
Go into that C:\FreelancerUtilities\Freelancer Mod Manager\mods folder and manually delete all the mods that come bundled with it.

Install Freelancer to C:\Freelancer.
Before it gets buggered up, make a C:\Freelancer10 directory and copy Freelancer to it for quick reloads of vanilla 1.0

Installing the mod, UnderVerseSERVER.zip…
First place the .zip in the FLMM\mods folder. Right click and ‘extract here’. This turns it into a .flmod extension.
Now double-click it and FLMM will automatically extract it into the \mod folder, then FLMM will open. Activate the mod, then close the program.
Note…NEVER use the FLMM File tab to launch Freelancer or FLServer. It is bugged and will lock up.

Run FLServer by itself so it generates the cfg file. To do this navigate to C:\Freelancer\EXE and double-click FLServer.exe
Name the server, check all 3 boxes and start the server. Let it run until it stops ‘loading’ and you can see the server name at the top. Close FLServer.
‘Send’ the directory C:\documents and settings\administrator\my documents\my games\freelancer\accts to the desktop for quick access (player file backups).

Install Ioncross to the C:\FreelancerUtilities folder. It will make a new folder.
Start Ioncross but say NO to allowing it to start the server. This takes you to the Configuration menu without loading a server.

Before Ioncross can control flserver properly you have to set two things.

1. proper mod version number as follows:
   In the typeable window lower left you see ‘FLServer - Version 1.0 Build 11 - FLServer’
   Simply overwrite the 1.0 with 2.29 so it reads ‘FLServer - Version 2.29 Build 11 - FLServer’

2. matching the dedi’s Date Format as follows:
   Ioncross can only use one of two settings for date: MM/DD/YYYY or DD/MM/YYYY. To assign one of these to your dedi, go to:
   START, Control Panel, Regional and Language Options, Regional Options, Customize, Date. Set the Short Date Format to one of the above (usually MM/dd/yyyy). Say ok.
   In the Ioncross Configuration, check the same box.

Very important after the two above changes…Now click the ‘Save Program Configuration’ button in the middle right.
Now you can close Ioncross.

Restarting Ioncross and allowing it to assume control will load a server.
You will know Ioncross is working by two ways, it will show ‘Good to go’ in the lower message window AND the error tab will not show a date format error.
Now press the ‘Stop Server’ button and close Ioncross.

Install the 32 weapons update for Ioncross to avoid warnings of players equipped with more than 24 weapons (simply copy and overwrite with the modified .exe)
Copy the custom data files for 2.29 to Ioncross, overwriting.

Something just occurred to me. Make sure each player who is trying to log into your server has IPv6 uninstalled or disabled for their local area connection.

That might be part of the problem.

robocop wrote:
Something just occurred to me. Make sure each player who is trying to log into your server has IPv6 uninstalled or disabled for their local area connection.

That might be part of the problem.

Doesn’t make a blind bit of difference from the clients point of view. That’s only important if you run a server on W7 or W8. I’ve joined servers with IPv6 enabled and had no issues.

Normally with issues like this it’s either the correct ports not being opened serverside in the router or something as simple as letting freelancer through windows firewall. Personally nver had issues setting up a server, but that’s just me

Dromedary wrote:

robocop wrote:
Something just occurred to me. Make sure each player who is trying to log into your server has IPv6 uninstalled or disabled for their local area connection.

That might be part of the problem.

Doesn’t make a blind bit of difference from the clients point of view. That’s only important if you run a server on W7 or W8. I’ve joined servers with IPv6 enabled and had no issues.

Normally with issues like this it’s either the correct ports not being opened serverside in the router or something as simple as letting freelancer through windows firewall. Personally nver had issues setting up a server, but that’s just me

Well, what I can say in response is only that in a few years of running our server I’ve had numerous complaints from players running Vista or 7 stating they can’t see the server in the list or that an odd string of numbers and letters shows in place of the IP addy in the GLS. After disabling and/or uninstalling IPv6 it worked fine for them. I’ve never experienced the problem myself but there you go…

You’re welcome. Glad to help.
Server name?

R