Flash player 24.0.0.186 run in Google Chrome can not connect to socket server.

Hi Rohit,

I have updated to the beta version. The problem is fixed. I can connect to the socket server and login in to the game.

Thank you for your help.

And when will update automatically to users client?

Hello,

Can you tell me what ports your application is using for communication?  If you add the following to your mms.cfg, does it "fix" the problem?

EnableInsecureSocketPorts=1

mms.cfg file location

Assuming a default Windows installation, Flash Player looks for the mms.cfg file in the following system directories:

• 32-bit Windows - %WINDIR%\System32\Macromed\Flash

• 64-bit Windows - %WINDIR%\SysWow64\Macromed\Flash

Note: The %WINDIR% location represents the Windows system directory, such as C:\WINDOWS.

Macintosh /Library/Application Support/Macromedia

Linux /etc/adobe/

Note: Unlike Windows and Macintosh, the Linux player is in a directory named adobe, not in one named Macromed or

Macromedia.

Google Chrome

Google Chrome uses its own version of the mms.cfg file, saved at:

• Mac: /Users/<username>/Library/Application Support/Google/Chrome/Default/Pepper Data/Shockwave

Flash/System

• Win: %USERNAME%/AppData/Local/Google/Chrome/User Data/Default/Pepper Data/Shockwave Flash/System

The System directory may not exist. If not, create it manually.

Note: Directives such as those relating to updating Flash Player are not honored as Google embeds Flash Player in

Chrome and all updates are released by Google.

You might use third-party administration tools, such as Microsoft System Management Server, to replicate the

configuration file to the user's computer.

Use the standard techniques provided by your operating system to hide or otherwise prevent end users from seeing or

modifying the mms.cfg file on their systems.

Hi,

We were able to reproduce the issue. We are investigating it.

You may follow up on https://tracker.adobe.com/#/view/FP-4198184

Thanks!