Open n8twj opened 6 years ago
The IP address is my current public IP address that I am attempting to mine from
Hi, i have the same problem but with all miners ip address. Do you found a solution ? thx,
Possibly, it seems to be related to other protocols, like get work... Try adding: --no-gbt --no-getwork (at least on bfgminer)
On Fri, Jan 12, 2018 at 3:24 PM, Namba06 notifications@github.com wrote:
Hi, i have the same problem but with all miners ip address. Do you found a solution ? thx,
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/UNOMP/unified-node-open-mining-portal/issues/230#issuecomment-357340178, or mute the thread https://github.com/notifications/unsubscribe-auth/AEyM8eu1XuB7GG5AEKJMTMTVXOTlsZAqks5tJ7-agaJpZM4RJP0u .
Sorry but i have this error on my mining pool server not on the miner. Any idea ? thx.
2018-01-12 22:34:26 [pool] (Thread 4) New block to mine at height 109483 w/ difficulty of 15438926452
2018-01-12 22:34:26 [pool] (Thread 3) New block to mine at height 109483 w/ difficulty of 15438926452
2018-01-12 22:34:27 [pool] (Thread 3) Accepted trusted share at difficulty 17113/84120 from etnk6y4PDE6MZj5vtAj6SrE5nSosDuhVW4iUmJuzcfEGf64BQ62gEcNiZJXNvjdPkSFJnZK5o2DhbTc4EF6jzAP36whYPV2HbC@120.29.113.197
2018-01-12 22:34:28 [pool] (Thread 1) Retargetting difficulty 1533 to 1022 for etnkJtoFG1xjb9m6Bv6yWhCZJwJfn8H4CajYjX8UuEVJMF1fwh59hHME9V8kaYFNSjS48oPvpwvBsA2XhYSEKC9Z962tzbdj7q
2018-01-12 22:34:28 [pool] (Thread 1) Retargetting difficulty 13663 to 9109 for etnkMrseWiSUBvvidXmqxHPVFXZMY4ks8ULrfD6wg9VnUBeVoZqCWNnGdojDgHpFSmcQityCqHF9zKphC1fF8RNb87UFujMR3Y
2018-01-12 22:34:28 [pool] (Thread 3) Retargetting difficulty 49891 to 33261 for etnkHvLMqE3HEGKNvwHYpz6QVE5cBAX4uevvujJRx9Hh6mGN1LjTsK7aHT9JmGmZRR8PcXjDhkuqtLqCrJePRQPg4NAnWMMbum
2018-01-12 22:34:28 [pool] (Thread 4) Retargetting difficulty 100000 to 74074 for etnkHvLMqE3HEGKNvwHYpz6QVE5cBAX4uevvujJRx9Hh6mGN1LjTsK7aHT9JmGmZRR8PcXjDhkuqtLqCrJePRQPg4NAnWMMbum
2018-01-12 22:34:28 [pool] (Thread 2) Retargetting difficulty 1266 to 844 for etnkJtoFG1xjb9m6Bv6yWhCZJwJfn8H4CajYjX8UuEVJMF1fwh59hHME9V8kaYFNSjS48oPvpwvBsA2XhYSEKC9Z962tzbdj7q
2018-01-12 22:34:29 [pool] (Thread 2) Malformed message from 130.180.208.180: ��s��������Y�Є�̤��[�'��ћ��zz̨̩�+�/�,�0����/5 2018-01-12 22:34:31 [pool] (Thread 2) Malformed message from 182.30.12.115: ��ˇ�@uA g^��yI�J�\�Z�W��U@�I�-�+�/̨̩�,�0� 2018-01-12 22:34:32 [pool] (Thread 4) Accepted trusted share at difficulty 74074/114262 from etnkHvLMqE3HEGKNvwHYpz6QVE5cBAX4uevvujJRx9Hh6mGN1LjTsK7aHT9JmGmZRR8PcXjDhkuqtLqCrJePRQPg4NAnWMMbum@212.156.45.78 2018-01-12 22:34:34 [pool] (Thread 2) Malformed message from 162.211.155.146: ����ך�U �+T���e�˱t�\���+c˂l
�+�/̨̩�,�0�
2018-01-12 22:34:34 [pool] (Thread 3) Accepted trusted share at difficulty 33261/134419 from etnkHvLMqE3HEGKNvwHYpz6QVE5cBAX4uevvujJRx9Hh6mGN1LjTsK7aHT9JmGmZRR8PcXjDhkuqtLqCrJePRQPg4NAnWMMbum@212.156.45.78
2018-01-12 22:34:37 [pool] (Thread 1) Malformed message from 90.252.243.163: ����[�Vi1ue��Q��)�6�X�EѰ�7Zm$������+�/�,�0̨̩����/5
q�)�c���+�/�,�0̨̩����/5] (Thread 2) Malformed message from 115.72.165.30: ���/����0���ME�-�ӹ��� 2018-01-12 22:34:48 [pool] (Thread 2) Malformed message from 24.125.146.6: ��
=�:���o�6{p7���Fcc�I,ڃ��Icjj�+�/�,�0̨̩����/5
⠑,D�Y(�,�+�$�#�4:49 [pool] (Thread 2) Malformed message from 73.238.186.188: ���^��vM��-`�d�2�
2018-01-12 22:34:49 [pool] (Thread 2) Malformed message from 73.238.186.188: ��1��햙#�&tz� �N��v�MO���c-�u.�,�+�$�#�
2018-01-12 22:34:49 [pool] (Thread 2) Malformed message from 73.238.186.188: �����T;�a#�G�52���Q��<geIE�/359� �
2018-01-12 22:34:53 [pool] (Thread 2) Malformed message from 182.30.12.115: ���y��/PV���â���/��Ô�\�p������+�/̨̩�,�0�
2018-01-12 22:34:57 [pool] (Thread 2) Malformed message from 130.180.208.180: ���%��t�o���6���7�7I.B��]���
2018-01-12 22:34:58 [pool] (Thread 1) Retargetting difficulty 56640 to 38531 for etnkMrseWiSUBvvidXmqxHPVFXZMY4ks8ULrfD6wg9VnUBeVoZqCWNnGdojDgHpFSmcQityCqHF9zKphC1fF8RNb87UFujMR3Y
This happens a lot on our pool, and it seems to be coming from all over the world regularly. I blocked the ip's at the firewall and they go away. I believe they are trying to probe and send mischievous packets to your miner to see if there are any weaknesses.
Hi, thank you very munch for your help. We also have this "error" on the API screen:
2018-01-29 22:27:50 [api] Stat collection finished: 2 ms redis, 3 ms daemon 2018-01-29 22:27:50 [api] Broadcasting to 4007 visitors and 18 address lookups { protocol: null, slashes: null, auth: null, host: null, port: null, hostname: null, hash: null, search: '?address=etnk6sGLBHJevpVXL37oAfEuArCVy1Tpo2UecoDibbPV6NnkrenFF85dmVQqMQbVKXb5mP5iVkwxpW94B6WiBwuv1LnSedX7Ce&longpoll=true', query: { address: 'etnk6sGLBHJevpVXL37oAfEuArCVy1Tpo2UecoDibbPV6NnkrenFF85dmVQqMQbVKXb5mP5iVkwxpW94B6WiBwuv1LnSedX7Ce', longpoll: 'true' }, pathname: '/stats_address', path: '/stats_address?address=etnk6sGLBHJevpVXL37oAfEuArCVy1Tpo2UecoDibbPV6NnkrenFF85dmVQqMQbVKXb5mP5iVkwxpW94B6WiBwuv1LnSedX7Ce&longpoll=true', href: '/stats_address?address=etnk6sGLBHJevpVXL37oAfEuArCVy1Tpo2UecoDibbPV6NnkrenFF85dmVQqMQbVKXb5mP5iVkwxpW94B6WiBwuv1LnSedX7Ce&longpoll=true' } { protocol: null, slashes: null, auth: null, host: null, port: null, hostname: null, hash: null,
Is it normal ? Do you have an idea ? Thx,
[2017-12-21 01:41:39.010] [DEBUG] [default] - Pool belacoin Thread 4 Share processing setup with redis (127.0.0.1:6379) [2017-12-21 01:41:39.028] [DEBUG] [default] - Pool belacoin Thread 4 started for belacoin [BELA] {scrypt} [2017-12-21 01:41:39.028] [DEBUG] [default] - Switching Setup scrypt Setting proxy difficulties after pool start [2017-12-21 01:41:47.458] [DEBUG] [default] - Pool belacoin Thread 1 Malformed message from (unauthorized) [75.129.114.108]: !Z;[���"����fmM�"����;YX�B�8���0�,�(�$�� �2017-12-21 01:41:47.459] [DEBUG] [default] - Pool belacoin Thread 1 Malformed message from (unauthorized) [75.129.114.108]: ��kj98���2�.�*�&���=5��� [2017-12-21 01:41:47.459] [DEBUG] [default] - Pool belacoin Thread 1 Malformed message from (unauthorized) [75.129.114.108]: �/�+�'�#�� ��g@32��ED�1�-�)�%�ýý</ýAýýýý ý┐
[2017-12-21 01:41:47.499] [DEBUG] [␍␊°▒┤┌├] - M▒⎽├␊⎼ CLI CLI ┌␋⎽├␊┼␋┼± ⎺┼ ⎻⎺⎼├ 17117 [2017-12-21 01:41:47.647] [DEBUG] [␍␊°▒┤┌├] - P⎺⎺┌ ␉␊┌▒␌⎺␋┼ T⎼␊▒␍ 3 M▒┌°⎺⎼└␊␍ └␊⎽⎽▒±␊ °⎼⎺└ (┤┼▒┤├⎺⎼␋≥␊␍) [75.129.114.108]: !Z;[┴␌⎽ýý°6ý>,ý^ýýK┌⎻≠ýýýýýý0ý,ý(ý$ýý �2017-12-21 01:41:47.648] [DEBUG] [␍␊°▒┤┌├] - P⎺⎺┌ ␉␊┌▒␌⎺␋┼ T⎼␊▒␍ 3 M▒┌°⎺⎼└␊␍ └␊⎽⎽▒±␊ °⎼⎺└ (┤┼▒┤├⎺⎼␋≥␊␍) [75.129.114.108]: ýý┐┘98ýýý2ý.ý*ý&ý��=5��� [2017-12-21 01:41:47.648] [DEBUG] [default] - Pool belacoin Thread 3 Malformed message from (unauthorized) [75.129.114.108]: �/�+�'�#�� ��g@32��ED�1�-�)�%�ýý</ýAýýýý ý┐
Hi Did you ever get this fixed i am having this problem on our pool too..equihash algo
[2017-12-21 01:41:39.010] [DEBUG] [default] - Pool belacoin Thread 4 Share processing setup with redis (127.0.0.1:6379) [2017-12-21 01:41:39.028] [DEBUG] [default] - Pool belacoin Thread 4 started for belacoin [BELA] {scrypt} [2017-12-21 01:41:39.028] [DEBUG] [default] - Switching Setup scrypt Setting proxy difficulties after pool start
�2017-12-21 01:41:47.459] [DEBUG] [default] - Pool belacoin Thread 1 Malformed message from (unauthorized) [75.129.114.108]: ��kj98���2�.�*�&���=5��� [2017-12-21 01:41:47.459] [DEBUG] [default] - Pool belacoin Thread 1 Malformed message from (unauthorized) [75.129.114.108]: �/�+�'�#�� ��g@32��ED�1�-�)�%�ýý</ýAýýýý ý┐
[2017-12-21 01:41:47.499] [DEBUG] [␍␊°▒┤┌├] - M▒⎽├␊⎼ CLI CLI ┌␋⎽├␊┼␋┼± ⎺┼ ⎻⎺⎼├ 17117
�2017-12-21 01:41:47.648] [DEBUG] [␍␊°▒┤┌├] - P⎺⎺┌ ␉␊┌▒␌⎺␋┼ T⎼␊▒␍ 3 M▒┌°⎺⎼└␊␍ └␊⎽⎽▒±␊ °⎼⎺└ (┤┼▒┤├⎺⎼␋≥␊␍) [75.129.114.108]: ýý┐┘98ýýý2ý.ý*ý&ý��=5��� [2017-12-21 01:41:47.648] [DEBUG] [default] - Pool belacoin Thread 3 Malformed message from (unauthorized) [75.129.114.108]: �/�+�'�#�� ��g@32��ED�1�-�)�%�ýý</ýAýýýý ý┐