-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Hails edited this page Jun 28, 2026
·
1 revision
| Log message | Cause | Fix |
|---|---|---|
Discord responded 400: ... Must be 30 or fewer in length |
More than 30 data fields in the payload | Set ENABLED_FIELDS to ≤ 30 field names (see Field Catalog) |
Rate limited by Discord; backing off Ns / 429
|
Polling faster than Discord allows | Normal in bursts; if constant, raise POLL_INTERVAL_MS to 15000 or 20000
|
Discord responded 401/403
|
Bad or expired BOT_TOKEN, or wrong APPLICATION_ID/USER_ID
|
Re-check the three Discord values in .env
|
station/schedule/requests endpoint unavailable (HTTP 404)
|
Wrong STATION_SHORTCODE or that endpoint isn't public on your instance |
Verify the shortcode; 403/404 on those is non-fatal and only blanks their fields |
Error: <number> on startup |
AzuraCast base URL/shortcode unreachable | Check AZURACAST_BASE_URL and that /api/nowplaying/<shortcode> loads in a browser |
| Widget not updating but no errors | Field names in the layout don't match, or the field isn't in ENABLED_FIELDS
|
Names must match exactly; run DRY_RUN=1 node sync.js to see what's actually being sent |
When in doubt, run DRY_RUN=1 node sync.js. It prints every field that would be sent with live values and needs no Discord credentials.
For the settings these errors relate to, see Configuration.
Main repository: https://github.com/Hailey-Ross/hails.widgetcast