sudo fsck -y /dev/sda1 && sudo reboot
I see a lot of users having issues connecting to umbrel.local and most of them are Windows users. People… please before getting into running a node, DYOR and learn at least basics about networking, TCP/IP, IPs, LAN, WAN.
Running a node is something serious, is not a toy!
Also Umbrel team, is NOT responsible for your own mistakes and lack of knowledge about how to fix simple things and not related with Umbrel software.
I will try to put here some simple steps so everybody can try them before start freaking out that their Umbrel node is “broken”.
Not having access to your node doesn’t really means your node is broken. Means that the PC from where you access it can’t see it in your LAN or in the parameters you configure your LAN.
So could be 4 reasons that maybe your node is not accessible:
- IP assigned. The IP for the node is not set fix, or was changed by your DHCP router, or is not in the same range of your regular LAN.
- Your computer from where you are accessing, doesn’t know the new IP or couldn’t find the IP related to umbrel.local. Some Windows versions update that information and sometimes simply block it.
- Hardware issues. If your HDD/SSD with data has connection failures, the Umbrel OS will enter into a loop`and cannot be accessible.
- Software issues. Very rare when UmbrelOS is stuck. So in 99% of cases a restart and a good amount of time waiting to come back (re-sync the blocks) will fix it. So be patient and after restart just wait before doing any further investigation.
- How to set a fix IP for my node?
Option A - setup in your router a fix IP for your node
- enter in your router configuration
- find DNS or DHCP server (depending on each brand)
- set a fix IP, from your LAN range and one that is not used by other device. You can run from any Windows machine in command prompt arp -a and will see a list of all computers connected in your LAN, with their assigned IPs and MAC address. One of those could be also your node if is ON. Also you can see the MAC address on the box of your Pi.
- So assign a fix IP using your RPi MAC address in your router done, from now on, each time your RPi will be connected to that router, it will be assigned the IP you configure it.
Option B - setup a fix IP in your RPi settings
- use Windows Powershell or Putty to enter SSH into your Rpi type ssh [email protected] or ssh umbrel@yourRpi-IP` if you know that dynamically assigned IP (see previous point listing IPs in your LAN)
- will ask you for a password, BUT YOU WILL NOT SEE IT. Just type your user password for Umbrel and press ENTER.
- once you are in, configure the static IP address for the Pi, the gateway path and a DNS server. The configuration for the DHCP client (Pi) is located in the /etc/dhcpcd.conf file:
sudo nano /etc/dhcpcd.conf
The following snippet is an example of a sample configuration. Change the value of static routers and static domain_name_servers to the IP of your router (default gateway, see Option A).
Be aware of giving the Raspberry Pi an address which is OUTSIDE the range of addresses which are assigned by the DHCP server. You can get this range by looking under the router configurations page and checking for the range of the DHCP addresses. This means, that if the DHCP range goes from 192.168.178.1 to 192.168.178.99 you’re good to go with the IP 192.168.178.100 for your Raspberry Pi.
Add the following to the /etc/dhcpcd.conf file:
#Configuration static IP address (CHANGE THE VALUES TO FIT FOR YOUR NETWORK)
interface eth0
static ip_address=192.168.178.100/24
static routers=192.168.178.1
static domain_name_servers=192.168.178.1
Restart networking system sudo /etc/init.d/networking restart
- Add node IP into your hosts file
Now, once you know that your Pi will have a fix IP, you can go and add it also to your local computer, for easy accessing.
Go to the hosts file located into: C\Windows\system32\drivers\etc\ If you can’t see it, go to view folder options and select “show hidden files and folders”.
copy it onto your desktop and start editing with notepad
add the following line:
192.168.x.x umbrel.local
(replace 192.168.x.x with your local IP assigned for your node)
save the file and copy it back over the original. It will ask you to confirm, because it’s a system file. Confirm and done.
restart your PC. From now on your PC will always go to the assigned IP when you type in your browser umbrel.local
For Mac users, follow these steps to edit your hosts file 40. For Linux users, these instructions are not valid, they already know what to do, if they already run a Linux :slight_smile:
-
Hardware issues.
Usually, most of the times, the external hard drive get disconnected (for various reasons) sometimes, the power source it fails, even if are milivolts that you do not detect them, those little intrerruptions could damage some hardware or do not run properly. power cuts are very serious damaging drives or files on the drives. It is very recommended to run your node with a backup battery that can keep ON your node several minutes until you can shut it down! DO NOT RUN YOUR NODE WITHOUT BATTERY IF YOU ARE IN A MIDDLE OF A THUNDERSTORM. YOU WILL GET REKT 99% OF THE TIMES!
In order to troubleshoot what is happening inside your node machine, Umbrel team will need to see the debug log. That log contain valuable information that can “tell” if there’s a component that fails. Also you can read it and see if something is wrong and maybe a quick view will give you a clue and fix it yourself. If you are not so comforbale with logs, just send to the Umbrel community the link of the log and we can take a look.
Enter SSH into your node. Open a terminal/command prompt/powershell/putty on your computer and enter
the password is your personal user password for Umbrel dashboard. When you type it, you won’t see what you type, so just type and press ENTER. If you do not change it, it is the Umbrel default password - moneyprintergobrrr
and then type
~/umbrel/scripts/debug --upload
At the end of the debug log it will be a link and instructions where to post it (on Telegram group or on Umbrel Community).
-
Software issues Most of the times these issues come from:
users do not have patience to wait until the node is fully synced and restarted or power off or do whatever any other tasks that should not do. Patience is the key for a node operator! power cuts or previous installations that didn’t end well mSD card get damaged. These cards are very sensitive. Always keep a copy at hand updates that hangs due to disk sectors that are not in a well state many other reasons that system can get unstable (it’s a simple Pi not a full server machine so expect these issues)
What to do?
run the debug log indicated at the point 3.
you can reflash the mSD card. On this card is ONLY the OS, not the data. So no user data will be lost
re-apply latest update. Yes sometimes, files can get corrupted and a reinstall could just write the correct version.
DONE! From now on you can access you node in your browser with umbrel.local !
Optional I would recommend to open your Umbrel dashboard using the onion address provided (after you enter with umbrel.local) and bookmark that address.
Also to REMEMBER:
each Umbrel app will have a different onion address so save them individually.
NEVER share these onion addresses in the wild internet with strangers!
If you create a LNbits app wallet, be aware to save that wallet address in your bookmarks. It is the only way to get back to it.
Thunderhub app and Lightning Terminal do not update your Umbrel dashboard, are hardcoded with the default password. so use these apps ONLY from your LAN or if you access from outside using onion address, do not use it on strange computers, only yours.
I really hope that this guide will help so many “lost souls” that get freaked out because of a simple access in LAN.
https://community.getumbrel.com/t/guide-umbrel-local-not-accessible-what-to-do/845/3