System logs page shows 401 errors when switching between node tabs after upgrade

[FASupportBot]

After upgrading to FusionAuth 1.69.x, the System Logs page (System → Logs) exhibits unreliable behavior when switching between node tabs in a multi-node deployment.

Symptoms:

• On initial page load, logs from other nodes often don't appear until navigating away and returning to the route
• The "current" node indicator behaves inconsistently
• Browser console shows 401 (Unauthorized) errors when attempting to fetch logs from other nodes

Example error from browser console:

GET https://your-instance.fusionauth.io/ajax/system/log/?nodeId=d8f010c2-aec8-49d2-8b96-bfc9f7e90fa3 401 (Unauthorized)
loadNodeContent @ /js/admin/SystemLogs.js?version=1.69.3:15

This occurs in a FusionAuth Cloud deployment and appears consistently after the upgrade. The issue happens even after a fresh login.

[FASupportBot]

This is a known bug in FusionAuth 1.69.x that affects the System Logs page when viewing logs from multiple nodes in a cluster.

The issue has been confirmed and logged with the FusionAuth development team. The 401 errors occur when the UI attempts to fetch log content from other nodes in the cluster, causing the tab-switching functionality to fail intermittently.

Unfortunately, there is no workaround available at this time. The bug will be addressed in a future release.

As a temporary measure, you may need to:

• Refresh the page multiple times when checking logs across nodes
• Navigate away from and back to the System Logs page to trigger a reload
• Access logs directly from individual nodes if you have that capability in your deployment

Once this issue is resolved in a future version, the System Logs page should reliably display logs from all nodes without authentication errors.