Contact support
This form reaches the Outpost support team. Before you use it, check known issues: if what you are hitting is on that list, the page has the workaround and the status of the fix.
Chat instead
Section titled “Chat instead”If it is broken now and you need somebody looking at it with you, chat is faster than this form.
Send a message
Section titled “Send a message”What to include
Section titled “What to include”A message with these four things in it gets an answer. A message without them gets a question back, which costs both of us a day.
| Include | Why |
|---|---|
| The component and version | Depot 0.3.0 and Depot 0.2.5 fail differently. |
| What you expected | It is often not what the product is meant to do. |
| What happened instead | Including the exact message, copied rather than described. |
| What changed recently | An upgrade, a policy change, a new firewall rule. |
Leave out anything secret. Do not paste a password, an API token, a licence file or a private key into this form. If a credential is part of the problem, say so and we will find another way to look at it.
What happens next
Section titled “What happens next”- If we recognise your email address, the message becomes a ticket against your organisation and goes to the queue that handles your account.
- If we do not, it becomes an inquiry and somebody reads it anyway. Use the address your Outpost account is under if you have one, and it will route correctly.
- We reply by email to the address you give here.
Not this form
Section titled “Not this form”- A security problem. See reporting a vulnerability.
- A page on this site that is wrong. Use the feedback control at the bottom of the page, or contribute a fix.
- Your own users asking for help. They use Tray on their own machine, and their request reaches you, not us.
Content is licensed CC BY 4.0. Code samples are MIT. Outpost and the Outpost mark are trademarks of Outpost Business Solutions, PBC and are not covered by either licence.