# Edge tunneler become INVALID\_AUTH after machine reboot

**URL:** https://openziti.discourse.group/t/edge-tunneler-become-invalid-auth-after-machine-reboot/3173
**Category:** Support
**Created:** [September 26, 2024, 6:49am UTC](https://openziti.discourse.group/t/edge-tunneler-become-invalid-auth-after-machine-reboot/3173 "2024-09-26T06:49:55Z")
**Posts on this page:** 1
**Page:** 2

<div class="post-metadata">

### Author: ![qrkourier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/qrkourier/32/52_2.png) [@qrkourier](https://openziti.discourse.group/u/qrkourier)
#### Post date: [September 27, 2024, 2:30am UTC](https://openziti.discourse.group/t/edge-tunneler-become-invalid-auth-after-machine-reboot/3173/21 "2024-09-27T02:30:30Z")

</div>

I'm so relieved! I agree the tunneler must be reliable and I rely on it for my remote nodes.

Sometimes I will also install the zrok service as another channel. The best solution will depend on how many remote nodes you are managing. It is self hostable and there's a Helm chart. The [zrok.io](http://zrok.io) SaaS from NetFoundry can provide access for a few without cost and is expandable for a small cost.

[Previous page](https://openziti.discourse.group/t/edge-tunneler-become-invalid-auth-after-machine-reboot/3173.md?page=1)