ownCloud Routing
-
-
@scottalanmiller said:
Just to be clear, for your MSP process, it's not a traditional MSP that you want but a consultant. You want someone who will oversee your processes, not just someone who can outsource desktop work.
Thats what we are using
-
@scottalanmiller said:
Just to be clear, for your MSP process, it's not a traditional MSP that you want but a consultant. You want someone who will oversee your processes, not just someone who can outsource desktop work.
Also it should be someone that you pay explicitly for this service... not on top of other services. I think @scottalanmiller has an article about getting advice from a vendor somewhere.
-
@coliver said:
@scottalanmiller said:
Just to be clear, for your MSP process, it's not a traditional MSP that you want but a consultant. You want someone who will oversee your processes, not just someone who can outsource desktop work.
Also it should be someone that you pay explicitly for this service... not on top of other services. I think @scottalanmiller has an article about getting advice from a vendor somewhere.
Yes, the important thing is that they are not a reseller with product to push.
-
@alex.olynyk said:
@coliver said:
@alex.olynyk said:
What steps do i need to take to access it by hostname?
If you're using apache (I will assume you are) you need to edit your virtualhost:80 and virtualhost:443 to have the ServerName be owncloud.mycompany.com.
where are these files?
I have httpd.conf opened and am searching it for virtualhost:80 and virtualhost:443 but I dont see these directives. Do I have to add them first?
-
@alex.olynyk said:
@alex.olynyk said:
@coliver said:
@alex.olynyk said:
What steps do i need to take to access it by hostname?
If you're using apache (I will assume you are) you need to edit your virtualhost:80 and virtualhost:443 to have the ServerName be owncloud.mycompany.com.
where are these files?
I have httpd.conf opened and am searching it for virtualhost:80 and virtualhost:443 but I dont see these directives. Do I have to add them first?
It should look like:
<Virtualhost *:80>as the opening line. It is a block of code with defined flags below it.
-
@coliver
here is my httpd.conf i dont see it -
Is that the whole file? If that is the case then the virtualhost configurations are probably in their own location under /etc/httpd.
What text editor are you using?
-
@coliver said:
Is that the whole file? If that is the case then the virtualhost configurations are probably in their own location under /etc/httpd.
What text editor are you using?
VI
-
@alex.olynyk said:
@coliver said:
Is that the whole file? If that is the case then the virtualhost configurations are probably in their own location under /etc/httpd.
What text editor are you using?
VI
contents of /etc/httpd
-
Ok, so open the /etc/httpd/conf/httpd.conf file. And then do type the following:
/<VirtualHost *:8080>The '/' is the vi shortcut to search for the following string. The VirtualHost should look like the following:
<VirtualHost *:8080> ServerAdmin [email protected] DocumentRoot /www/docs/dummy-host.example.com ServerName dummy-host.example.com ErrorLog logs/dummy-host.example.com-error_log CustomLog logs/dummy-host.example.com-access_log common </VirtualHost>You'll want to edit it with the appropriate info.
-
@coliver pattern not found
is this what i need to follow? https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-centos-7
-
Yes. That's pretty much what you need.
-
I followed the directions in https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-centos-7
now apache wont start
any ideas?
-
Do you have the port you are using defined in two different locations? Did you do a systemctl stop httpd before trying to restart it?
-
@coliver i changed the listen port from 8080 to 80 as it everyone asked why I didnt leave it on 80
-
It's complaining about port 443 though.
-
then added port 80 to firewalld
-
@alex.olynyk said:
@coliver i changed the listen port from 8080 to 80 as it everyone asked why I didnt leave it on 80
Yeah, changing ports is best only when there is a solid reason, should not be done casually. It's a trivial thing, but just "one more" potential point for a problem and just... why?
-
@alex.olynyk said:
@coliver i changed the listen port from 8080 to 80 as it everyone asked why I didnt leave it on 80
Good, I was going to comment on it but figured you had a reason for it to be that way.
