Pages:
Author

Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 20. (Read 48581 times)

newbie
Activity: 41
Merit: 0
What info do I need to point my miners that are currently hosted offsite to my Apollo? I’m currently solo mining from the Apollo and want to add some more hash using my other miners.



they would need to open port 3333 on their WAN address to point to your Apollo's internal ip address (or can be any wan port, just needs to point to port 3333 on the apollo).

Thanks John! Do i need to create a stratum something that looks like this stratum+tcp://btc.f2pool.com:1314 for my Apollo though?
legendary
Activity: 2174
Merit: 1401
Question: When solo mining, it says  "Mine directly to your Bitcoin node" does that mean we need an address that comes from the node? Or any address will work?
Also, has any Apollo found a block yet?

Any legacy or non script segwit address will work, the newer longer segwit/taproot addresses wont work for solo mining.

Not yet, but someone found a 42 trillion share so far (highest that I know) which is 1/2 network diff...we are also going wide release and will push an email + UI upgrade soon so if a large majority of all apollo users go solo there should be a block pretty fast.

Of course we have no idea what our users are doing, where they are mining or what % is solo vs pool etc so can be difficult to gauge.


Have mid-April orders started shipping?


I think all April orders are out right now...starting to work on May after the July 4th holiday, and should probably clear the whole backorder queue by end of may!
legendary
Activity: 2174
Merit: 1401
What info do I need to point my miners that are currently hosted offsite to my Apollo? I’m currently solo mining from the Apollo and want to add some more hash using my other miners.



they would need to open port 3333 on their WAN address to point to your Apollo's internal ip address (or can be any wan port, just needs to point to port 3333 on the apollo).
newbie
Activity: 41
Merit: 0
What info do I need to point my miners that are currently hosted offsite to my Apollo? I’m currently solo mining from the Apollo and want to add some more hash using my other miners.

newbie
Activity: 1
Merit: 0
Hello,

I have an Apollo 2 that has been running fine for a couple months now. Turbo mode in my garage with on a shelf that has 360 degree air flow. The temps stayed around 74C all the time which, according to the gauge in the software was fine. I upgrade to 2.0.5 and have not been able to to use the Apollo since. It keeps shutting off. I was able to get into for a sec and turn it down to ECO mode but it died again shortly afterwards. I'm not sure what is happening. I can't get it to stay on long enough to troubleshoot. I tried to re-image the SD with 2.0.5 but, I couldn't even get through the start up page. I'm active working on downgrading it back to 2.0.4 right now. Anyone have any ideas??

I reimaged to 2.0.4. It ran for about 3-5 minutes and now it won't stay on for longer then 1 minute.
newbie
Activity: 53
Merit: 0
Question: When solo mining, it says  "Mine directly to your Bitcoin node" does that mean we need an address that comes from the node? Or any address will work?
Also, has any Apollo found a block yet?

Any legacy or non script segwit address will work, the newer longer segwit/taproot addresses wont work for solo mining.

Not yet, but someone found a 42 trillion share so far (highest that I know) which is 1/2 network diff...we are also going wide release and will push an email + UI upgrade soon so if a large majority of all apollo users go solo there should be a block pretty fast.

Of course we have no idea what our users are doing, where they are mining or what % is solo vs pool etc so can be difficult to gauge.

Thanks for the info.

Also, is it possible/doable to upgrade the fan of the Apollo II ? I find it pretty loud, not sure what kind of fan it is. I live in hot weather so the fan spins faster.
jr. member
Activity: 122
Merit: 4
Question: When solo mining, it says  "Mine directly to your Bitcoin node" does that mean we need an address that comes from the node? Or any address will work?
Also, has any Apollo found a block yet?

Any legacy or non script segwit address will work, the newer longer segwit/taproot addresses wont work for solo mining.

Not yet, but someone found a 42 trillion share so far (highest that I know) which is 1/2 network diff...we are also going wide release and will push an email + UI upgrade soon so if a large majority of all apollo users go solo there should be a block pretty fast.

Of course we have no idea what our users are doing, where they are mining or what % is solo vs pool etc so can be difficult to gauge.


Have mid-April orders started shipping?
legendary
Activity: 2174
Merit: 1401
Question: When solo mining, it says  "Mine directly to your Bitcoin node" does that mean we need an address that comes from the node? Or any address will work?
Also, has any Apollo found a block yet?

Any legacy or non script segwit address will work, the newer longer segwit/taproot addresses wont work for solo mining.

Not yet, but someone found a 42 trillion share so far (highest that I know) which is 1/2 network diff...we are also going wide release and will push an email + UI upgrade soon so if a large majority of all apollo users go solo there should be a block pretty fast.

