Error Pages
500 with Incident Code
A 500 page in the "we are already on it" spirit: a hazard tape of CSS stripes, an incident code for support in a dashed frame, a refresh button and a link to the service status.
What you can change
- title and description — the heading and the explanation in your own words
- incident — the real incident code from your monitoring
- statusHref and statusLabel — the address and label of the status page
A link for your AI agent: preview, code and instructions.
Preview
Use it with AI
- 1. Copy the link.
- 2. Write to your agent in your own words and drop the link into the sentence.
- 3. The agent opens the link and installs the component from the registry.
put this on the home page as the hero:
https://vibeui.ru/c/errorpage-002?lang=en&theme=dark
Not sure where to paste it? Step-by-step guide
Show the full instructions
What the link says, spelled out. Use it when your agent cannot open links — paste this text instead.
Loading…
For developers
The install command lives in the “Component source” block below — a signed link that stays valid for 24 hours.
Technical notes
The block is self-contained: one file, no dependencies, its palette in local --vibeui-errorpage-002-* variables. A server component with no JS: the refresh button is a link with an empty href that points at the current address, and after a 500 a repeated request usually goes through. The hazard tape is drawn with repeating-linear-gradient — no images. The incident code is marked up as a dl and carries user-select:all: one tap selects it whole for pasting into a ticket.
Tags
- 500
- error
- incident
- status
- server
Component source
The same file your agent installs. Here in case you would rather copy it by hand.
Loading…