Pomerium-announce is a low traffic mailing list for important releases and security announcements.
Follow us on Twitter @pomerium_io or LinkedIn for the latest updates and industry news.
Check out our forum, Discuss, where the community explores Pomerium's uses and shares their best practices.
Want updates delivered directly to your inbox? Sign up for our newsletter here:
For general help and configuration questions, discussions about integrations or complex setups, or anything else related to Pomerium, head to our Discuss forum, where you can search for open threads or start a new one.
We prefer to communicate in Discuss so that answers can be indexes and easy to find for others. If a specific issue requires a faster back and forth to find a resolution, we may ask to move the discussion to our slack channel.
Like every software, Pomerium has its flaws. If you find one, search the issues to see if it has already been reported. If not, open a new issue and describe the bug, and somebody will look into it!
Please follow the issue template so we have all the needed information. We need to be able to repeat the bug using your instructions. Please simplify the issue as much as possible. The more detailed and specific you are, the faster we will be able to help you!
We suggest reading How to Report Bugs Effectively.
First, search to see if your feature has already been requested on GitHub or Discuss. If it has, you can add a 👍 reaction to vote for it. If your feature idea is new, open an issue to request the feature. You don't have to follow the bug template for feature requests. Please describe your idea thoroughly so that we know how to implement it! Really vague requests may not be helpful or actionable and without clarification will have to be closed.
While we really do value your requests and implement many of them, not all features are a good fit for Pomerium. If a feature is not in the best interest of the Pomerium project or its users in general, we may politely decline to implement it.