Canonical page: https://koalavps.com/support/

Language: English. Source snapshot: 2026-10-21. Generated: 2026-10-21T13:31:28.274Z.

[Home](https://koalavps.com/) / [Explore](https://koalavps.com/resources/) /  A human path through the problem

A human path through the problem

# Helpful support starts with clear information.

Find useful information for account, billing and infrastructure questions. Prepare a concise description of the issue and use a verified service contact; response commitments depend on the support scope for your order.

[Find your VPS](https://koalavps.com/vps/)

## IN THIS DOCUMENT

[Send the details that help](https://koalavps.com/support/#section-1)[Account access is sensitive](https://koalavps.com/support/#section-2)[Know the service boundary](https://koalavps.com/support/#section-3)[Incident or security report?](https://koalavps.com/support/#section-4)[Send a report another operator can act on](https://koalavps.com/support/#section-5)[What a good incident update should contain](https://koalavps.com/support/#section-6)[Questions & answers](https://koalavps.com/support/#page-faq)[Knowledge base](https://koalavps.com/resources/)

## Send the details that help

Include the server identifier, region, the time and timezone of the issue, expected behaviour and what you observed. A short reproduction is more useful than a large unfiltered log. Redact passwords, tokens and unrelated personal information.

## Account access is sensitive

Support requests need a secure way to verify account control. Staff should never request your password, private SSH key, wallet seed phrase or full recovery-code set. Use only contact channels published on a verified domain.

## Know the service boundary

Infrastructure support covers the machine and agreed network service. Application debugging, migrations and ongoing administration require an explicit managed-service scope. Confirm what is included before relying on support for a production workload.

## Incident or security report?

A widespread service issue belongs in the incident process. A vulnerability needs a private verified security channel and careful disclosure. An individual application error needs its own reproduction and diagnostic context.

## Send a report another operator can act on

Include the affected service identifier, region, time with timezone, observed error, recent change and a short reproduction. Distinguish an account problem, payment reconciliation, network reachability and an application failure. Remove passwords, tokens, seeds and customer data from attachments before submitting them.

## What a good incident update should contain

An incident update should explain the affected scope, known impact, current mitigation and next update point. If the cause or recovery time is unknown, say so. Response and restoration targets come from the support agreement. Keep updates consistent with verified operational facts.

## A little more clarity.

Should I send a wallet seed or root password to diagnose an order?

No. Use order and transaction identifiers for payment questions, and a scoped diagnostic or approved secure process for server support. Never send a wallet recovery phrase or private key.

KEEP EXPLORING

## Continue reading.

[Guides ### From a clean image to a useful server. A sensible initial setup makes future maintenance less stressful. Keep a record of the decisions and test each access change befor…](https://koalavps.com/first-server/)[Guides ### A careful payment takes a minute. Crypto transfers deserve a deliberate check because the network does not provide a conventional undo button.…](https://koalavps.com/payment-safety/)[Trust ### Secure messages start with a verified key. Verify the official public key and its full fingerprint before sending confidential information. An official KoalaVPS key is not c…](https://koalavps.com/pgp/)

CONFIGURE YOUR INFRASTRUCTURE

## Take control. Deploy on your terms.

No identity paperwork. Full administrator access. Crypto-native billing.

[Select a configuration](https://koalavps.com/vps/)