mirror of
https://github.com/AmruthPillai/Reactive-Resume.git
synced 2026-10-05 03:03:58 +10:00
66 lines
3.0 KiB
Plaintext
66 lines
3.0 KiB
Plaintext
---
|
|
title: "Checking service status"
|
|
description: "Find out whether rxresu.me is up, see its recent uptime, and learn what to do when Reactive Resume is slow or unreachable."
|
|
---
|
|
|
|
If rxresu.me won't load, is slow, or something that normally works keeps failing, check the status page first. It tells
|
|
you whether the problem is on our side or yours.
|
|
|
|
## Check the status page
|
|
|
|
Open [status.rxresu.me](https://status.rxresu.me). The page shows:
|
|
|
|
- Whether the service is **Online** right now, and for how long.
|
|
- Uptime for the last 24 hours, the last 7 days and each recent month.
|
|
- When it last checked. The service is checked every minute from several locations around the world.
|
|
|
|
<Card title="Reactive Resume status" icon="signal" href="https://status.rxresu.me">
|
|
Live and recent uptime for rxresu.me.
|
|
</Card>
|
|
|
|
## If the service is down or slow
|
|
|
|
<Steps>
|
|
<Step title="Confirm it on the status page">
|
|
If the status page shows a problem, it's on our side. You don't need to do anything else.
|
|
</Step>
|
|
<Step title="Wait and try again">
|
|
Most outages and slowdowns are short. Try again in a few minutes. Your documents are safe on the server while it's
|
|
unavailable.
|
|
</Step>
|
|
<Step title="Look for announcements">
|
|
Longer outages and planned maintenance are announced on [GitHub](https://github.com/reactive-resume/reactive-resume)
|
|
and the [Discord server](https://discord.gg/aSyA5ZSxpb).
|
|
</Step>
|
|
</Steps>
|
|
|
|
## If the status page says everything is fine
|
|
|
|
The problem is probably between your device and the service. Try these in order:
|
|
|
|
1. Reload the page.
|
|
2. Check your internet connection by opening another website.
|
|
3. Open rxresu.me in a private window. If it works there, a browser extension, such as an ad or script blocker, may be
|
|
getting in the way.
|
|
4. Try a different browser or device.
|
|
|
|
If you lose your connection while editing, the editor says so under the document name and keeps your changes on this
|
|
device. They're sent as soon as you're back online. Downloading and sharing are unavailable until then.
|
|
|
|
Still stuck? Ask in [GitHub Discussions](https://github.com/reactive-resume/reactive-resume/discussions/categories/q-a).
|
|
If you can reproduce a bug, [open an issue](https://github.com/reactive-resume/reactive-resume/issues).
|
|
|
|
## If you run your own copy
|
|
|
|
The status page only covers rxresu.me. A self-hosted copy reports its own health at `/api/health` on your address, for
|
|
example `https://resume.example.com/api/health`. It returns `healthy` when the database, file storage and (if you use it)
|
|
Redis are working, and an HTTP `503` error when any of them fails. See [Self-hosting with Docker](/self-hosting/docker) for setup and
|
|
health checks.
|
|
|
|
## Help keep the service running
|
|
|
|
Reactive Resume is free and has no ads or investors. Server costs are paid by donations, so busy periods can still slow
|
|
it down. If Reactive Resume helps you, consider
|
|
[donating on Open Collective](https://opencollective.com/reactive-resume/donate). If you need guaranteed availability,
|
|
you can [host your own copy](/self-hosting/docker).
|