Of course we have no idea what our users are doing, where they are mining or what % is solo vs pool etc so can be difficult to gauge.
full member
Activity: 626
Merit: 159
Question: When solo mining, it says  "Mine directly to your Bitcoin node" does that mean we need an address that comes from the node? Or any address will work?
Also, has any Apollo found a block yet?

Any btc address will work.

Apparently this was incorrect so striking this!
newbie
Activity: 53
Merit: 0
Question: When solo mining, it says  "Mine directly to your Bitcoin node" does that mean we need an address that comes from the node? Or any address will work?
Also, has any Apollo found a block yet?
legendary
Activity: 2174
Merit: 1401
Hello all,
I just got my full node apollo 2 preorder, followed the set-up instructions with HDMI connection and after 20 mins the fans don't slow, and it doesn't boot to the log-in screen. I have also tried the ethernet setup with similar results, fans do not slow, and device does not show up on my list of connected devices on my router. Any tips from here?

Sounds like it's not booting, make sure SD card is firmly in slot (click in/out) and try flashing the card with latest image release. Reach out to support if you are still having issues.

https://www.futurebit.io/flashing-sd-card
newbie
Activity: 1
Merit: 0
Hello all,
I just got my full node apollo 2 preorder, followed the set-up instructions with HDMI connection and after 20 mins the fans don't slow, and it doesn't boot to the log-in screen. I have also tried the ethernet setup with similar results, fans do not slow, and device does not show up on my list of connected devices on my router. Any tips from here?
legendary
Activity: 2174
Merit: 1401
my internet went down. After the provider got it back online the apollo two needed restarted now the miner connects to the pool but the node has this error -111 ECONNREFUSED I have rebooted it several times

was there a power outage as well? Might have corrupted your node if you keep seeing this. You can either reformat the whole node drive in settings our reach out to support so they can try and debug it for you (might be able to recover with a reindex of chainstate).
jr. member
Activity: 107
Merit: 7
my internet went down. After the provider got it back online the apollo two needed restarted now the miner connects to the pool but the node has this error -111 ECONNREFUSED I have rebooted it several times
legendary
Activity: 2174
Merit: 1401
FYI can confirm etcher has a bug in latest release on Mac that causes it to fail flashing from a .img.xz file. Workaround for now is to decompress the file first and then flash.

Not sure if this is happening on windows/linux.

EDIT: yea latest release is garbage. balena screwed up a nice app when they bought them.

Latest stable release I can find that works on Mac/linux is this release: https://github.com/balena-io/etcher/releases/tag/v1.18.11
legendary
Activity: 2174
Merit: 1401
Apollo OS v2.0.5 image releases are out:

https://github.com/jstefanop/apolloapi-v2/releases/tag/v2.0.5

Anyone with OTA upgrade issues can upgrade with this reflash, this is the first non beta stable release that will be officially pushed to all Apollo BTC users still on the old UI. Everyone that has not tested the beta now is the time to upgrade!



After a lot of updates from the gui without success to reach the dashboard and I just flashed the fresh released image and …. Same behavior can’t reach the dashboard ( cleared the cache of all my browser, tried on differents computers phones ect … ) seems that a firewall problem ? I haven’t got any issues with the 2.0.4 beta …
I have an MCU1

Are you able to access the dashboard when you log in via a monitor?
jr. member
Activity: 31
Merit: 4
Apollo OS v2.0.5 image releases are out:

https://github.com/jstefanop/apolloapi-v2/releases/tag/v2.0.5

Anyone with OTA upgrade issues can upgrade with this reflash, this is the first non beta stable release that will be officially pushed to all Apollo BTC users still on the old UI. Everyone that has not tested the beta now is the time to upgrade!



After a lot of updates from the gui without success to reach the dashboard and I just flashed the fresh released image and …. Same behavior can’t reach the dashboard ( cleared the cache of all my browser, tried on differents computers phones ect … ) seems that a firewall problem ? I haven’t got any issues with the 2.0.4 beta …
I have an MCU1
legendary
Activity: 2174
Merit: 1401
Apollo OS v2.0.5 image releases are out:

https://github.com/jstefanop/apolloapi-v2/releases/tag/v2.0.5

Anyone with OTA upgrade issues can upgrade with this reflash, this is the first non beta stable release that will be officially pushed to all Apollo BTC users still on the old UI. Everyone that has not tested the beta now is the time to upgrade!

legendary
Activity: 2174
Merit: 1401
Anyone had a successful flash to 2.0.5? I'm a bit weary to upgrade until others report some success, don't have time currently to stuff around reflashing SD cards

It seems it's worked for me because the node is running and the solo mining works.. but i can't reach the dashboard via the browser. Didn't test to plug the apollo directly by hdmi.

Update now reboots system, if you are accessing over web ui on another device the IP address most likely changed on reboot and you'll need to enter new ip address

