Quote from: dstm on October 30, 2017, 01:09:12 PM

Quote from: The_Immortal on October 30, 2017, 12:48:18 PM

Quote from: dstm on October 30, 2017, 12:38:38 PM

Quote from: The_Immortal on October 30, 2017, 12:31:56 PM

Quote from: dstm on October 30, 2017, 11:06:25 AM

Quote from: The_Immortal on October 30, 2017, 10:57:39 AM

Quote from: dstm on October 30, 2017, 10:43:41 AM

Quote from: The_Immortal on October 30, 2017, 10:30:54 AM

dstm, thank you.

And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.

Could you tell me please why is that? ZM cannot properly work with proxy under Linux?

No, there are no issues with proxies on linux, some people use zm with proxies.
How do you setup your proxy?
Are you blocking ports? ZM requires port 3443 to be open to be able to submit it's dev fee shares, it won't work if it's not able to do so.

Code:

zm --server 192.168.32.119 --port 7777 --user my_wallet.worker_name --pass x

192.168.32.119 - proxy-server
7777 - port which is mapped to eu1-zcash.flypool.org:3333

Well, should I open the port 3443 on proxy-server as well? And where should I map it then?

eu1-zcash.flypool.org:3443

Well, I set mapping local tcp port 3443 to eu1-zcash.flypool.org:3443 on proxy-server - the same result: Connection refused

Code:

# GPU0 connected to: 192.168.32.119:7777
connect: Connection refused

Again, under Windows with the same config there is no problem with connection...
And again, linux EWBF works properly with such settings.

How can I get what is the problem?

Sry, I forgot to mention you have to do some more configuration.
I'll think about a better solution later.

This might be helpful.
https://bitcointalk.org/index.php?topic=2021765.msg23213269#msg23213269

Well, I see the solution:

Quote from: dr. on October 19, 2017, 02:17:33 AM

I've managed to solve it easily by additionally remapping local port AND pool hostname (3proxy+edited windows hosts file, in my case)

But have no idea how to do it... Need an example Sad

Quote from: dr. on October 19, 2017, 02:17:33 AM

It seems you've hardcoded pool addresses for devfee, so they don't actually went through proxy even if I forward the right port (3443 in my case).

Could you please simplify your code just to use an ordinary port forwarding?
The problem is all my rigs can connect only via proxy-server Sad

I see. There is currently no better solution, it's on my todo list.

But could you tell me please what should I put into Windows hosts file then? Something like that:

Code:

localhost:3443 eu1-zcash.flypool.org

?

It hasn't changed anything tho...