# Master is not available. Backup is available, node is inactive

**URL:** <https://forum.inductiveautomation.com/t/master-is-not-available-backup-is-available-node-is-inactive/31321>\
**Category:** Ignition\
**Created:** [January 16, 2020, 12:04am UTC](https://forum.inductiveautomation.com/t/master-is-not-available-backup-is-available-node-is-inactive/31321 "2020-01-16T00:04:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dstorm](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@dstorm](https://forum.inductiveautomation.com/u/dstorm)\
**Post date:** [January 16, 2020, 12:04am UTC](https://forum.inductiveautomation.com/t/master-is-not-available-backup-is-available-node-is-inactive/31321/1 "2020-01-16T00:04:17Z")

</div>

I have an operator running client on their computer workstation while connected to the master. There is a master and backup for Ignition. They are having issues from time to time where the red overlay on components will appear for a while and then go away. Sometimes it happens long enough for a message box to appear stating  
" Master is not available [http://10.62.1.52:8088/main](http://10.62.1.52:8088/main)  
Read timed out  
Backup is available, node is unactive [http://10.62.1.72:8088/main](http://10.62.1.72:8088/main)"

The setting on the Read Timeout for a client is 10,000ms.  
The setting for Redudancy Setting Failover Timeout is also 10,000ms.

We are thinking the issue is that the work station that client is running on is losing connection with the master. This would explain why the backup is available but unactive, and explain the statement that the master is unavailable. I was just wondering if anyone has seen this error before and could confirm this theory? Any help will be appreciated!

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [January 16, 2020, 1:48pm UTC](https://forum.inductiveautomation.com/t/master-is-not-available-backup-is-available-node-is-inactive/31321/2 "2020-01-16T13:48:09Z")

</div>

I’ll confirm that for you. 🙂

---

<div class="post-metadata">

**Author:** ![Reyes](https://avatars.discourse-cdn.com/v4/letter/r/ccd318/32.png) [@Reyes](https://forum.inductiveautomation.com/u/Reyes)\
**Post date:** [December 19, 2022, 3:27pm UTC](https://forum.inductiveautomation.com/t/master-is-not-available-backup-is-available-node-is-inactive/31321/3 "2022-12-19T15:27:44Z")

</div>

Hey @dstorm Did you find the issue? I'm getting the same error on my clients.

Thank you

---

<div class="post-metadata">

**Author:** ![dstorm](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@dstorm](https://forum.inductiveautomation.com/u/dstorm)\
**Post date:** [January 30, 2023, 1:47pm UTC](https://forum.inductiveautomation.com/t/master-is-not-available-backup-is-available-node-is-inactive/31321/4 "2023-01-30T13:47:15Z")

</div>

The problem was the bottom paragraph. Can't remember our fix for it.

The work station that client is running on is losing connection with the master. This would explain why the backup is available but unactive, and explain the statement that the master is unavailable.