Quote from: t3c on Today at 11:19:08 AM

Another Feb 14th purchaser with the same issues I can see cited here by many in the thread.

The node simply will not connect and on the occasions when it did it never got past block 225K before restarting from scratch again.

Reformatted the SSD 4 times now, the same thing happens or I get Connection Refused error or There was an error getting stats for Node: ETIMEDOUT.

Miner is not running.
Port 8333 is open and reachable.
500mb/s up & down direct to premises fiber.
Tried both static and DHCP LAN addresses. Same issues.
I have reindexed. Same issues.
Unit now intermittently clicks when on and nothing is running (no miner, no node)

I'm an EU user so am starting to think the RMA process will be a painful and expensive experience for me along with the import taxes/duties due on this unit still to pay (i knew what i was getting into in respect to that of course).

I have logged a support request via the online form and email so I guess now I wait for a reply as the 14 day cut off to log an RMA is on Wednesday/Thursday since the unit was finally delivered to me out here, I take my support email as notice to FB in respect to logging a potential RMA.

So far it's been an extremely disappointing experience with my Apollo II. I run a few Bitaxes and was a Butterfly Labs OG back in the day so this isn't my first rodeo with mining hardware but my unit seems seriously buggy/flawed in how it's trying to operate. Starting to think I should've gone with Umbrel or Start9 in running my own node and simply got more Nerd/Bitaxes for hashing but like many here I wanted to support FB and have an all in one unit capable of hashing and running a node from one box. It's a great looking unit the Apollo II but if it cannot do the 1 main thing it was designed to do it's completely useless.

This was supposed to be a plug & play node/miner and so far after the 2 days I have had trying to get it to work correctly it has been far from it in that regard.

Just reply to your order email and will take care of it. As mentioned before in the current batch of controllers we are seeing a few % of them with bad memory chips (either production issue or actual bad chips), which is causing the node to fail to sync.

If you have gone through the normal troubleshooting (reflash your SD card, and reformat your node SSD drive by going to the settings and then extras menu) and it still fails to sync most likely thats whats going on.

If your in EU we can just send you the controller itself to swap out, its relatively straightforward to do.