I Got problems MUDEC_00044: I use some solution but can’t fix it.
Thank you for sending this problem report. 
However is there any problem to use Mudfish? If then please elaborate little bit more for me.
Actually this was for the issue about Amazon EC2, i had this issue around one month ago but i didnt have time to do a the report.
Below is the issue i had 1 month ago and still have it.
To be noted, I dont have the issue when Full connect is activated using EC2 node. But when i connect blade and soul to EC2 i cant even ping the node. Tell me is the report is okay or if i should do another one. I’m really sorry for the delay but EC2 is really a good server for me.
I really like the mudfish services and I really hope i can use the EC2 node again.
If I remember correctly, from your desktop you can’t even send a ping to 52.28.104.3 (DE Europe (Germany - Amazon EC2)), right? However is it pingable to 52.28.104.226 IP?
Yes this is correct, i can’t even ping 52.28.104.3 but ONLY when mudfish is open. If i close mudfish i can ping EC2.
I can’t even ping 52.28.104.226 also.
I don’t understand what’s the issue.
Okay i tried it, i can now connect to EC2 and ping it.Now the issue that arises is Fastconnect gives me very stable and low ping in game without fastconnect I’m getting 350ms.
Before with EC2 + fastconnect i was getting 230ms so it’s not worth using EC2 without fastconnect.
Okay. It seems the culprit is FastConnect mode. Let me test it again.
Yes it seems like it’s fast connect. Me and my girlfriend, we both used fast connect mode with EC2 before, but it’s been more than 2 months since we haven’t been able to use it. If EC2 wasn’t our best node I wouldn’t have mind but this is the node that gives us best ping in Blade and Soul. We are currently using IdealHosting 2, but in game we get 280+ ms which is kinda bad.