#FlexibleLeverage updated
- all string fields now have limit 1024 letters (was 128).
https://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.50.0
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.32.0
- all string fields now have limit 1024 letters (was 128).
https://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.50.0
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.32.0
#FlexibleLeverage v1.34 updated
- [fix] logins exclusion list (policy settings) fixed.
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.34.0
- [fix] logins exclusion list (policy settings) fixed.
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.34.0
#FlexibleLeverage for #MT4 updated
- added support infinite length of strings for
- added support infinite length of strings for
http://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.53.0
- added support infinite length of strings for
logins and groups parameters in NOP settings;- added support infinite length of strings for
logins, groups and symbols parameters in policy settings;http://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.53.0
#FlexibleLeverage for #MT4 updated
minor update
http://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.54.0
minor update
http://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.54.0
#FlexibleLeverage for #MT5 v1.35 updated
- added support infinite length of strings for
- added support infinite length of strings for
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.35.0
- added support infinite length of strings for
logins and groups parameters in NOP settings;- added support infinite length of strings for
logins, groups and symbols parameters in policy settings;https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.35.0
#FlexibleLeverage for #MT4 updated to v1.55
possible fix against "out trade" problem on some LPs.
http://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.55.0
possible fix against "out trade" problem on some LPs.
http://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.55.0
#FlexibleLeverage for #MT4 updated to v1.56
- fixed mistake with NOP Groups and Logins field;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.56.0
- fixed mistake with NOP Groups and Logins field;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.FlexibleLeverage/1.56.0
#FlexibleLeverage for #MT5 updated to v1.36
- fixed mistake with NOP Groups and Logins field;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.36.0
- fixed mistake with NOP Groups and Logins field;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.36.0
#AMF plugin for #MT4 updated
- bugfix related to TP restrictions;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.AMF/1.22.0
- bugfix related to TP restrictions;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.AMF/1.22.0
#WebAPI updated to most recent version
MT4ManAPI.dll updated to v1415
https://cloud.mywebapi.com/History
Our downtime was : 30 seconds, equals to 99.9988799% SLA
99.9% SLA (Microsoft Azure conditions) = 44 minutes per month of downtime allowed.
MT4ManAPI.dll updated to v1415
https://cloud.mywebapi.com/History
Our downtime was : 30 seconds, equals to 99.9988799% SLA
99.9% SLA (Microsoft Azure conditions) = 44 minutes per month of downtime allowed.
CPlugin news
#WebAPI updated to most recent version MT4ManAPI.dll updated to v1415 https://cloud.mywebapi.com/History Our downtime was : 30 seconds, equals to 99.9988799% SLA 99.9% SLA (Microsoft Azure conditions) = 44 minutes per month of downtime allowed.
#AMF plugin for #MT5 updated
- bugfix related to TP restrictions;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.AMF/1.22.0
- bugfix related to TP restrictions;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.AMF/1.22.0
#WebAPI IMPORTANT
tonight we run two more additional mirrors of WebAPI:
Hong-Kong
IP
London
IP
Your systems from regions above will get single digit latency value (in milliseconds).
make sure you allow these IPs to connect to your MT4/MT5
No need to change anything else on your side, traffic will be routed to closest to your origin mirror. To make it happen, always use address
tonight we run two more additional mirrors of WebAPI:
Hong-Kong
IP
103.252.117.172London
IP
83.229.68.30Your systems from regions above will get single digit latency value (in milliseconds).
make sure you allow these IPs to connect to your MT4/MT5
No need to change anything else on your side, traffic will be routed to closest to your origin mirror. To make it happen, always use address
cloud.mywebapi.com👍1
#Toolbox on staging got update.
Some of your assigned application forgot their settings.
https://pre.toolbox.cplugin.net
Some of your assigned application forgot their settings.
https://pre.toolbox.cplugin.net
#WebAPI IMPORTANT
new mirror run in Singapore
IP:
make sure you allow these IPs to connect to your MT4/MT5
No need to change anything on your side, traffic will be routed to closest to your origin mirror. To make it happen, always use address
new mirror run in Singapore
IP:
5.223.43.1make sure you allow these IPs to connect to your MT4/MT5
103.252.117.17283.229.68.30194.233.70.35 - is out of service, forever. you can remove it from whitelists.No need to change anything on your side, traffic will be routed to closest to your origin mirror. To make it happen, always use address
cloud.mywebapi.com#WebAPI
today we are updating
Minimal interruptions should be during maintenance.
No actions required from your side. As we have bunch of mirrors, we update one after another without downtime.
today we are updating
auth.cplugin.net to serve requests faster using updated code and hardware.Minimal interruptions should be during maintenance.
No actions required from your side. As we have bunch of mirrors, we update one after another without downtime.
#WebAPI got major performance gain, in addition to Identity server.
Requests, addressed to pumping connection will be executed during 5ms.
Before, it was ~300ms.
Enjoy!
Requests, addressed to pumping connection will be executed during 5ms.
Before, it was ~300ms.
Enjoy!