missing connection response

[chengen]

Hi, Teresa,
I am trying to set up the debug environment so I can try to get the information you need to help me. Even that appears challenging to me. I installed debug flash player (for firefox) and SOSMax.
Now whenever I try to access our site (or any flash page I guess) I get this popup asking me where the debugger or profiler is. If doesn't matter if I choose localhost or our web server address and click connect, it always come back with the same popup. If I choose do not connect it will give me another popup saying can not connect or something then move on. However, there is nothing logged in the SOSMax console.
If I launch the client from flashdevelop directly, then I see the logging messages as shown below in the SOSMax console. But that is the same as what I can see in the flashdevelop output window. Is that the correct log message I am looking for? If yes, do you know how I can get that to log when I access the client from within firefox?

[54.34:437] [Loading settings file from {}]
[54.38:926] [Settings file loaded]
[54.38:962] [Attempting BinaryTCP connection. Host: www.kingdomsunite.com, Port: 9899]
[54.39:945] [Connection established. Type: BinaryTCP]
[54.40:007] [Receiving (0 0) <-- ConnectionResponse]
[54.48:923] [Sending (0 0) --> LoginRequest]
[54.49:110] [Receiving (0 1) <-- LoginResponse]
            [Sending (0 0) --> CreateRoomRequest]
[54.49:293] [Receiving (0 2) <-- JoinZoneEvent]
[54.49:328] [Receiving (0 3) <-- JoinRoomEvent]
            [Sending (0 0) --> PluginRequest]
[54.49:907] [Receiving (0 4) <-- PluginMessageEvent]
[54.49:947] [Sending (0 0) --> CreateRoomRequest]
[54.50:977] [Queuing (0 6) --> JoinRoomEvent]
            [Receiving (0 5) <-- ZoneUpdateEvent]
[54.51:007] [Receiving (0 6) <-- JoinRoomEvent]

[tcarr]

I'm confused here because I don't recall needing to tell my browser anything after I installed the debug flash player for Firefox. Can you please give me the exact error message that you get? A screen shot if you can't copy the text.

In our internal docs on how to use SOSMax, it says:
It may complain about a missing file /some/path/to/mm.cfg on launch. If so, and it exists in the default location, make a dummy path and file in the directory SOS is launching from.

There's also another note that might be useful:
You may need to open TCP port 4444.

[chengen]

Teresa,
I attached a screenshot showing what I see when I visit our site using firefox after I installed debug flash player. I guess I lied about the popup after I choose "Don't Connect". When I choose "Connect" it will give me the same popup regardless of whether I choose localhost or other machine. But if I choose "Don't Connect" there will be no more popup and it proceed to the site.
es5_1.jpg

I don't get any log in SOSMax console if I access the site like this. I will get log if I test movie from flashdevelop.

[tcarr]

According to this website, you may have a bad install of your flash player.

Another website suggests trying these steps:
Select Other Machine
Write in 127.0.0.1
Check the box which says Don’t show this dialogue at launch
Click connect button

[chengen]

The suggestion to put in 127.0.0.1 didn't work. In the end, I selectd "Localhost" and "Don't show this dialog anymore" or something and clicked "Don't connect". Now the popup doesn't come up anymore but I still don't get any log in the SOSMax console.
Next I will download and install debug flash player again.

[chengen]

I reinstalled debug flash player and now everything seem to work. I got the following log. Still very limited information, but the timeout line is interesting. I don't see that in flashdevelop output.

[09.55:892] POWERFLASHER SOS max (Build 1004)
[09.55:960] [Loading settings file from {}]
            [Settings file loaded]
            [Attempting BinaryTCP connection. Host: 50.63.138.218, Port: 9899]
            Warning: Timeout on xmlsocket://50.63.138.218:843 (at 3 seconds) while waiting for socket policy file.  This should not cause any problems, but see http://www.adobe.com/go/strict_policy_files for an explanation.
            [Connection established. Type: BinaryTCP]
            [Receiving (0 0) <-- ConnectionResponse]
            [Sending (0 0) --> LoginRequest]
            [Receiving (0 1) <-- LoginResponse]
            [Sending (0 0) --> CreateRoomRequest]
            [Receiving (0 2) <-- JoinZoneEvent]
            [Receiving (0 3) <-- JoinRoomEvent]
            [Sending (0 0) --> PluginRequest]
            [Receiving (0 4) <-- PluginMessageEvent]
            [Sending (0 0) --> CreateRoomRequest]
            [Receiving (0 5) <-- ZoneUpdateEvent]
            [Receiving (0 6) <-- JoinRoomEvent]
            [Receiving (0 7) <-- PluginMessageEvent]
[10.39:254] [Receiving (0 8) <-- PluginMessageEvent]

The connection was successful, which means I did not reproduce the problem our user had.

[tcarr]

Another user suggested a while back opening port 843 to avoid that 3 second wait while Flash checks on the normal port. Another option is to use a custom policy file and add a TCP port to your ES5 on port 843 that tells clients that they can use port 9899 (and whatever other ports are allowed).

I'm very glad that you have SOSMax working for you now. Being unable to reproduce the bug is another headache of course.

[chengen]

Teresa,
Can you please elaborate on "opening port 843" or point me to the instruction? We did not knowing block any port on the server.

[tcarr]

I assumed that he meant opening it in the firewall, but if you already have that port open, then I guess if you care about that 3 seconds you add a TCP listener to your ES5 on port 843, and use a custom policy file.

[chengen]

Teresa,
Can you point me to the instruction on using a custom policy file? We don't have the need to use a custom policy file and I don't want to complicate things. But if there is no harm then getting rid of the 3 second wait will be good.