# OS X: Running Projucer from headless console / ssh

**URL:** <https://forum.juce.com/t/os-x-running-projucer-from-headless-console-ssh/17650>\
**Category:** The Projucer\
**Created:** [May 10, 2016, 7:36am UTC](https://forum.juce.com/t/os-x-running-projucer-from-headless-console-ssh/17650 "2016-05-10T07:36:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![myhrman](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@myhrman](https://forum.juce.com/u/myhrman)\
**Post date:** [May 10, 2016, 7:36am UTC](https://forum.juce.com/t/os-x-running-projucer-from-headless-console-ssh/17650/1 "2016-05-10T07:36:34Z")

</div>

We use Projucer to re-generate project files automatically in our continuous integration builds. However, attempting to run Projucer via a headless console on OS X prints a number of error messages:

Projucer : Set a breatpoint at CGSLogError to catch errors as they are logged.  
Projucer : This user is not allowed access to the window system right now.  
\_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, \_CGSDefaultConnection() is NULL.  
Projucer : CGSConnectionByID: 0 is not a valid connection ID.  
Projucer : CGSConnectionByID: 0 is not a valid connection ID.  
Projucer : CGSConnectionByID: 0 is not a valid connection ID.  
Projucer : CGSConnectionByID: 0 is not a valid connection ID.  
Projucer : CGSConnectionByID: 0 is not a valid connection ID.  
Projucer : CGSConnectionByID: 0 is not a valid connection ID.  
Projucer : Invalid Connection ID 0

Simple to re-produce. Just attempt to do “Projucer -help” via SSH.

Could we get slightly better support for this use-case? It seems like it does proceed with the generation of the project files regardless, but doesn’t look good in the log files.