Forum ‹ General ‹ Error Joining Room:

[tomoprime]

Hi I updated my Client code and Server code to the new player.io v2.3 release but what used work is now giving me some issues connecting to my local development server. You may want to note in the update notes to add a parterid of null in the connect string for Unity users.

[client side error]
Error Joining Room: PlayerIOClient.PlayerIOError: GeneralError; Unable to connect, errorcode=AccessDenied...

[server side error]
[16:23:15] Starting Development Server (v2.3.0.0)
[16:23:15] PolicyServer Error: Unable to start Flash policy server on port 843. Details: Access denied (Local Endpoint: 0.0.0.0:843)
[16:23:15] PolicyServer Error: Unable to start Silverlight policy server on port 943. Details: Access denied (Local Endpoint: 0.0.0.0:943)
[16:23:16] Server started. Logged in with account: tomoprime
[16:23:16]
[16:23:16] Trying last loaded dll
[16:23:16]
[16:23:16] Using Game Dll: newGame.dll
[16:23:16] ========================
[16:23:16] (dll: /Users/Tomo/Downloads/Player-2.3/Flash/NewGame/Serverside Code/Player.IO Test Server Project/bin/Debug/newGame.dll)

The odd thing about this error is that I don't recall getting a pop up window. I may have logged in once before though. I'm using MonoDevelop running the executable as Mono 2.10.6 on Mac (which used to connect ok). The Admin panel of GameServers shows my tomoprime: Development Cluster (1 server) as up but I am unable to connect to it. Does my dev cluster need to be Live just to interact with it locally? I wish the Unity Client gave more detail in the error message...

[Benjaminsen]

There is quite a few things that can result in this error. Thus can I get you to try the following things?

0: restart... yea it sounds cliche, but it sometimes work.

1: Verify that nothing is using that port already. Quickest way to do this is by running netstat -a -o -n in a console. If there is something listening to the port, compare the PID with the ones from your task manager to see what is blocking the application. (Skype has a tendency to listen to both ports for instance)

2: Verify that the application is allowed to listen to the ports in your firewall software. With windows firewall you can add the application to the allowed list or simply whitelist the two ports.

3: Try disabling IPv6 on your computer. We have seen some cases where IPv6 conflicted with the IPv4 instance

4: Got several network cards / connections? Try disabling one of them

5: If all of the above fails, post here so we can continue the debugging

[tomoprime]

Hi Ben
It's been a while since I've seen you on chat

0 - check

1- I had used lsof to see if something was using the ports...

I looked up ports 8184, 843, and 943...

The only thing I noticed was an occasional packet sent out from Unity on port 843.
Tomo$ lsof -i|grep :843
Unity 811 Tomo 29u IPv4 0xffffff8019449880 0t0 TCP localhost:50668->localhost:843 (SYN_SENT)

2- Firewall software is disabled - check. I use Skype but it was turned off in this case. I'm based in NY.

3-Disable IPv6. That's a bit extreme. Was this an intermittent problem for past users ? Playerio was working and just stopped for me in the middle of development. Nothing changed on my system as far as I could tell.

4- I'm working on a Mac Air. So no extra cards. I did have VirtualBox running Windows XP though which used to run playerio 2.2.8. I had shut this down to run playerio 2.3 on Monodevlop to spare me the extra ram and further simplify my dev server connection as "localhost".

UPDATE: I just fired up VirtualBox on my Mac Air to run the older 2.2.8.0 Dev Server in MS Visual Studio and my Unity Client which has the newer 2.3 DLL is able to connect to it... It seems the Dev Server connect issue is exclusive to MonoDevelop running PlayerIO v2.3 on Mac. I should also note that I only run Unity 3.4.2f2 Pro/Android/iOS on Mac OS Lion.

[Benjaminsen]

Oh! You are in monodevelop!

I actually had the same issue as you are describing in mono develop myself, updating to the newest stable version of mono & monodevelop and rebooting the machine worked for me.

/Chris

[tomoprime]

Didn't I mentioned that in my 1st post?
I'm using MonoDevelop running the executable as Mono 2.10.6 on Mac

I updated Mono to 2.10.8 and still no change. I didn't update MonoDevelop as it breaks the Unity install.

[Benjaminsen]

Didn't I mentioned that in my 1st post?
I'm using MonoDevelop running the executable as Mono 2.10.6 on Mac

I updated Mono to 2.10.8 and still no change. I didn't update MonoDevelop as it breaks the Unity install.

Mmm that's bad. Can you add me to Skype? my handle is "q-rious" then we can do a bit of live debugging.

[Benjaminsen]

Just a quick update, we can now replicate the error reliable allowing us to debug and fix it shortly. Stay tuned!

[capitaljmedia]

Hey guys, any update on this error?

I am also trying to use Monodevelop on OS X, but getting the error that Mono / .NET 4.0 is not installed, but I just installed the latest version of Mono, do I still have to get .Net separately?

-JJ