yup same I’ts all down to there internal DNS issue’s proven by sending ping’s to the servers. which are all over the place last night I got over 280ms for eth.hiveon.net and 15ms on eu-eth.hiveon.net, but this morning they have all dropped back down.
Only change on my internal network is last nights results were taken on a quiet network (only me using it) and this mornings results kids are up so everybody is connected and using youtube on several devices.
I have 2 identical rigs on ethermine and hiveon from weeks , and i confirm that the payout difference is 9% , so ethermine is far better that hiveon, this is sure .(i have a third on binance and is same as hiveon)
Also this problem in stats it translated in loss of mining , they sayd “mining is not affected” , but i can confiem that for all my rigs i got no money for all that time , if i look at stats visa hiveon it seems all normal , but it isnt , the money are missing , i repeat , if i had not XLS stats in these weeks i never noticed …
this is very bad , i can confirm that ETHERMINE is by far the best pool , not only for payout amount, but cause they never has problems or even stats errors …
Agreed. I lost income on my rig as well. They lied about mining not being affected, and to make it worse they didn’t announce any “upgrades” beforehand and didn’t warn anybody. Also, I reached out to chat support yesterday to ask what was upgraded and I couldn’t get an answer directly from them. This company is very suspicious. They had a lock on DNS server settings and had a hardcoded DNS server that had a redirect address 127.0.1.2 or something like that. I battled with support about that for several days and asked what’s this redirect going to and I was never given an answer. All of a sudden, the hardcoded DNS was “fixed” quietly and wasn’t even mentioned in the changelog. I can’t trust this company enough to mine on their pool. I can imagine they’re making tons of money redirecting and misreporting hashpower.
You are right 100% , i Love HIVE OS , but you cannot claim “free pool” while you steal 8/10% of the hash power !
Now i understand why big farmers goes with hiveos but do not mine in their pool …
To be fair i have to tell that also BINANCE POOL is giving more or less same as HIVEON , it seems that ethermine is on another level …
Also i tried DUAL mining on shardpool , ETH on Ethermine (via their proxy ) and ZIL on shardpool , and agai nthere is a 10% loss … so they claim " you will get 3/4% of ZIL fro free!" but in the meanwhile you are loosing 10% of ETH …
I also appreciate that HIVE people do not close the undesired topics and let us talk freely !
I confirm that the mining incomes from the “dead statistics period” was added yesterday , so it seems that nothing was lost … still stays the 10% difference with ethermine, but important is that we didnt loose that day , they should have make some calculations and added manually i think …
Yeah…they say that their infrastructure upgrades doesn’t affect mining but it most certainly affects mining.
Here is console output just now:
20210824 20:34:07 Using protocol: stratum1.
20210824 20:34:07 Authorizing...
20210824 20:34:07 WARN: failed to ethproxy-subscribe on naw-eth.hiveon.net:24443: can't parse json:
* Line 1, Column 1
Syntax error: value, object or array expected.
20210824 20:34:07 ERROR: No connection, retry after 10 seconds
It’s too bad that ethermine makes the miners pay the transaction fees for payouts because you can lose quite a lot as a result of that.
I think that my initial tests with ethermine post EIP-1559, I was paying like 50 Gwei for the payout.
That was crazy!
The good news is that HiveOn still pays the transaction fees when you have a payout. If you look on Etherscan for your payout transaction ID, it is still listed as transaction type 0 (legacy), so Hiveon, I think only pays like 1 Gwei transaction fee for that.
With ethermine, because you pay the transaction fee, therefore; you can get paid any time you exceed the payout threshold (which HiveOn only pays, once a day, at their specified time), but the transaction fee can eat into your profits by quite a significant margin.
I think that it’s up to each person to decide for themselves.
Subjectively, I’ve found that if you have a bigger farm, and your payout threshold (or how long you wait and/or are willing to wait before taking a payment is longer than most), then ethermine tends to work better because then you can get a larger payout, all at once, with one transaction fee.
But, I think that if you are a smaller miner, and/or that you don’t want to nor need to be paid out when you want to be paid out (i.e. you are ok with HiveOn’s payout time table/schedule), then HiveOn paying the transaction fee for you still might still be worth it).
These are just some subjective observations I’ve been able to loosely figure out with minimal arithmetic to show the calculations behind it.
(I ran this set of calculations for myself to try and figure out which was a better deal when EIP-1559 kicked in.)
YMMV.
re: getting back on topic - the issue that I am seeing
If I just reboot my system, it seems to connect back up to the pool without any issues.
I’m not sure why the system is complaining about it can’t read the JSON file when it was working fine when the system started up, and for hours on end, until it just suddenly stops working.
No idea why.
I think the error you’re getting is because of connectivity issues. During and since their “upgrade”, which they refuse to divulge what was actually being upgraded, their servers have had horrible issues with latency and connectivity. I actually think since EIP1559 they have actually DOWNGRADED their servers in order to save money and still offer a “free” pool. The servers in the east coast of the US have had 300ms or greater ping times since and every other server has had a significant increase in ping times. I don’t think they were upgrading anything. The loss of income and poor connectivity since clearly indicate that there was an actual downgrade. If you run the net stats command, you will see the HORRIBLE ping times from their servers worldwide, not just one particular set of servers. And even more alarming, if you run the test over and over consecutively, you will see that on each run there’s at least one or two FAILED connections to their API servers. As a client, I don’t see how HiveOS can actually pay for a service like that. I believe that they’re using CloudFlare free services as a CDN and you’re seeing the results of that.
Can you please tell me how you concluded that the loss of income was “added” yesterday. I’m genuinely curious how u made this deduction without actual internal access. I want to see if my losses were added yesterday cause I was off the pool for almost 12hrs and they haven’t added a penny.
fwiw: Have you used the newer feature in the flight sheets to measure access to the servers?
If you have multiple rigs, consider pointing at various primary/backup options or even pools.
I run my own Recursive Resolver (Unbound) from home and get usually 0.1-0.5ms response times to repeated/cached queries on Unbound. Even with this advanced setup, NOTHING helps HiveOS ping times. Just check your net stats, you won’t see a ping under 80ms from ANY server at any given time, usually it’s 300-3,000ms. In a situation like that there’s nothing the user can do. HiveOS obviously uses low quality servers or most likely a free or lower-tiered CDN plan. Nothing can be done about that. They have to upgrade their servers.
I’m not sure if that’s the case.
I would be more inclined to agree with your hypothesis if, after I reboot the system, it would still fail to connect.
The fact that a reboot appears to “fix” the issue would suggest something else.
I won’t be surprised if it was due to HiveOn “upgrading their infrastructure”, but again, the fact that a reboot appears to “fix” this issue - I’m not sure how I can make it “fix” itself WITHOUT having to do a reboot.
A miner stop/start doesn’t seem to be enough to try and rectify/resolve this issue.
re: ping times
The other potential hypothesis as to why their servers might have longer ping times CAN also be the fact that other people are realising that HiveOn pays the transaction fees (unlike ethermine) and therefore; people might be jumping on to the HiveOn pool for this reason.
I was actually originally mining on the HiveOn pool and then jumped on to the ethermine pool after watching a few of the YouTubers use ethermine, and then once ethermine implemented the change where miners would have to pay your own transaction fees to get your ETH out from the pool (like I said, I was paying like 50 Gwei to get my ETH paid out from ethermine), I jumped back onto HiveOn pool because HiveOn pays your transaction fees.
I think that more and more people are realising that this is the case, so I won’t be surprised if a part of the reason for the slow down is the increase in activity/traffic on the pool itself that HiveOn previously didn’t have.
That would be another hypothesis.
And yes, the ping times have gotten worse (actually, more importantly, the standard deviation for the ping times have gotten worse), but I’ve also historically didn’t get great ping times already in the first place (when I am trying to secure my system).
To your last point - I have no idea.
I was going to run some tests with the different local pool addresses, but it looks like that this might be a broader, systemic issue because I did notice the increase in ping times at least starting from about a week ago.
But the error message that I am getting/seeing now - this is more of a more recent development (as of at least the 20210818 HiveOn OS/client release).
(The good news is that it is very easy for me to roll back to an earlier version of their OS by just swapping out the hiveramfs.tar.xz file on my HiveOS diskless PXE server.)
As I stated earlier, I ran consecutive net tests for over an hour, and EACH AND EVERY TIME there’s was a minimum of 1-2 “Failed” connections to random API servers around the globe. That’s all the testing I need. IT is what I been doing for a living. I know how to test a network. Doesn’t matter if u agree with me or not, I have my own testing and experience tell me what I need to know. If there was a global OS issue, this forum would be filled with posts just like yours. Their pool and API servers are hosted on extremely low quality servers. It’s easy to see that.
“Just check your net stats, you won’t see a ping under 80ms from ANY server at any given time, usually it’s 300-3,000ms.”
That’s not necessarily true.
I just ping naw-eth-hiveon.net and this is what I am getting:
Check back again in a few minutes. The issue is intermittent and with different servers at any given time. Other posters have already stated this. Look at my example below. “Aaawave” is the name of the client, the rig, sent the ping in 2.2ms, the server took over 86ms to respond.
The data that I have doesn’t support your claims though.
Let assume that what you are saying is true.
So, then how do you explain where my average ping times is 20 ms vs. what you are seeing?
(I posted the screenshot from the ping test above. Statistics for that are as follows:
round-trip (ms) min/avg/max/med = 15/20/41/18)
(If you want me to run net stat and/or long duration ping tests, I can certainly do that. Not a problem.)
I don’t have your server or ISP skills, I am a small time miner.
I have a very tight “payout per days model” which has remained consistent. My payout results do not show a material deviation during the “stats blackouts” which would justify paying for HiveOS(maxed at 4) or transaction fees.
Full disclosure: I have “free” MMPOS rigs pointed at other pools to stay informed, tweak weak GPUs, and to be pointed at Hive pool to make up for my rig service outages on Hive pool rigs. My experience with some pools is definitely behind Hive on a per MH/s to net payout basis. I have not tried all the pools…yet 
Forgive my idiot question, but I don’t see, in the picture that you have attached, where it shows an 86 ms respond time.
It shows aaawave forwarded to unbound#5353 IP (2.3 ms).
I must not be looking at the right spot because I am unable to see the 86 ms reponse in the screenshot that has been provided.
Yes do that. Because several of us on this thread were testing extensively during and after the outage. You can get those ping times now, and in one hour the whole connection fails. Then switch to another server that seems good, and within a few hours those servers started lagging behind with 300+ms. We’re talking about pool and server ping times, if your issue isn’t that and your ping times are so great, open another thread and get the answers u need. Why r u here debating obviously bad ping times that everyone else is having
Because I compared it to the output on HiveShell net stat responses when I was doing my testing. Dude, just go somewhere. I been doing IT work since 1998, not debating networks or network testing with some random miner. If your issue isn’t bad connections, then u might have a corrupt file, or like I stated, intermittent loss of connection that made the file unreachable/unreadable. Either way it goes, this isn’t the thread for your issue if you’re so convinced it isn’t a network issue. In that case, open up a thread.
