# Accessing Node After Power Outage

**URL:** <https://community.umbrel.com/t/accessing-node-after-power-outage/2785>\
**Category:** Support and Troubleshooting\
**Created:** [August 19, 2021, 4:51pm UTC](https://community.umbrel.com/t/accessing-node-after-power-outage/2785 "2021-08-19T16:51:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ghost4hire](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/ghost4hire/32/1015_2.png) [@ghost4hire](https://community.umbrel.com/u/ghost4hire)\
**Post date:** [August 19, 2021, 4:51pm UTC](https://community.umbrel.com/t/accessing-node-after-power-outage/2785/1 "2021-08-19T16:51:13Z")

</div>

I ran into this issue after a storm knocked out our power and this is how I resolved it.  
I thought this would be helpful in case someone else has this particular issue since it wasn’t already documented.

**What I experienced:**

- The Umbrel UI shows up via browser but there is no option to log in or log out.
- The Shutdown, Restart, and Troubleshoot buttons throw a connection error.
- I am able to SSH into the Raspberry Pi 4.

**How I resolved it:**  
SSH into Raspberry Pi 4 and reboot using the following command

```
ssh -t umbrel@umbrel.local    
sudo reboot

```

Good luck!

---

<div class="post-metadata">

**Author:** ![cam.btc](https://avatars.discourse-cdn.com/v4/letter/c/ce73a5/32.png) [@cam.btc](https://community.umbrel.com/u/cam.btc)\
**Post date:** [August 20, 2021, 12:35am UTC](https://community.umbrel.com/t/accessing-node-after-power-outage/2785/2 "2021-08-20T00:35:05Z")

</div>

Thanks! I was finally able to ssh into my umbrel using that command and did the reboot.

However… I have another problem now. When I go to umbrel.local I get a page that says the umbrel refuses to connect … and if I go to the IP address that I assigned to it in my router I get the umbrel start page that never loads. I figured it was offline, but now that I was able to ssh into the umbrel I’m able to ping out 🤔

 ![Screen Shot 2021-08-19 at 8.34.44 PM](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/2X/1/1acebbb4f62afd2dd58d6296652936b1bae7d84b.png)

---

<div class="post-metadata">

**Author:** ![ghost4hire](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/ghost4hire/32/1015_2.png) [@ghost4hire](https://community.umbrel.com/u/ghost4hire)\
**Post date:** [August 20, 2021, 2:57am UTC](https://community.umbrel.com/t/accessing-node-after-power-outage/2785/3 "2021-08-20T02:57:17Z")

</div>

That could be a browser caching issue.

Try clearing out your cookies and open an incognito window.

---

<div class="post-metadata">

**Author:** ![ghost4hire](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/ghost4hire/32/1015_2.png) [@ghost4hire](https://community.umbrel.com/u/ghost4hire)\
**Post date:** [August 20, 2021, 3:21am UTC](https://community.umbrel.com/t/accessing-node-after-power-outage/2785/4 "2021-08-20T03:21:26Z")

</div>

If clearing the browser cache doesn’t work you might want to stop then restart the startup service

`sudo systemctl stop umbrel-startup.service && docker system prune --force --all && sudo systemctl start umbrel-startup.service`