AUTH441: Auth token too large
What this means
The login token is larger than this server accepts.
The server rejected the login token for size: a 400 when it travels in the Authorization header, or a 414 when it travels in the URL. No client-side encoding can shrink it — the server's header/URL size limits must be raised, or the token made smaller.
What to do
Export diagnostics and contact support. Retry after making the change above; retrying without it will fail the same way.
Your data
No order or product data is affected.
Troubleshoot
- On Apache, raise LimitRequestFieldSize (header path) or LimitRequestLine (URL path) in the vhost config.
- On nginx, raise large_client_header_buffers.
- Behind a proxy or CDN, the limit may be at that layer — check both.
- If limits cannot change, contact support about issuing a smaller token for this site.
Where to look
When WCPOS can save this error, it is recorded on the device that raised it. Open Store health → Logs (the heart-pulse icon at the bottom of the navigation drawer), find the entry marked with this code and expand it: the expanded row shows the plain-language reason and the context captured at the moment of failure. For a store request, that context may include the server’s own error code (serverCode), the HTTP status or the endpoint; the fields shown depend on where the failure occurred. When reporting a problem, use Copy debug info at the top of the Logs screen (Share debug info on phones and tablets) rather than screenshots: it bundles the app version, connection state and the most recent errors. Logs are kept for at most 30 days, so collect them while the problem is fresh. Also copy any browser-console error that appeared before the POS was able to write its own log entry.
Details
- Code:
AUTH441(AUTH_TOKEN_TOO_LARGE) - Severity: error
- Introduced in: WCPOS 1.10.0