Anyone else have the issue with this error at start?
It seems there is a problem to communicate with the miner, check error message.
SyntaxError: Unexpected end of JSON input
Wait at least 1 minute, if problem persists, try to restart the miner, check the settings or try to reboot the system.
I am running the full node by itself connected via cable.
Shoot us an email with this error, its very rare and it seems to be caused by a specific pool/configuration and trying to narrow it down. |
|
|
|
For a change, since this is also an image thread, I want to chime in with something other than a support request, and instead speak out a big thanks for this nice little machine to jstefanop and his team. I've restarted it a few times to change settings and such, but it never stopped on its own, crashed or anything like that. I did add a PC fan on top and one below, which I run off of 5V from the controller (so roughly half speed on these 12V DC fans - very quiet).  There are few things more pleasing than a system with weeks or months of uptime that just chugs along tirelessly. Thanks! Obviously this thread is full of support issues as that is its purpose, and couple dozen people with issues makes it seem like the product is full of issues but its nice to see posts like this once in a while since obviously there are thousands of happy customers and those thousands of people don't come on here to post they have no issues  |
|
|
|
When will be able to run a lightning node and how would i connect my storage wallet to my node?
This is what I want to know as well; it's been nearly a year of ownership for me and I've wanted this functionality from day one  Sadly its been a year of most of the team focusing on operations and supply chain issues to get all your orders out. We seem to have that mostly under control for the near future, and focus will definitely shit to building out our front end and features we have in the pipeline! |
|
|
|
Hello , i need a quick help here.
I bougth more cheap apollo no controller no psu.
Connect a apollo on normal atx supply , works fine.
But i not have sucess on configuration. First i tried windows, plug apolo micro usb in pc, and run binarie winx86...
The log says, waiting device COM(1)...COM(2).....
I got a orangepi pc, i tried flash stock rom, not work (orangepi not boot)
I tried again, run orangepi on normal OS , and run binarie for ARM , same result of windows.. Aparentelly , OS not found device connected by microusb cable.
Anyone have a tip , or guide setup basic to run ?? Im really trying run, but its hard..
You have to open your device manager in windows and find the COM port that associated to your Apollo (it will come up after the light in front goes solid red). You then need to edit the start.bat file with that COM port and your pool info etc. All the instructions are inside the start file. |
|
|
|
Hi in the dashboard my Apollo always show: SyntaxError: Unexpected end of JSON input I did reboot or reset the device but always the same error...  Shoot us an email with this error, we are trying to debug and see what's causing it since we have received more than one report of it. Also send your configuration environment (just full Apollo package, or 1 or more standards connected, wifi vs ethernet etc). |
|
|
|
Great deal! The stock power supplies are rated for 200watts and in turbo mode I was seeing 201watts in turbo. Isn’t this bad? I thought you’re supposed to leave a 20% buffer so that you’re not maxing out the psu? I tested these units on a 750w psu as well and if you abide by the 80% rule, you’ll need higher than an 850w unit if you’re going to run more than two units. I don’t recommend running these at max settings. I don’t live in a cold climate and these got really hot fast! 75C and the room was hot. I went from 12.5th/s in turbo @ 800watts to 14.5th/s at 1050watts for 4 units (two 750w psus). Each unit saw about 266wats at full speed. Mine runs at 205w on turbo mode Okay...and if your psu is rated for only 200w and you're operating above the 80% (which would be 160w) doesn't that concern you at all? The FutureBit PSU is already derated to 80%, its designed to run @ 200 watts 24/7. If this was a normal ATX PSU it would be marketed as a "250W" PSU. |
|
|
|
Hey guys newbie question. I have 2 full systems, only one running. If I open the second one should I just connect the miner without the power supply to the existing miner using micro usb ? Also if I cant run 2 nodes willl the miner set himself as mining only or I need to stop the node setting inside the Dashboard ? Thank you!
You need a power supply for the second unit. But then you can connect it it with the USB cable to the first unit. I would remove the SSD from the second unit as you don't need two nodes running. You can't connect two full node systems to each other. Each full node system controls its own hashboard, so if you try to connect it via USB to another one that's going to cause issues. You either run both of them separate, or you gut one and turn it into a "standard" unit. But that is a waste of $300. |
|
|
|
Hey guys….just wanted to follow-up on Stratum V2 - is that being developed for any other reason than asicboost or auto-tuning? Braiins OS? What does that pipeline timeline look like?
Anyone care to take a stab at this? @jstefanop? We are focused on direct solo mining, and expansion of apps included by default in the FutureBit OS right now (block explores, LND, wallets etc). Well probably work on startum v2 stuff after these are launched. Thank you Futurebit for delivering what you promised.   Cant wait to see what developments are in the works! And thank you for supporting us which is allowing us to deliver what we promised! |
|
|
|
Edit: I think my brother figured it out, DMZ was enabled and the FutureBit was the only thing on that list, maybe that's how they're getting in?
Assuming you have a consumer-grade router with DMZ enabled, your Apollo was likely compromised in seconds than minutes! Never ever put any device in such a DMZ without knowing what you are doing. (Such consumer-grade DMZs have most likely every port open - from SSH, HTTP, HTTPS, every port from 0 to 65535 ...) So, it seems your brother figured it out! Good! Remove Apollo from DMZ and back in the LAN where it should belong firsthand. Reset the Apollo to factory defaults and start hashing without any more disturbance. how to reset to factory defaults ?? Wazzzzz up....  ...now I know that we like to come on here and post questions and queries when we run into an issue with the miners and hey it is ok for I have posted a question on here at times myself...but indeed reach out also with your question to the support desk or team at Futurebit itself...it is why I was instructed to do at one time and they did respond to me... that email link addy as to where to write to them is... order@futurebit.io ...so indeed just post the question you do here on the forum to the email addy for them I just posted and well then wait for a response and well keep checking on here just in case as well...Ok folks I am outta here for a minute again...have to corral them chickens...hehehehe... ...Dr. J my man hope you and the crew are doing well and that things are churning along... ...Laterrrssss...    P.S. Oh by the way...Dr. J or anyone there at Futurebit...did any of you find or have the temperature numbers for the Futurebit miners...meaning at different settings in the configuration of the miner what are the temp ranges...so that well the users can just keep an eye out for the temps on the miners and that way no one damages their miner by accident you know...ok someone there hit us up on them numbers...thanks Fan controller automatically regulates temps within 60-70c which is normal operating range for all modes. In hotter environments/custom settings/turbo mode etc it can get to over 70c, but the chips are designed to operate at 80c continuously. Would not get worried unless you see temps above 80c. |
|
|
|
If anyone is interested in buying a full node+psu at an extremely discounted price, message me.
I have absolutely no desire to be apart of FutureBit with the obvious coding flaws that's allowed some sort of exploit through that's caused a great deal of us to all experience the same exact thing.
I'm currently mining 7 different coins with a dozen or so different miner manufacturers, Helium, a couple weather stations, GEOD navigators, etc... this is the only product I own I truly feel has a potential to completely compromise my entire network by the obvious back doors on these units.
First 400 takes it, it's less than 2 weeks old, I'll even throw in free expedited shipping.
Let's stop with the fear mongering please. Only you and one other person has reported this, and support has been in touch with one of you. Its been determined the issue is because you guys chose to expose your Apollo to the whole internet for anyone to attack. This akin to leaving your Bitcoin wallet on a table outside, publicly yelling out your address and telling everyone come and take it. The issue is with forwarding our webUI to the open internet. The webui is not a server grade hardened frontend, its designed for easy access and control of your Apollo from your LAN. While you can forward your WAN port 80 so you can bring your UI up from any and device/place what you are doing is essentially hosting it as a public web page that anyone can try to attack, and this is precisely what happened. Simply remove those port forwards and you will be fine(or go through the process of turning your Apollo into a hardened server grade web server). If you really want to be able to access your Apollo from outside your LAN in an easy and more secure way, then setup a remote access app directly in the desktop environment. |
|
|
|
update on my end. i thought i had it figured out. but i woke up this morning and was wrong..... so i reflashed, setup a totally different vlan than it was on, added it on a totally different wifi network instead of the same ether connection it was on before, setup the pool and password on startup, clicked on settings and users and changed the main password to one that is different from default and different than my dashboard login, fired it up, working great, temps around 45 and 62, ran great for 5-8 hours, woke up, changed back to slushpool and topminer01.........(i have tried using multiple pools, keeps reverting back to topminer01 on slushpool) is there something i'm missing? is there a different system password that someone could be accessing to get into it and change everything? i'm at a loss at this point.....
Where did you buy it? from futurebit. one full node and 3 standard units. OK just wanted to rule out third party tampering before you got it. What pool are you using? Have you tried other pools? yep i've used multiple. i am not currently using slushpool however. its so strange, i go through all these steps. it runs fine on the pool i set, then at random it will go back to this topminero1 workername on slushpool as others have seen. with reflashing and all that and setting the default pool to something totally different, i just can't understand how it keeps changing without some sort of a compromise or something. like i said, after yesterday, it had a new network, new ip, isoloated from anything else in my network, all the passwords on the unit that i know of changed, unless there's more i don't know about or some kind of a virus or bug or something.... OK The config file that the miner uses to populate the pool login details is called "miner_config" and is located in: /opt/apolloapi/backend/apollo-miner/ If you SSH into the miner you can cd to that directory and view it with "cat miner_config" command So I would first, SSH in while the miner is set how you like it, then check that file to make sure it has saved the settings. Then if it switches back to slushpool and the other account, check again and see if the file has changed. You can also see the log for the miner in that directory called miner.events First thing you need to change is the default root password. Please remember that the root password is public, so if someone gains access to your network and scans it and finds "futurebit-btc" its pretty easy for them to do a google search and figure out how to log in and take over your unit. This applies to almost any miner / open source firmware or devices on your network. You can change the default password in the OS settings using a monitor: Power Button on Upper right hand corner -> Settings -> Users -> Change password OR SSH into your device (futurebit/futurebit123) and type password update command Ideally you should do this right after a fresh SD card install before you connect the device to your network with a monitor keyboard and mouse, that way if you have another compromised system on your network it does not have a chance to auto log in and hijack your Apollo. This is just temporary though and you need to find the root cause of how they are accessing your network in the first place, which is probably another compromised system/device on your network. Everyone should be doing this regardless, and in a future update we will be implementing more security measures like setting the dashboard password you initially set up to the root password as well. |
|
|
|
I'm not experiencing any issues with usernames being changed. I've also never seen the dashboard (don't even know how to access it to be honest). It seems like the issue could very well be with someone getting on your networks and not a backdoor, but what do I know... I did discover a couple lines of code will keep them running in the case of a crash of the software and that has kept mine functioning without any need for manual intervention. I pasted the code below if anyone cares. It's nothing groundbreaking you couldn't find in 2 seconds with a Google search, but does the job for my .bat files. @echo off
:Start:
pushd "%~dp0"
.\apollo-miner.exe -host YOURPOOLHERE -port YOURPORTHERE -user USERNAMEHERE -pswd ANYTHING -comport YOURCOMHERE -brd_ocp YOURSETTINGHERE -osc YOURSETTINGHERE -ao_mode 1
:: Wait 10 seconds before restarting.
TIMEOUT /T 10
GOTO:Start Looks like your running a standard unit, so there is no dashboard for that since you run the miner software directly on your system |
|
|
|
I'm absolutely clueless on why my miner will mine flawlessly for days, then I'll have days where it disconnects 100+ times, what's going on?
Also, every single time it disconnects it changes my pool to - stratum+tcp://stratum+tcp://us-east.stratum.slushpool.com:3333 and the username to Topminer.01 with a password of X
It almost seems like my miner is compromised because it makes no sense on why it reverts to some random slushpool account, I've tried to mine on over 10 different pools and it'll mine great for 1-3 days then I'll experience the same exact thing where it just stops mining, changes the pool back to slushpool and restarts itself.. It DOES connect to this slushpool and it hashes.. but I can't login to the slushpool website and find that Topminer.01 at all, it seems like someone is stealing my hashes.
Sounds like your network or another device on your network is compromised. I would try reflashing your SD card to stock, if you still see it happening then someone is gaining access to your Apollo through another device on your network. You can also change the default account/ssh password on your Apollo as well using the UI settings (we will have the dashboard password apply as the system password automaticly for additional security in the next update). |
|
|
|
Is it normal to be in the RED for memory at around 3GB while mining in Balanced mode and BTC node running ??
Yes especially if the node is still syncing. This will nearly max out mem/cpu until its complete, nothing to worry about though as it also uses fast system swap memory on the SSD as well. FYI Bitcoin Mag put out a cool article/getting started on the Apollo (setup instructions are even better than mine haha). Check it out! https://bitcoinmagazine.com/guides/how-to-use-futurebit-apollo-bitcoin-node-miner |
|
|
|
Can anyone add any insight here. I opened port 8333 on my linksys velop router and my apollo is connected to a switch. Right now it's still showing 10/32 connections. Will this increase after sync?
I''m also viewing doing everything via the web dashboard from my Mac.
I would like to know as well. I am already sync and only have 17 to 18 connections. what were you at before full sync? I saw mine hit 11 then back to 11. I even ran this command in Terminal nc -zv (IP)8333 and it says PORT 8333 succeeded I was at 10 connections the whole time I was syncing. I checked this morning and I seen that I am fluctuating from 19-20. I wonder how we can get all 32. Awesome! I'll give it some time to finish syncing. I have a feeling if Im hovering at 10 it'll be find once it's done. The port is open specific for the device according to my linksys velop system. I hope I don't have to do anything with the modem. When I originally set up the mesh system, I had to disable the built in wifi that was on the modem. Do you think there is anything else I need to do in there? As of now, with an uptime of 1 hrs, I have 22 connections. Hopefully it grows. I also got myself a external USB fan to put under my Apollo. I am keeping the Temps at 46-56 Celsius on Turbo mode. Yea your node will only show inbound connections while its syncing, once it has complete then it can participate in the rest of the network and connect to other outbound nodes. Your node will build up connections up to the maximum over time as it discovers more peers on the network, but that can take some time. |
|
|
|
That is actually very helpful thank you. I download the package - use native package installer. On Status it says "error: wrong architecture 'i386' -- Run dpkg --add-architecture to add it and update afterwards"
I get various "add architecture issues no matter what build type I try to download. I have searched online for help videos and articles with minimal success. Furthest I have gotten in command prompt to try to add these is my access is denied. Is there some way to run script as an admin and add the architecture? Hopefully this makes sense....
THank you!
You can also expose the UI directly to the open internet, it is a mini web server after all. If you port forward both port 80 and 5000 to the Apollo in your router settings you will be able to access the dashboard from anywhere using your public IP address. Obviously I dont recommend this and you should have a secure password as anyone can bring up your dashboard if they come across your public IP address, but its an easy way to access the dashboard remotely without messing with third party viewer apps. |
|
|
|
damn, did i break mine already? the SSD isn't loose. I powered them off to add a 3rd unit but I haven't been checking the node tab so have no idea when it stopped working.
"Node is offline - Double-check your NVMe SSD is seated correctly on the M.2 slot on the bottom of your device and restart your Apollo. If the node is still not loading, you can try re-formatting your node drive in the settings section of the dashboard"
Do you see the red LED next the SSD after it has booted? Also bring up a terminal and type "lsblk" this will show whether the nvme is even recognized. |
|
|
|
Since electricity is very expensive here, I only want to mine when the sun is shining and my solar panels produce more than I need - I am planning to automate this = the FutureBit will sometimes loose power and then the next day it will get power again to run for say 8-10 hours during the middle of the day. Question: Will the FutureBit jump back into action again in this scenario without me having to manually get it to mine again? Or will it mess up things? Reading from previous posts it sound as if these hard shutdowns will mess things up - so I guess my next question is if the dashboard allows for schedule planner so that the dashboard can be set to stop and start the mining in the correct way at certain custom selected times?..keeping the beast alive but in sort of "sleep mode". Thanks for your replies in advance If you dont shut it down manually before you cut power then yea you'll corrupt the SD card eventually. There is no way to automate this in the UI, but you can do it on the backend if you know how to use scripts and systemctl. Commands to start/shutdown the miner on the backend are simply: systemctl stop apollo-miner systemctl start apollo-miner |
|
|
|
Just reach out via email if your having any issues. If you got two extra standard units just shutdown your full node, plug in the new units to their power supplies and the USB cable to the back of the main unit, fire up the full node and it should auto recognize them and start mining. Keep in mind you might need an extra USB hub if you have more than 2. |
|
|
|
Okay so what is the cable that connects 2 miners in this case. Both ends need to be what________________?  [/quote] Its a USB to Micro USB cable, but you should have received one if you ordered a standard unit. |
|
|
|
|
Show Posts