Keep in mind update takes a while (15-30 minutes since whole UI is rebuilt from source) so it will get stuck in the 60-70% range for a while, dont touch or reboot the system until it reboots by itself otherwise the build will fail and you'll get a broken UI.

I'll have the 2.0.5 images up today (or you can re-image using 2.0.4 and try the OTA update again).

How do I find a new IP address? The full node made no indication of a new IP and simply doesn’t load.

Download an IP scanner or log into your router settings/app this list the devices.

These URLs should also work if you are on a Mac/linux machine to avoid needing ips..

futurebit-apollo-2.local

futurebit-apollo-btc.local

None of the above worked so I just reflashed the OS. Went through setup as normal and tried upgrading again. Everything seemed fine but the version still states 2.0.4 with an option to upgrade to 2.0.5. Any idea why? I am using the native UI of the apollo 2 full node.

Nevermind! It seems to have worked because when I logged in on another device on my network, it properly reflected the new 2.0.5 version. I then reloaded my browser on the unit and it is showing the correct version. Thanks for all the help!

Mine is behaving similarly after upgrading to v2.0.5, it seems to be successful after installing it OTA and rebooting eventually (and the hashrate font is noticeably bigger after that), but it seems to eventually revert back somehow and loads the old 2.0.4 version of the site, the font gets small again, and then the power button flashes and offers an upgrade again, labelled v2.0.4beta at the bottom of the power button menu.  However, doing a full refresh of the tab, or opening it in a new browser tab, brings it all back to 2.0.5 with the bigger font... for a while at least.  This keeps happening so far, this loop.

Restart your browser/ clear your browser cache, it's saving the old version of the site that keeps getting loaded.

Some browsers are worse than others with this behavior.

Thanks, tried that, so far it's working and hasn't loaded the old version of the site.  FYI, when this issue is happening, the web interface is trying to download/install the new version over and over, so it might be worse than a visual/cache issue, depending on what is actually happening there.

You mean the update button is orange? yea if its loading the old UI it will think its on the old version and prompt you again for the update (it does not do anything unless you force the update though).

Have to keep in mind the Apollo is essentially a web server, so while it serves your browser the latest version on the device itself, modern web browsers are designed for speed and efficiency and rely heavily on cache which causes weird issues like this that can only be resolved with a cache clean after an update.
newbie
Activity: 10
Merit: 0
Anyone had a successful flash to 2.0.5? I'm a bit weary to upgrade until others report some success, don't have time currently to stuff around reflashing SD cards

It seems it's worked for me because the node is running and the solo mining works.. but i can't reach the dashboard via the browser. Didn't test to plug the apollo directly by hdmi.

Update now reboots system, if you are accessing over web ui on another device the IP address most likely changed on reboot and you'll need to enter new ip address

Keep in mind update takes a while (15-30 minutes since whole UI is rebuilt from source) so it will get stuck in the 60-70% range for a while, dont touch or reboot the system until it reboots by itself otherwise the build will fail and you'll get a broken UI.

I'll have the 2.0.5 images up today (or you can re-image using 2.0.4 and try the OTA update again).

How do I find a new IP address? The full node made no indication of a new IP and simply doesn’t load.

Download an IP scanner or log into your router settings/app this list the devices.

These URLs should also work if you are on a Mac/linux machine to avoid needing ips..

futurebit-apollo-2.local

futurebit-apollo-btc.local

None of the above worked so I just reflashed the OS. Went through setup as normal and tried upgrading again. Everything seemed fine but the version still states 2.0.4 with an option to upgrade to 2.0.5. Any idea why? I am using the native UI of the apollo 2 full node.

Nevermind! It seems to have worked because when I logged in on another device on my network, it properly reflected the new 2.0.5 version. I then reloaded my browser on the unit and it is showing the correct version. Thanks for all the help!

Mine is behaving similarly after upgrading to v2.0.5, it seems to be successful after installing it OTA and rebooting eventually (and the hashrate font is noticeably bigger after that), but it seems to eventually revert back somehow and loads the old 2.0.4 version of the site, the font gets small again, and then the power button flashes and offers an upgrade again, labelled v2.0.4beta at the bottom of the power button menu.  However, doing a full refresh of the tab, or opening it in a new browser tab, brings it all back to 2.0.5 with the bigger font... for a while at least.  This keeps happening so far, this loop.

Restart your browser/ clear your browser cache, it's saving the old version of the site that keeps getting loaded.

Some browsers are worse than others with this behavior.

Thanks, tried that, so far it's working and hasn't loaded the old version of the site.  FYI, when this issue is happening, the web interface is trying to download/install the new version over and over, so it might be worse than a visual/cache issue, depending on what is actually happening there.
Pages:
Jump to: