ownCloud Routing
-
@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.
-
I just did a clean install of CentOS and setup virtual hosts as described in this document. https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-centos-7
I did not change any ports. I restarted Apache and I still get this
-
Doing anything to Apache on your ownCloud server is WRONG.
There is no need to do anything in apache (unless you are adding SSL).
Here are my setup instructions for ownCloud on CentOS.
They need a little minor updating, but work 100% if you leave SELinux disabled. -
There is a single damned setting that will fix the URL. I told you to set it in the other post.
You have not listened to a damned thing I suggested, so I stopped helping.
-
Thanks for all your help Jared and thanks for the setup instructions.
-
@alex.olynyk said:
Thanks for all your help Jared and thanks for the setup instructions.
The piece you need to set are in the followup post on using SSL soI will put them here for you.
Add the DNS name to the trusted domains array
1 => 'owncloud.domain.com',updated the overwrite.cli.url to use the DNS name
'overwrite.cli.url' => 'https://owncloud.domain.com/owncloud', -
Go into your DNS server at each site and add a record for owncloud.domain.com pointing to the internal IP address of your owncloud box.
Go into your public DNS host and add an a record pointing back to your public IP.
Setup port forwarding on your firewall for port 80 to go to the internal IP of your owncloud box.
-
Port forwarding is working. Thank you.
I added an A record on my public DNS host pointing back to the public IP. How long until it goes into effect?
-
@alex.olynyk Should be almost instant.
Did you run ipconfig /flushdns on your client?
-
Yes
-
@alex.olynyk said:
Port forwarding is working. Thank you.
I added an A record on my public DNS host pointing back to the public IP. How long until it goes into effect?
Did you put in the local IP in your local DNS?
You should never rely on NAT Hairpinning
-
@alex.olynyk said:
I added an A record on my public DNS host pointing back to the public IP. How long until it goes into effect?
It technically goes into effect immediately. But it takes a bit to converge. But generally I see 99% of things converged in under 15 minutes.
-
@JaredBusch said:
Did you put in the local IP in your local DNS?
This is very important, you can't skip this step.
-
@scottalanmiller said:
@JaredBusch said:
Did you put in the local IP in your local DNS?
This is very important, you can't skip this step.
He also never stated that he fixed his ownCloud config.php either. I listed 3 clear steps. He said he did step 3.
-
@JaredBusch said:
@alex.olynyk said:
Port forwarding is working. Thank you.
I added an A record on my public DNS host pointing back to the public IP. How long until it goes into effect?
Did you put in the local IP in your local DNS?
You should never rely on NAT Hairpinning
Yes
-
the local ones will be instant.
