"So it appears the node goes offline only when I connect to it after a few minutes (via Sparrow Wallet). Can it be because it is overheating, connecting to the node actually makes it run hotter?!? I bought the unit couple years ago and I just cleaned it so it shouldn't overheat? The fan is on Auto as well."

You are not the only one, I am having the exact same issue. My node runs fine until I connect remotely to Sparrow, after which it randomly shut down in minutes or hours.

As per my previous reply, my Apollo has been rendered useless since last week. Node can't even go 12 hours without randomly going offline. Mining just fine otherwise. Nothing seems wrong and others report the same problem.

I have been having the exact same issue, which means it's not us but something wrong on futurebit's end. I wrote them and they never wrote back 

Fairly confident Ledger Live will not work with the Apollo node. Couldn't get Sparrow wallet to work either, or Wasabi. Now using Specter desktop wallet and it works flawlessly.

Ran the update this morning, which is now stuck at "Hold on, page will reload in a few seconds..." It's been at that stage for over 30 minutes. What should I do if anything?

Thanks for the replies, after a day of pulling my hair out I finally figured out what the problem was - no space after my "," when inputting my DNS parameters; 8.8.4.4,8.8.8.8 does not work (which is what the tutorial shows). No error message pops up when setting this up in Ubuntu so after trying again for the 100th time I changed that up and it worked. I appreciate again the responses.

I've searched the the thread for help on changing the IP address on the machine and can't find what I need. I am following the standard Ubuntu instructions for changing to a static IP address, but after hitting "Apply" and toggling the switch the network settings don't change. Is there something particular about the Apollo setup that is preventing me from changing the IP address?

Thanks folks for the feedback. My router does support UPnP but I don't use it (for reasons some of you shared) and it is turned off. Deleting the upnp=1 in my config file solved the issue and the node is no longer looking for a upnp igd.

I just deleted the upnp=1 from the bitcoin.conf and rebooted the node, now that error script no longer appears. I was following a guide from bitcoin magagazine on setting up Sparrow with your node that includes that line and it's not necessary since I'm not using upnp.

Thanks for the reply. I did read through that thread you shared prior to posting but it didn't really answer my question. I do have upnp=1 in my configuration file and I think it is related to this, but I am not sure what any of it means tbh.

Hello,

I am getting this message in my debug.log, and am not sure what it means or if I should do anything about it? My node seems to be working fine and I can connect to it via my Sparrow wallet. TIA

Any updates from the team lately? Nothing on any social media since March 20th. The team has not met some important Q1 benchmarks listed in the Whitepaper that has me concerned. IQN is NOT listed on any exchanges, despite what they announced, is it because the tokens are locked up for two months after the ICO ends? Also, to my knowledge there has been no "marketing campaign to attract end users." Are they posting progress somewhere?