Just paste

/usr/clearos/apps/owncloud/deploy/install

into the command line to run it.

I am just learning to use the linux shell and was wondering, what are the command(s) to re-install the script?
From this location: /usr/clearos/apps/owncloud/deploy/install

Last post today, I promise - for those interested in the the full list of iptables rules implemented in your environment after 1.2.6 just type this command at your SSH prompt:

cat /etc/clearos/firewall.d/10-dnsthingy

One more thing: TCP port 443 traffic destined for the block page is handled with a REJECT iptables rule. No binding there. This is how we address SSL-based ads. Reject vs drop. Dropping would introduce a slower web browser experience, whereas reject behaves very nicely. Browse youtube home page, for example, and see their oversized doubleclick ad is handled.

sorry - duplicate response; didn't see the original post appear right away.

Hi Derick, we have an updated package available (1.2.6) that no longer binds to port 80 at all, but rather to an alternate port. An iptables rule is added instead, so that port 80 traffic destined for the block page interface is re-directed. This way it works with or without apache or any web server that likes exclusive port 80 tcp binding.

We have a few thousand devices across a handful of networks running the updated version for a few days without any trouble. Would you like to try it? If so, just email us at support at dnsthingy.com.

Thanks for reporting this so we could make it better!

I didn't realize it at the time I had owncloud and the web server installed I couldn't get dnsthingy to work. It wasn't until after I removed owncloud and the web server was I able to get dnsthingy to work correctly. Then when Tim replied with the install script location I re-installed owncloud and the web server, but couldn't get the web server to start. So I started looking into it. I ran fuser to find what was listening on port 80 and the PID was associated with dnsthingy. I soon as I killed the PID's the webserver started but then of course dnsthingy wouldn't work. I was unsure how to modify dnsthingy so I made the changes to owncloud and httpd so both service now run as expected. Thanks!

I believe DNSthingy sets port 80 and port 443 to listen

I've just pinged the guys from DNSthingy to clarify this for us...was not aware if this is, in fact, what's happening.

Will report back our findings and how we're going to deal with it.

B.

Thanks! I ran the install script and that got owncloud working! I also found another interesting thing. With DNSthingy installed the webserver service will not start. I believe DNSthingy sets port 80 and port 443 to listen so when the web server attempts to start you get an address already in use error when running systemctl status httpd.service . I changed the /etc/httpd/conf/httpd.conf file to listen on port 84 (unused) and the /etc/httpd/conf.d/flex-80.conf to use port 84 as well as /etc/httpd/conf.d/flex-443.conf to 444 (unused) and now both service start and run as expected. Thanks for the help!

I just did a fresh install of clearos 7.1 home and its doing the same thing. Any help is appreciated.