'Could not connect to Matchmaker' Dedi Error Now that I have your attention It's not a fix as such, it's a work around that I have found.. Ever since rF2 was released many users including myself have experienced the 'could not connect to matchmaker' on their dedicated server.. 1. The problem only exists if you are running more than one dedicated rF2 server. I have tried everything from ports, different ranges of ports (ie having one server on port 32000 and the other on 54000). I have tried the one install, copy and pasted, renaming the folder to ie rFactor2_2, changing the profile name and port numbers. I have tried two installs, installing the mods and tracks in each install, changing profile names and ports. I have changed the properties in the links for IP addresses and ports. I have tried one install and creating different profiles with the different ports (and tried different port ranges ie 32000 for one, 54297 for the other). What happens in all instances, is either what ever server runs first you can't connect to the other OR if you can connect to both servers (99% of the time in my testing) either one, the other, or both will display the message 'could not connect to matchmaker'. This happens at random times, could run for days, could run for hours.. Very Frustrating.. When this happens, as many may know by now, is that no one can join your server. You need to restart it before it becomes visable again in the list and for your fellow drivers to join.. What I've noticed in this build (134) is that it's much worse than previous builds, in that I get more of the messages 'could not connect to matchmaker' when trying to run more than one dedicated server on the one server.. Enough ramblings.. The fix.. The fix is only for those who have access to their physical server in full (administration access). As long as you have administrative access to your server (in a datacentre, remote location or in your home/work) you can create another user profile.. I've found that the only way to run multiple servers from the one physical machine (for those trying to run more than one at present) is to either create a VM (virtual machine) for each user / install, or create another user profile.. From here, the rest is straight forward. You now have two alternate logins, two 'seperate' installs, two registry etc etc.. I've run now 2 x rFactor2 servers (with different ports of course) on the 2 x user profiles for a few days now with no dramas what so ever. In my instance I have 2 x communities who use the server, each running rFactor 2. Yes it can be a pain in the backside if you are one community wishing to run more than 1 x rFactor 2 servers, and yes this never happened for rFactor 1 (and still doesn't). In the past I've had 5 x rFactor1 servers running on the one user profile.. My find is simply to advise ISI (and others) of the temp fix until rF2 goes gold (or soon after gold), where in the instance of more than 1 x dedi server is required to be run, it can only be done via seperate VM's or seperate user profiles, this is the only way it can be done to avoid the dreaded 'could not connect to matchmaker'. Hope this helps ISI (in a fix) and others in running (where they can) more than one server.