Q: How to fix the Omada widget 'API Error: Unexpected error' / 'Unexpected token <' in Homepage when multiple devices open the dashboard?

This is caused by concurrent Omada logins overwriting Homepage's shared cookie jar. Each viewer logs in every 5 seconds; an in-flight request can then send a token from one session with the session cookie from another, causing Omada to return an HTML login page instead of JSON. Immediate workaround: 1. Restart the Homepage container, not the Omada container: ```bash docker restart homepage ``` Or with Docker Compose: ```bash docker compose restart homepage ``` 2. Until the widget is fixed, avoid opening Homepage on multiple devices simultaneously. Multiple tabs on the same device do not trigger the issue as reliably. 3. Restarting Omada does not clear the bad state in Homepage. A permanent fix requires changing the Omada widget to reuse/cache a session instead of logging in on every 5-second poll, or isolating cookies/tokens per request rather than using a process-global cookie jar.

Question 1

Why does fiveColumns show only 4 columns for root services after upgrading Homepage to v1.0.0?

Accepted Answer

This is a regression in Homepage v1.0.0: `fiveColumns: true` is ignored for root-level layout groups, while nested groups can still display correctly. As a workaround, switch from the `latest` image tag to the `dev` tag, which contains the fix, then pull and recreate the container. Keep `fiveColumns: true` in `settings.yaml`. Alternatively, upgrade to a stable release containing the fix once available.

Question 2

How to fix the Omada widget 'API Error: Unexpected error' / 'Unexpected token <' in Homepage when multiple devices open the dashboard?

Accepted Answer

This is caused by concurrent Omada logins overwriting Homepage's shared cookie jar. Each viewer logs in every 5 seconds; an in-flight request can then send a token from one session with the session cookie from another, causing Omada to return an HTML login page instead of JSON.

Immediate workaround:
1. Restart the Homepage container, not the Omada container:
   ```bash
   docker restart homepage
   ```
   Or with Docker Compose:
   ```bash
   docker compose restart homepage
   ```
2. Until the widget is fixed, avoid opening Homepage on multiple devices simultaneously. Multiple tabs on the same device do not trigger the issue as reliably.
3. Restarting Omada does not clear the bad state in Homepage.

A permanent fix requires changing the Omada widget to reuse/cache a session instead of logging in on every 5-second poll, or isolating cookies/tokens per request rather than using a process-global cookie jar.

Homepage

Core Features

What It Can't Do

Use Cases

Detailed Introduction

Troubleshooting & FAQ (2)

Tags

Getting Started

Similar Projects