Yes, thats correct. I wondered why Futurebit uses no IEE vendor specific mac address but a private one (C2:1A:02....)?

Did you open up port forwarding TCP to port 8333 in your WAN router for the Apollo's LAN IP address?

Where do you see that in the Web-IF?

This is a high end Gen4 SSD. Also the version without the additional heatsink will IMHO not work. Wasted money for an Apollo miner....

The only officially supported NVMe drives are Kingston NV2s and Curcial P2/P3s.

We have also noticed some newer Gen4 drives are not compatible and this is a hardware issue. Our custom SSD drive adapter for this board is only designed for 2x PCIe Gen 2 lanes.

There is no need to buy higher end NVMe drives for this system as its a waste, they will either fail because they draw to much power, or newer Gen4 pcie protocol is incompatible with our hardware.

We are currently sourcing Kingston NV3 drives, but only one type with a certain controller works with our system, they have two types with a different controller that does not work.

Also I know 660GB/1TB seems like the drive is almost full, but bitcoin is growing at about 100GB/Y even in its current maxed out full blocks state. 1TB drives have at least 2-3 years of life left, and 2TB drives will literally last the life of the system at over 10 years.

2TB is boarderline overkill, 1TB will last enough where you can get a 2TB for half the cost in 2 years.
[/quote]



Does a Gen 3 drive work? Specifically a Crucial P3 Gen 3 x 4
model# CT2000P3SSD8

[/quote]

I successfully installled a 2TB Samsung SSD 980 Pro on my Apollo BTC which works with smooth temperature.
Apollo support team confirmed most low end M.2 SSD drives will work. They do not recommend to buy higher versions as the Apollo can't take advantage of faster link speeds (sometimes will not work due to power requirements -> The Apollo BTC controller is rated for 3A at 3.3V so max is around 10 watts acc. to them).  They have tested Kingston and Crucial drives with their Apollo systems.


Other questions:
- For the (very unproble case) that my Apollo Solo Miner will maybe find a block in the future somewhen, where would this be shown in the Apollo 2.0.6 Web-IF?
- Anyone knows why Apollo miners use private MAC addresses?

Thank you for your answer.
No, I run the Apollo Server as a pure network server (without keyboard, mouse and monitor).
Regarding “sudo apt update” and “sudo apt upgrade” I don't share your concerns.
As far as I have understood the support, you just should not do a distribution update, but these updates are ok (as they also contain security fixes) and can be done in addition to the Web-IF updates from Appollo.
My Apollo 2.0.5 system runs very stable even after having installed the latest Ubuntu OS updates with above commands using SSH.

To get others to connect to your BTC node, you must enable port forwarding in your router to the apollo node.

Example:
Inbound rule:
Allow ANY SOURCE IP:Protocol:TCP:ANY SOURCE PORT -> APOLLO INTRANET NODE-IP:Protocol:TCP:PORT:8333

I highly advise to configure suitable internal and external firewall rules, accordingly, and place the Apollo node into a VLAN network which is separate from your normal untagged intranet LAN.

Example:
internal firewall: full isolation of apollo server from intranet network. Except access for specific admin device (allow access to web-if (port 80) and SSH (port 22)).
external firewall: allow access from any external port to apollo server tcp port 8333 only.

As Ubuntu is a very save OS, I have no real doubt to get hacked.
However, you could consider additionally using TOR via flag in settings, to increase security.

You can try out, if your node is accesable using this:
https://bitnodes.io/#join-the-network

Funny, but after a system reboot, It works now as intended and shows the miner working on my local node.

Yes, I am.

I have configured my Apollo BTC miner (firmware v2.0.5) for solo mining with the new easy GUI function. So I just had to enter my personal BTC wallet address and nothing more. My intention was to have my miner running directly attached on my local node.

Configuration: SOLO settings > Mine directly to your Bitcoin node > activated "SOLO Mining mode"

However, when I click in the GUI on "Solo mining", I get this message: "CK Pool Disconnected! Please check your node connection and the CK Pool status."

Is this message normal and can be ignored? Or do I still have to connect to ck pool?

PS: Can anyone please provide a reply on my question above regarding the update of the pending Ubuntu packages? I would highly appreciate any help, too

got it fixed with changing "/etc/apt/sources.list.d/nala.list" from
to

I tried a "sudo apt update" after I had sucessfully completed a "sudo apt upgrade" via SSH using Putty.
Unfortunetlay, with the latest firmware version v2.0.5 (MCU2) I am getting the following error message:


Can you maybe explain to me, how I can solve this issue? Thanks for your support!