An upgrade to accomodate Darwin is critical for cPanel to run properly along side Darwin Streaming Server, even if it is installed and configured manually manually. It is the nature of the streaming that it most often has to be delivered over port 80 to ensure it can be viewed from behind any normal firewalls, ie. lynksis, dlink, etc. I have gone through the process of manually tweaking httpd.conf so that apache and Darwin Streaming Server can live happily together on port 80. Port 80 streaming from Darwin bound to an specific IP address is essential for many installations, and even with much tweaking it is impossible to have cPanel live in harmony. Currently I have Darwin bound to a specific IP on port 80, and Apache is running fine, but my WHM / cPanel thinks that Apache is down, which is a major problem. I have even had to disable httpd in the chkserd Service Monitor routines, or it will be restarted every minute when it is actually working. Darwin Streaming Server should actually be relatively straight forward to integrate nicely, it is not a complicated installation, and the configuration is very consistent. Specific details to configure both Darwin & Apache on port 80: DARWIN STREAMING SERVER: /etc/streaming/streamingserver.xml specify desired IP for streaming server: <PREF NAME="bind_ip_addr" >0</PREF> APACHE httpd.conf remove "port 80" from <define SSL></defineSSL> add "Listen 0.0.0.0:80" for all IP's that need apache add again "Listen 0.0.0.0:443" for all IP's that need apache SSL within <define SSL></defineSSL> That's it! WHM is at this point only happy when Apache loads on every single IP bound to the server. Perhaps some binding control could be a feature, or automatically handled by the Darwin config, adding all IP's for listening to httpd.conf, but not the one bound to Darwin. I also bind the admin server to the same IP with the following: /etc/streamingadminserver.conf bind=0.0.0.0 (IP of choice) Once initially added, the Darwin support could be expanded easily for more advanced configuration, as all streaming configuration is withing one logical XML file (/etc/streaming/streamingserver.xml). The admin interface could also be accessible. Please get the Apache status reading properly ASAP.