Report website down
🤯
Don't panic.
Your website hosted here is offline right now? Let's waste no time and get it solved together in a professional manner.
Please be advised to consider the points below for the best support experience and the quickest solution.
# Keep a cool head
This is an urgent situation. Please try to stay calm and focus on the facts. Emotions and allegations won't help fixing the issue.
# What error do you see?
There are many reasons why websites go down. Often the error you are seeing in the browser gives you a good hint. There are help pages to get you started investigating these specific errors:
- 403 troubleshooting guide
- 404 troubleshooting guide
- 500 troubleshooting guide
- 503 troubleshooting guide
- 504 troubleshooting guide
# It's likely something on your side
Most downtime we see is caused by "client coding mistakes" - usually by not making proper use of the available resources. In many cases we can help you to solve the issue. Many of such errors can be resolved by analyzing logs files and metrics. We are happy to discuss and research such problems together with our clients.
# It's maybe something on our side
See our status page status.fortrabbit.com if is already known. If not, don't hesitate to contact us. Provide enough details:
# What's the context?
Make sure to provide the exact app and environment names. Is the happening to just one app hosted here or to multiple or all?
# Have your developer on board
We advice to get your developer in contact with us. We often can't help worried business owners if they are missing the skills to have a technical conversation about the problem.
# Have you made recent changes?
Did you maybe recently pushed code? Or did some editor changed some setting on the App? Or was there any other change done, prior the downtime? Maybe someone uploaded a lot of images or performed other actions interacting with the website? Anything that can be of interest.
# Since when do you see the error?
Report the exact time when the issue started to happen.
# What else do we need to to know?
Is the error happening constantly, or is it more on/off? Have you got similar issues before?