Search the Community

Showing results for tags 'configuration'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Company news
    • General announcements
  • ftrack Studio (main app)
    • General discussion
    • Feature requests
    • API
    • Help
    • Actions and Widgets
    • ftrack Go
  • ftrack Review
    • General discussion
    • Feature requests
    • Help
  • Connect and plugins
    • General discussion
    • Connect package releases
    • Feature requests
    • Help
    • Connect plugins releases
  • Advisory Forum
  • Tech preview
    • API
    • New integrations
    • Studio overview
    • ftrack Review

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. I was following the instructions for configuring Sentry for error monitoring, but when I restarted the server I kept getting "ValueError: Invalid Sentry DSN" in my logs and the server refused to start. It turns out that in the Client Keys section of my Sentry project, I need to hit the "Show deprecated DSN" link in order to show the DSN that includes the secret. Apparently newer Sentry clients no longer require having the secret in the URL, which is why Sentry lists it as deprecated. It would be useful to specify in the instructions that the deprecated DSN is required in order to avoid confusion.