====== Fixing Indigo Server File and Folder Permissions ======

Sometimes the file/folder permissions (or owner) for Indigo Server can become incorrect. This can result in an error when starting the Indigo Server or it can cause reflectors to fail to create.

===== Why are the permissions wrong? =====

There are a few ways the permissions can become incorrect. If you used Apple's Migration Assistant tool to copy files from one Mac to another (or after an OS X upgrade) then that can result in incorrect file/folder owners. Or sometimes a poorly written installer sets incorrect file/folder permissions recursively on the entire **''/Library/Application Support/''** folder. This can result in problems not just with Indigo, but with all types of applications (yikes!).

===== How To Fix It =====

//**First, if you're using Indigo 6 or later, try rerunning the installer for your version ([[http://www.indigodomo.com/downloads.html|download]] installers from the downloads page).**// That will usually fix any permission issues (and will leave all your settings in place).

If that doesn't work, we've created a tiny application that tries to heal the common Indigo file/folder permissions (and owner) problems. To use it:

  - Shutdown the Indigo Server if it is running via the **''Indigo->Stop Server''** menu item
  - [[http://aws.indigodomo.com/download/IndigoPermFixer.dmg|Download the Perm Fixer app here]]
  - Double-click to mount the disk image
  - Right-click (or control+click) the file **''Indigo Perm Fixer.app''** and choose the **''Open''** menu item
  - It will prompt you for your OS X user account password (this is required because changing file/folder permissions requires OS X admin level access)
  - Select all the text in the output window and copy it to the clipboard
  - Launch Indigo (and the Indigo Server)
  - If you are troubleshooting an Indigo Reflector, then give it a couple of minutes to establish and test it

If Indigo still cannot launch (or your reflector still isn't working) then paste the results of step #6 above into an email to support so we can help troubleshoot the problem further.