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

Has anyone used the NODE Configuration to set up ledger live access?  If so, would you please share how you configured the node from the settings file?
'

Both MCUs are identical and will be supported with any software updates, the new version just has different components that are more readily available and needs a different kernel to run so thats the reason for two versions.

Not sure about the virtual keyboard, is this occurring with the new image?

Excellent news!  Congrats to the whole Futurebit team on the update. 

I look forward to updating as soon as I backup the Home Assistant data, which I just installed on Monday and loving so far (for those interested).

Two questions from me:

 - being a Batch 3 owner, will there be future updates/features that come to the new MCU2 and not to MCU1?  Hope I'm on a 'retired' or 'legacy' hw platform after only a few months.

- after reboot, at the login screen, is there a reason virtual keyboard is disabled/not loading?  I share a keyboard between my workstation and futurebit.  Was hoping to use the virtual key board to login, but doesn't appear to work.  Was this intentional?

That's extremely odd. Best bet I guess would be to wait for FutureBit to post the 0.3.4 images and then flash the SD card from that. Alternatively you could try to reflash 0.3.2 and see if a fresh install will trigger the update prompt

Dont have it.  I would post a screen shot if allowed.

You should get a notification in the top right of the WebUI

v0.3.4 of the Apollo UI has been Released!

Security:
-Fix vulrablilites when dashboard is exposed to public IP
-Bitcoind RPC is now randomly generated internally and only accessible via dashboard settings
-FutureBit user system password is now updated to dashboard password during initial setup

Feature:
-Option to enable Bitcoin Node to run via TOR network
-Users can directly edit bitcoin.conf via dashboard and edit their own settings (ie ipallow for external wallet connections etc)
-Better error handling and displaying UI faults to user

Fixes:
-UI stat bug cause by old corrupt log files
-Issue causing internal error when both wifi and ethernet interfaces are used
-Additional bug fixes and improvements

You should see a yellow update button on your UI, press this to start the update and wait until either the UI automatically reloads, or refresh your browser once you see your Apollo start mining again.

If you encounter any issues wait at least 15 minutes before you do anything as rebooting or power cycling during an update thats not complete can brick your system. Rebooting should fix any UI issues after the update.

Updated image with new UI as well as updated OS subsystem will be released next week.

Also encountered a small issue where if your Apollo has over 2-3 months of uptime, pulling the new update from git might not work, so if you have a really long uptime reboot your Apollo before starting the update (good practice either way to reboot it before performing updates as that clears memory and caches that could stall the update).

It much harder to discover nodes over tor, it takes a while but should eventually get up to near the max connections.

Appreciate the reply but unfortunately it did not work.

rpcallowip=123.456.7.890 in the config box. computer ip where ledger live is installed.

Then on ledger live connect node enter my ip address of the futurebit miner along with the port number example 123.123.1.123:8333

user futurebit password from settings page. Have tried this in TOR mode as well and still nothing.

Yes, with the new update all you have to do is add the line

rpcallowip=youripaddress

in the settings page of your node and save. IP address has to be the local IP address of your computer you have ledger live installed. You then can enable the connect full node settings in ledger live using your nodes ip address and its RPC credentials (username futurebit RPC password displayed in settings). Obviously both the node and your computer have to be on your local network for this to work.

That should do it and allow you to broadcast your Bitcoin txs through your own node via your ledger hardware wallet!

trying to connect my node to ledger live....will this work ?
has anyone tried and got it working ?

Worked like a charm, I should have checked the worker on Slushpool before posting as it has been active for 35 minutes.

This has also been my experience using the new TOR connection option