I tried to find useful information about the stratum proxy server, but it appears to be old source code, and the majority of the results here on the forum are a little old, so I am not sure why your setup does not work, but based on the error, the proxy may be modifying something, such as the username and password, or submitting incorrect credentials.
If your purpose is just to use proxy and optimize the network I think this one below should be able to help you it's a free tool from Bitmain for proxy solution.
- https://www.zeusbtc.com/tools-download/details/5600-antminer-antproxy-tool-download
Topic: Issue with Mining Proxy for Pool Connection - "Unauthorized Worker" Error (Read 45 times)
January 02, 2025, 04:15:02 PM
December 30, 2024, 02:10:53 PM
I don't think ViaBTC restricts miners from using proxies.
Have you tried to connect your miner without the proxy? If it's connecting properly, meaning the proxy might be the issue, you need to change it to maybe HTTP proxies instead of using socks5 and proxies that encrypt data sent to the pool server.
Would you mind to share the unit model of your miner?
And the type of proxy you use(HTTP, Socks4, Socks5)?
Have you tried to connect your miner without the proxy? If it's connecting properly, meaning the proxy might be the issue, you need to change it to maybe HTTP proxies instead of using socks5 and proxies that encrypt data sent to the pool server.
Would you mind to share the unit model of your miner?
And the type of proxy you use(HTTP, Socks4, Socks5)?
Yes, I've tested direct connections to ViaBTC without the proxy and it works perfectly fine. This confirms the issue is with the proxy implementation. I'm using a custom Stratum protocol proxy, not HTTP/SOCKS. I'll continue debugging the authorization handling in my proxy code since that seems to be the root cause.
I'm renting hashpower through MRR for SHA256 Asicboost mining (1.12Ph/s advertised). The miner is located in Russia and I'm testing a custom Stratum proxy to handle pool connections.
Type: SHA256 Asicboost
December 30, 2024, 11:36:38 AM
I don't think ViaBTC restricts miners from using proxies.
Have you tried to connect your miner without the proxy? If it's connecting properly, meaning the proxy might be the issue, you need to change it to maybe HTTP proxies instead of using socks5 and proxies that encrypt data sent to the pool server.
Would you mind to share the unit model of your miner?
And the type of proxy you use(HTTP, Socks4, Socks5)?
Have you tried to connect your miner without the proxy? If it's connecting properly, meaning the proxy might be the issue, you need to change it to maybe HTTP proxies instead of using socks5 and proxies that encrypt data sent to the pool server.
Would you mind to share the unit model of your miner?
And the type of proxy you use(HTTP, Socks4, Socks5)?
December 30, 2024, 10:16:30 AM
Hi everyone,
I'm setting up a mining proxy to improve efficiency and reduce bandwidth and maintenance costs when connecting miners to pools. However, I'm encountering an issue while submitting shares to the pool.
The pool I’m trying to connect to is ViaBTC, and the problem occurs when the proxy tries to submit a share. The pool responds with an "Unauthorized Worker" error (error code 24), even though I’ve double-checked the worker credentials and they match the pool's configuration.
My Questions:
Could this be related to the way my proxy handles authentication with the pool?
Are there specific configurations or settings I should verify for ViaBTC?
Has anyone experienced a similar issue with their mining proxy, and how did you resolve it?
If anyone has experience with this or ideas on how to fix it, I’d greatly appreciate your help. Let me know if more details are needed to troubleshoot the issue.
Thank you in advance for your support!
I'm setting up a mining proxy to improve efficiency and reduce bandwidth and maintenance costs when connecting miners to pools. However, I'm encountering an issue while submitting shares to the pool.
The pool I’m trying to connect to is ViaBTC, and the problem occurs when the proxy tries to submit a share. The pool responds with an "Unauthorized Worker" error (error code 24), even though I’ve double-checked the worker credentials and they match the pool's configuration.
My Questions:
Could this be related to the way my proxy handles authentication with the pool?
Are there specific configurations or settings I should verify for ViaBTC?
Has anyone experienced a similar issue with their mining proxy, and how did you resolve it?
If anyone has experience with this or ideas on how to fix it, I’d greatly appreciate your help. Let me know if more details are needed to troubleshoot the issue.
Thank you in advance for your support!
Jump to: