[BUG] harvester doesn't connect with <ssl.SSLContext object at 0x000001742EB45748> from UAE only

Describe the bug I’m trying to run remote harvester in UAE with direct connection via public internet to main node and I get this:

2021-05-02T14:22:42.561 harvester harvester_server        : INFO     Cannot connect to host 212.220.xxx.xxx:8447 ssl:<ssl.SSLContext object at 0x000001742EB45748> [Connect call failed ('212.220.xxx.xxx', 8447)]
2021-05-02T14:22:45.577 harvester harvester               : INFO     Reconnecting to peer {'host': '212.220.xxx.xxx', 'port': 8447}

If trying the same through VPN via internal IP to internal IP of the main node everything works fine, but VPN is officially forbidden in UAE unless it’s government provided VPN…

2021-05-02T14:56:42.418 harvester chia.harvester.harvester: INFO     0 plots were eligible for farming d9b418ddac... Found 0 proofs. Time: 0.00000 s. Total 0 plots
2021-05-02T14:56:42.433 harvester harvester_server        : INFO     -> farming_info to peer 192.168.0.6 dfed90ff464b5129d7c74cexxxxx0a5893b3d9b504cc14d348fxxxx

Is there anything I can do about it other than changing country which is not a option as hardware is there? I haven’t experienced that issues in other countries… only UAE location is affected… No chances of changing ISP either as there is only one company - government related ISP. (well technically 2 ISP companies, but second one is just consumer trademark for the first)

Second question: impossible to install chia linux version in UAE location - install.sh scrip stalls on pip install commands saying network is not accessible, which probably means python repositories are blocked on ISP level… but is there any workarounds? as windows version works fine and syncs fine… but managing whole windows VM for chia only is a nightmare…

Expected behavior Chia harvester connects to main node via public internet and it’s possible to install linux version

• OS: Ubuntu 20.04 LTS, Windows 2016 server

[sheirys]

I’m also getting similar error when I’m trying to connect harvester and full node remotely, as you see in following:

2021-05-05T01:50:07.081 daemon chia.daemon.server         : INFO     Starting Daemon Server
2021-05-05T01:50:07.082 daemon chia.daemon.server         : INFO     Not implemented
2021-05-05T01:50:07.091 daemon chia.daemon.server         : INFO     Waiting Daemon WebSocketServer closure
2021-05-05T01:50:09.877 harvester harvester               : INFO     Started harvester service on network_id: mainnet
2021-05-05T01:50:09.878 harvester harvester               : INFO     Reconnecting to peer {'host': 'myip', 'port': 8447}
2021-05-05T01:50:09.895 daemon chia.daemon.server         : INFO     Register service {'service': 'chia_harvester'}
2021-05-05T01:50:09.896 daemon chia.daemon.server         : INFO     registered for service chia_harvester
2021-05-05T01:50:31.093 harvester harvester_server        : INFO     Cannot connect to host myip:8447 ssl:<ssl.SSLContext object at 0x00000201AF1F7978> [Connect call failed ('myip', 8447)]
2021-05-05T01:50:34.097 harvester harvester               : INFO     Reconnecting to peer {'host': 'myip', 'port': 8447}
2021-05-05T01:50:55.158 harvester harvester_server        : INFO     Cannot connect to host myip:8447 ssl:<ssl.SSLContext object at 0x00000201AF358438> [Connect call failed ('myip', 8447)]
2021-05-05T01:50:58.175 harvester harvester               : INFO     Reconnecting to peer {'host': 'myip', 'port': 8447}
2021-05-05T01:51:19.390 harvester harvester_server        : INFO     Cannot connect to host myip:8447 ssl:<ssl.SSLContext object at 0x00000201AF358668> [Connect call failed ('myip', 8447)]
2021-05-05T01:51:22.399 harvester harvester               : INFO     Reconnecting to peer {'host': 'myip', 'port': 8447}

Tried to restart harvester and full node, didn’t solved.

Make sure that you do chia start farmer. chia start node does not start farmer. I think command like chia status would be very helpful where information about running services would be displayed.

You can check if farmer is running with telnet.

[github-actions[bot]]

This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.