Signal problem?

To add comments, please log in or register
Erdenebayar Lamjav
1358
Erdenebayar Lamjav  

Dear traders, I rent server "Payment for virtual hosting on 'MQL5 New York 6', tariff #4" on 2018.02.05. And I subscribe Subscription to signal '****' (author: '*****') for a month (02.05–03.05).

Yesterday that trader open 30 orders, but mine is not any position opened. But why?

Erdenebayar Lamjav
1358
Erdenebayar Lamjav  

That error on Virtual server terminal side.

2018.03.01 00:01:20.389    MQL5.community: authorization failed

2018.03.01 00:01:30.296    Signal: '92****': failed get list of signals, connection error <--Too many error occurred

2018.03.01 00:41:33.537    '92****': 0 charts, 0 EAs, 0 custom indicators, signal enabled, no subscription found, last known ping to Broker09 is 1.87 ms

2018.03.01 00:41:33.537    RAM: 72 Mb reserved, 110 Mb committed

Erdenebayar Lamjav
1358
Erdenebayar Lamjav  
2018.03.02 00:01:23.294    MQL5.community: authorization failed
2018.03.02 00:01:32.232    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:06:23.657    MQL5.community: authorization failed
2018.03.02 00:06:33.392    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:11:23.908    MQL5.community: authorization failed
2018.03.02 00:11:33.003    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:16:23.396    MQL5.community: authorization failed
2018.03.02 00:16:32.802    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:21:23.852    MQL5.community: authorization failed
2018.03.02 00:21:35.165    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:26:23.292    MQL5.community: authorization failed
2018.03.02 00:26:32.292    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:31:23.623    MQL5.community: authorization failed
2018.03.02 00:31:33.248    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:36:23.125    MQL5.community: authorization failed
2018.03.02 00:36:35.486    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:41:23.488    MQL5.community: authorization failed
2018.03.02 00:41:25.519    '92****': ping to current access point DC 2  is 1.97 ms
2018.03.02 00:41:34.191    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:41:48.458    '92****': 0 charts, 0 EAs, 0 custom indicators, signal enabled, no subscription found, last known ping to Broker09 is 1.97 ms
2018.03.02 00:41:48.458    RAM: 70 Mb reserved, 111 Mb committed
2018.03.02 00:46:23.865    MQL5.community: authorization failed
2018.03.02 00:46:32.866    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:51:23.978    MQL5.community: authorization failed
2018.03.02 00:51:34.431    Signal: '92****': failed get list of signals, connection error
2018.03.02 00:56:23.637    MQL5.community: authorization failed
2018.03.02 00:56:32.653    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:01:23.967    MQL5.community: authorization failed
2018.03.02 01:01:37.015    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:06:23.345    MQL5.community: authorization failed
2018.03.02 01:06:32.408    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:11:23.394    MQL5.community: authorization failed
2018.03.02 01:11:32.504    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:16:23.116    MQL5.community: authorization failed
2018.03.02 01:16:32.382    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:21:23.806    MQL5.community: authorization failed
2018.03.02 01:21:32.995    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:26:23.309    MQL5.community: authorization failed
2018.03.02 01:26:32.310    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:31:23.687    MQL5.community: authorization failed
2018.03.02 01:31:38.875    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:36:23.049    MQL5.community: authorization failed
2018.03.02 01:36:32.143    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:41:23.552    MQL5.community: authorization failed
2018.03.02 01:41:32.881    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:41:48.538    '92****': 0 charts, 0 EAs, 0 custom indicators, signal enabled, no subscription found, last known ping to Broker09 is 2.24 ms
2018.03.02 01:41:48.538    RAM: 70 Mb reserved, 111 Mb committed
2018.03.02 01:46:23.586    MQL5.community: authorization failed
2018.03.02 01:46:33.196    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:51:23.292    MQL5.community: authorization failed
2018.03.02 01:51:32.746    Signal: '92****': failed get list of signals, connection error
2018.03.02 01:56:23.779    MQL5.community: authorization failed
2018.03.02 01:56:32.702    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:01:23.954    MQL5.community: authorization failed
2018.03.02 02:01:36.673    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:06:23.394    MQL5.community: authorization failed
2018.03.02 02:06:33.457    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:11:24.506    MQL5.community: authorization failed
2018.03.02 02:11:36.304    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:16:23.900    MQL5.community: authorization failed
2018.03.02 02:16:34.150    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:21:24.074    MQL5.community: authorization failed
2018.03.02 02:21:33.731    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:26:24.249    MQL5.community: authorization failed
2018.03.02 02:26:33.312    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:31:24.361    MQL5.community: authorization failed
2018.03.02 02:31:35.987    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:36:24.614    MQL5.community: authorization failed
2018.03.02 02:36:36.708    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:41:24.226    MQL5.community: authorization failed
2018.03.02 02:41:33.664    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:41:49.196    '92****': 0 charts, 0 EAs, 0 custom indicators, signal enabled, no subscription found, last known ping to Broker09 is 1.97 ms
2018.03.02 02:41:49.196    RAM: 72 Mb reserved, 110 Mb committed
2018.03.02 02:46:24.166    MQL5.community: authorization failed
2018.03.02 02:46:33.370    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:51:24.997    MQL5.community: authorization failed
2018.03.02 02:51:33.841    Signal: '92****': failed get list of signals, connection error
2018.03.02 02:56:24.781    MQL5.community: authorization failed
2018.03.02 02:56:35.000    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:01:24.081    MQL5.community: authorization failed
2018.03.02 03:01:34.613    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:06:24.318    MQL5.community: authorization failed
2018.03.02 03:06:36.772    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:11:24.696    MQL5.community: authorization failed
2018.03.02 03:11:34.415    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:16:24.183    MQL5.community: authorization failed
2018.03.02 03:16:33.605    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:21:24.436    MQL5.community: authorization failed
2018.03.02 03:21:33.389    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:26:24.798    MQL5.community: authorization failed
2018.03.02 03:26:36.142    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:31:24.910    MQL5.community: authorization failed
2018.03.02 03:31:36.036    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:36:24.163    MQL5.community: authorization failed
2018.03.02 03:36:35.117    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:41:24.775    MQL5.community: authorization failed
2018.03.02 03:41:25.822    '92****': ping to current access point DC 2  is 1.88 ms
2018.03.02 03:41:34.541    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:41:49.745    '92****': 0 charts, 0 EAs, 0 custom indicators, signal enabled, no subscription found, last known ping to Broker09 is 1.88 ms
2018.03.02 03:41:49.745    RAM: 70 Mb reserved, 111 Mb committed
2018.03.02 03:46:24.903    MQL5.community: authorization failed
2018.03.02 03:46:34.669    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:51:24.390    MQL5.community: authorization failed
2018.03.02 03:51:35.953    Signal: '92****': failed get list of signals, connection error
2018.03.02 03:56:24.518    MQL5.community: authorization failed
2018.03.02 03:56:33.378    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:01:24.130    MQL5.community: authorization failed
2018.03.02 04:01:35.178    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:06:24.523    MQL5.community: authorization failed
2018.03.02 04:06:33.540    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:11:27.870    MQL5.community: authorization failed
2018.03.02 04:11:38.027    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:16:24.310    MQL5.community: authorization failed
2018.03.02 04:16:35.733    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:19:44.994    Connect: 170.75.197.157:443
2018.03.02 04:19:44.994    '92****': connect failed [No connection]
2018.03.02 04:19:50.151    Connect: 38.76.16.223:443
2018.03.02 04:19:55.308    'Broker09': connect failed
2018.03.02 04:20:00.464    Connect: 170.75.197.157:443
2018.03.02 04:20:05.621    Connect: 38.76.16.223:443
2018.03.02 04:20:10.777    'Broker09': connect failed
2018.03.02 04:20:15.934    Connect: 170.75.197.157:443
2018.03.02 04:20:15.965    '92****': login on Broker09 through DC 2  (ping: n/a)
2018.03.02 04:20:16.512    Connect: 170.75.197.157:443
2018.03.02 04:20:16.543    '92****': login datacenter on Broker09 through DC 2  (ping: n/a)
2018.03.02 04:20:16.621    '92****': previous successful authorization performed from 18.218.119.24
2018.03.02 04:20:16.621    '92****': 0 charts, 0 EAs, 0 custom indicators, signal enabled, no subscription found
2018.03.02 04:20:16.668    MQL5.community: authorization failed
2018.03.02 04:20:27.325    '92****': ping to current access point DC 2  is 14.61 ms
2018.03.02 04:21:24.501    MQL5.community: authorization failed
2018.03.02 04:21:35.095    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:26:24.097    MQL5.community: authorization failed
2018.03.02 04:26:34.676    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:31:24.474    MQL5.community: authorization failed
2018.03.02 04:31:35.116    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:36:24.837    MQL5.community: authorization failed
2018.03.02 04:36:34.150    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:41:24.339    MQL5.community: authorization failed
2018.03.02 04:41:34.481    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:41:50.310    '92****': 0 charts, 0 EAs, 0 custom indicators, signal enabled, no subscription found, last known ping to Broker09 is 2.07 ms
2018.03.02 04:41:50.310    RAM: 70 Mb reserved, 111 Mb committed
2018.03.02 04:46:24.577    MQL5.community: authorization failed
2018.03.02 04:46:33.561    Signal: '92****': failed get list of signals, connection error
2018.03.02 04:49:52.605    Virtual Hosting: close command received
2018.03.02 04:49:52.605    main window close command received
2018.03.02 04:49:52.730    stop experts command
2018.03.02 04:49:52.730    main process shutdown
2018.03.02 04:49:52.745    main window destroy
2018.03.02 04:49:52.761    main window destroyed [1]
2018.03.02 04:49:52.761    main window close command processed
2018.03.02 04:49:52.761    MetaTrader 4 exit
2018.03.02 04:49:52.761    pumping stopped
2018.03.02 04:49:52.792    base dispatchers stopped
2018.03.02 04:49:52.808    base dispatchers deleted
2018.03.02 04:49:52.808    MetaTrader 4 build 1108 stopped
2018.03.02 04:50:00.887    terminal data initialized
2018.03.02 04:50:00.902    MetaTrader 4 build 1108 started (MetaQuotes Software Corp.)
2018.03.02 04:50:00.902    Windows Server 2016 Standard (x64 based PC), IE 11.00, RDP, 8 x Intel Xeon  E5-1620 v3 @ 3.50GHz, RAM: 50193 / 65428 Mb, HDD: 437057 / 457278 Mb, GMT+01:00
2018.03.02 04:50:00.902    Data Folder: C:\Hosting\instances\E55DA38CF3FB0173EAAD198FF03BED26
2018.03.02 04:50:00.902    Started with configuration file 'C:\Hosting\instances\E55DA38CF3FB0173EAAD198FF03BED26\start.ini'
2018.03.02 04:50:00.918    main frame created
2018.03.02 04:50:01.168    load frame OK
2018.03.02 04:50:01.183    hosting socket initialized
2018.03.02 04:50:01.183    MetaTrader 4 init OK
2018.03.02 04:50:01.324    Connect: 38.76.16.223:443
2018.03.02 04:50:01.512    '92****': login on Broker09
2018.03.02 04:50:01.918    '92****': previous successful authorization performed from 202.70.34.30
2018.03.02 04:50:01.918    '92****': 0 charts, 0 EAs, 0 custom indicators, signal disabled
2018.03.02 04:50:01.933    '92****': ping to current access point DC 1 is 1.56 ms
2018.03.02 04:50:02.230    '92****': ping to current access point DC 1 is 1.56 ms
2018.03.02 04:55:02.030    Virtual Hosting: flush logs command received
2018.03.02 04:55:08.046    Virtual Hosting: flush logs command received
2018.03.02 04:58:13.604    Virtual Hosting: flush logs command received
2018.03.02 04:58:21.089    Virtual Hosting: close command received
2018.03.02 04:58:21.089    main window close command received
2018.03.02 04:58:21.198    stop experts command
2018.03.02 04:58:21.198    main process shutdown
2018.03.02 04:58:21.214    main window destroy
2018.03.02 04:58:21.230    main window destroyed [1]
2018.03.02 04:58:21.230    main window close command processed
2018.03.02 04:58:21.230    MetaTrader 4 exit
2018.03.02 04:58:21.230    pumping stopped
2018.03.02 04:58:21.261    base dispatchers stopped
2018.03.02 04:58:21.277    base dispatchers deleted
2018.03.02 04:58:21.277    MetaTrader 4 build 1108 stopped
2018.03.02 04:58:29.246    terminal data initialized
2018.03.02 04:58:29.261    MetaTrader 4 build 1108 started (MetaQuotes Software Corp.)
2018.03.02 04:58:29.261    Windows Server 2016 Standard (x64 based PC), IE 11.00, RDP, 8 x Intel Xeon  E5-1620 v3 @ 3.50GHz, RAM: 50186 / 65428 Mb, HDD: 437054 / 457278 Mb, GMT+01:00
2018.03.02 04:58:29.261    Data Folder: C:\Hosting\instances\E55DA38CF3FB0173EAAD198FF03BED26
2018.03.02 04:58:29.261    Started with configuration file 'C:\Hosting\instances\E55DA38CF3FB0173EAAD198FF03BED26\start.ini'
2018.03.02 04:58:29.277    main frame created
2018.03.02 04:58:29.590    load frame OK
2018.03.02 04:58:29.605    hosting socket initialized
2018.03.02 04:58:29.605    MetaTrader 4 init OK
2018.03.02 04:58:30.761    Connect: 38.76.16.223:443
2018.03.02 04:58:30.918    '92****': login on Broker09
2018.03.02 04:58:31.293    '92****': previous successful authorization performed from 173.231.184.87
2018.03.02 04:58:31.293    '92****': 0 charts, 0 EAs, 0 custom indicators, signal disabled
2018.03.02 04:58:31.340    '92****': ping to current access point DC 1 is 1.65 ms
2018.03.02 05:10:31.728    Virtual Hosting: flush logs command received
Sergey Golubev
Moderator
106091
Sergey Golubev  

You can check once again this instruction about 'How to Subscribe to a MT4 Signal

If you checked everything according to the link/thread above and it still does not work - write to the service desk (the link is on your profile) - 

Forum on trading, automated trading systems and testing trading strategies

VPS Cancelled Early Without Warning?

MQL5.Support, 2018.02.28 06:37

The work of virtual hosting was restored. Please check your rented servers.

If you have any problems, please create new request at Service Desk.

To add comments, please log in or register