Resources01 · Docs

DOCS / TROUBLESHOOTING

Website and account troubleshooting

Start from the user action, find the first failure boundary, then decide whether the issue belongs to the browser, website, client module, or remote service.

Published 2026-08-08About 8 minutesACTIONABLE CHECKLIST

Blank page, missing styles, or content appearing too slowly

  1. Confirm that the final address is https://kyormar.com/ and is not stuck on a temporary hostname or redirect loop.
  2. Reload the page, confirm that HTML revalidated, and verify that hashed CSS and JavaScript return 200.
  3. If only the animation is missing, check whether the system has Reduce Motion enabled.
  4. Record the exact route, browser version, and incident time instead of saying only that “the page is broken.”

Verification code, signup, or login failure

Preserve the error code or message shown on the page. Expired codes, existing accounts, incorrect passwords, and unavailable services are different boundaries and cannot be bypassed by repeatedly signing up.

  • Confirm the email format and request the verification code only once.
  • Confirm that a browser extension has not modified the login page.
  • Session credentials remain only in the current browser session; closing it may require another login.
  • Do not send verification codes, passwords, or access tokens to support.

Quote, QR code, or entitlement did not synchronize

The site requests a formal quote from the payment service before creating an order. After payment, it still verifies the order number, currency, amount, SKU, quantity, and price version. Any mismatch prevents frontend activation of entitlements.

  • Reconfirm after a price change; do not use an expired quote.
  • Do not create duplicate orders. Check pending payment status on the Orders page first.
  • If payment was made but the entitlement is missing, keep the order number and contact payment support instead of paying again.

Submit minimal but sufficient evidence

INCLUDEIncident time, page address, steps taken, and a public error code.
EXCLUDEPasswords, verification codes, tokens, full bank-card numbers, private keys, and task content.

For payment or account issues, use the support entry point; for product-boundary questions, first read the architecture guide.