Problems with Organization Secrets

#1

Use this guide to troubleshoot issues with Organization secrets.

404 Error

client error 404: 404 page not found.

If you receive a 404 error when trying to create or manage secrets, it may indicate you are running an outdated version of the Drone server. Please ensure you are running Drone 1.1.0 or higher.

403 Error

client error 403 {“message”:“Forbidden”}

If you receive a 403 error when trying to create or manage secrets, it may indicate you are not a Drone system administrator. Only a Drone system administrator can manage organization secrets.

Case Mismatch

When you configuration organization secrets, the organization name is case-sensitive. For example, secrets for organization Foobar will not match foobar. The organization name you use when creating secrets must match the exact casing in your source control management system (e.g. GitHub).

For example, if your organization is Foobar (capital F)

# this is bad (wrong case)
drone orgsecret add foobar username spaceghost

# this is good (correct case)
drone orgsecret add Foobar username spaceghost

Pull Requests

When you configure organization secrets, they are disabled for pull requests by default for security reasons. If you want to expose organizations secrets to pull requests, they must be created with the --allow-pull-request flag.

Still Experiencing Issues?

If you have tried all of the above and are sill experiencing issues, please create a discourse thread that includes all of the requested information:

  1. Full result of drone repo info <repository> (Do not redact the repository name)
  2. Full result of drone build info <repository> <build>
  3. Full yaml configuration file
closed #2