TABLE OF CONTENTS

Error 500 or Hang Tight, We Hit a Small Snag
Error 403 or Whoops, Something Went Wrong
Error 404 on the Display
Error 429: Too Many Requests (Screen Disabled)
CSRF Error When Logging In or Saving
CAPTCHA Check Fails
Import Signature Authentication Failure
Wrong Screen or the DAKboard Home Page Is Showing
Helpful Articles

Use this guide if your Screen, the DAKboard website, or your Display shows an error message or a page that will not load. Find the message you see below. Each section explains why it happens and how to fix it.

If your Screen loads but content is missing or not updating, see Screen Troubleshooting: Content Not Updating or Missing. If a DAKOS device shows code or an error message while starting up, see DAKOS Troubleshooting: Startup and Error Messages. For a list of every issue we cover, start at DAKboard Troubleshooting: Start Here.

Error 500 or Hang Tight, We Hit a Small Snag:

Why this happens: An Error 500 (or 503) means something went wrong on our side, not with your Display or your settings. You will see a page that says "Hang tight! We hit a small snag." The page reloads itself automatically every 10 minutes, so it recovers on its own once the problem is fixed.

How to fix it:

Check our Status Page for an open outage. If there is one, our team is already working on it and you do not need to contact us; the error page will reload on its own.
If there is no outage, find the Reference code. On the error page, click Show technical details if the details are hidden. You will see "An internal error occurred. (Ref: …)", followed by a 12-character code.
Go to any page in your DAKboard account (or this support site), click the Chat icon at the bottom right of the page, type Create Support Ticket, and include the Ref code, the date and time shown on the error page, and what you were doing (for example, saving a Screen or opening a Block editor).

Why the Ref code matters: each code is unique to that one error, so it lets our team find exactly what happened.

Error 403 or Whoops, Something Went Wrong:

Why this happens: You are trying to use a feature your plan does not include. This happens if a Display is set to show a Custom Screen on the Free Subscription, or a Loop or Screen Schedule on the Free or Essential plan.

How to fix it: A Custom Screen needs a Paid Subscription, and Loops and Screen Schedules need the Plus plan. Upgrade your Subscription, or assign a Screen your plan includes to the Display. See Predefined vs Custom Screens: Why Can't I…? for what each kind of Screen can do.

For details, see How to Assign a Screen to Your Display (Why am I Getting a 403 Error or Whoops, Something Went Wrong?).

Error 404 on the Display:

Why this happens: The Screen assigned to the Display was deleted from your account and is no longer available.

How to fix it: Assign a different Screen to the Display on your Displays & Devices page.

For details, see How to Assign a Screen to Your Display (Why am I Getting a 404 Error?).

Error 429: Too Many Requests (Screen Disabled):

Why this happens: Each plan allows a set number of devices per Screen (tablets, browsers, DAKboard Displays, and so on) showing it at the same time. Every time the Screen's URL is opened or refreshed, it counts as a new connected device. When the count goes over your plan's limit, the Screen is disabled and shows "Error 429: Too many requests."

How to fix it:

Check the usage. Open the Screen in the Custom Screen Editor and click the Metrics button. It shows the average number of connected devices over the past 24 hours and 7 days, and the limit for your plan.
Turn off auto-refresh. DAKboard refreshes your content on its own, so turn off any automatic refresh in the browser or app showing your Screen, or set it to the longest interval. The Fully Kiosk app has auto-refresh turned on by default.
Stop sharing the URL. Everyone who opens a shared Screen or Display URL counts as a connected device. If the URL was shared, export the Screen first (you cannot recover a deleted Screen), then delete it and import the file to get a new URL and reset the count.
Too many real devices? If you see "Max-connected devices reached!", remove some devices or upgrade your plan. The limits are on our Pricing Page under Compare Plans.
Ask us to turn the Screen back on. A disabled Screen has to be reviewed and reenabled by our team. Click the Chat icon at the bottom right of the page and type Create Support Ticket.

For details, see High Screen Usage or Disabled Screen (error 429).

CSRF Error When Logging In or Saving:

Why this happens: The CSRF token protects your account and is stored using cookies. The error appears if cookies are blocked on our site, if the token has expired (we expire them after a set time for security), or if your browser or one of its extensions holds on to an old token.

How to fix it:

Refresh the page (press F5 or SHIFT+R on Windows, Command+R on a Mac, or click the refresh button). This creates a new token and fixes almost every case.
If that does not work, clear your browser cache, or do a hard refresh with CTRL+SHIFT+R (Option+Command+R on a Mac). You may need to log out and back in.
If it still happens, make sure cookies are allowed and turn off browser extensions, pop-up blockers, or ad blockers. To test quickly, log in from an Incognito or Private window, which turns extensions off.

For details, see What to do When you get a CSRF Error.

CAPTCHA Check Fails:

Why this happens: Our sites use Google's reCAPTCHA to protect your account. It can fail because of your browser (out of date, JavaScript turned off, extensions or ad blockers, or a corrupted browser profile), your network, or a temporary problem with Google's reCAPTCHA servers.

How to fix it:

Make sure your browser is up to date and JavaScript is turned on.
Turn off browser extensions and ad blockers for a moment, then try again.
Clear your browser's cache and cookies, or try a different browser.
Restart your modem and router, or try a different network such as a mobile hotspot.
If none of these work, wait a while and try again. Temporary reCAPTCHA issues usually clear up on their own.

For details, see CAPTCHA with DAKboard.

Import Signature Authentication Failure:

Why this happens: When you export a Screen, we add a lock code to the file. If the file is changed in any way after export, the lock code no longer matches and the import is refused. This keeps unauthorized data out of our services.

How to fix it: The file is corrupted and cannot be imported. Export the Screen again and import the new file without opening or editing it.

For details, see How to Use the Custom Screen Live Editor (Why did I get the Message "Import signature authentication failure!"?).

Wrong Screen or the DAKboard Home Page Is Showing:

These are not error codes, but the Display is not showing the Screen you expect. Find what you see in the table below.

What you see	Why	How to fix it
A DAKOS Display still shows the old Screen after you assigned a new one	The Display is offline, has not refreshed yet, or runs a DAKOS version older than 3.55, which may not work properly with our services.	1. On Displays & Devices, check for the green dot and the last connect time under the Display's Settings. 2. Restart the Display by unplugging the power and plugging it back in. 3. Upgrade DAKOS if it is older than 3.55. See How to Assign a Screen to Your Display (Wrong Screen Showing on DAKOS Device). If the Display is offline, see DAKOS Troubleshooting: Offline and Network Issues.
The DAKboard home page instead of your Screen	On the Amazon Fire TV app, you were logged out of the app. On a DAKOS device, someone logged in to the account from the Display with a touchscreen, mouse, or keyboard.	On a DAKOS device, reboot the Display. On a Fire TV, log back in to the app. See How to Assign a Screen to Your Display (Why am I seeing the DAKboard Home Page?).
A Template you added shows as Unassigned	The Template has been added as a Screen but is not assigned to a Display yet.	Assign it to your Display. See How to Assign a Screen to Your Display.

Still stuck? Click the Chat icon at the bottom right of the page and type Create Support Ticket, or see Report a Bug, Request a Feature, or View DAKOS Release Notes to report the issue to our team.