Using Certbot (OwnCloud 9.0.2)
-
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
You need to create a custom resource record for Google Domains and the default is @ which should be changed to the hostname. So in my case it's oc for the resource name and my ipv4 address. It was that easy. Now the issue I have is the ip address is associated with the apache test page. I need it to go to x.x.x.x/owncloud not x.x.x.x
-
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
You need to create a custom resource record for Google Domains and the default is @ which should be changed to the hostname. So in my case it's oc for the resource name and my ipv4 address. It was that easy. Now the issue I have is the ip address is associated with the apache test page. I need it to go to x.x.x.x/owncloud not x.x.x.x
you can add a redirect in your apache conf for that
-
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
You need to create a custom resource record for Google Domains and the default is @ which should be changed to the hostname. So in my case it's oc for the resource name and my ipv4 address. It was that easy. Now the issue I have is the ip address is associated with the apache test page. I need it to go to x.x.x.x/owncloud not x.x.x.x
you can add a redirect in your apache conf for that
I'm going to go through it now. Appreciate all of the help
-
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
You need to create a custom resource record for Google Domains and the default is @ which should be changed to the hostname. So in my case it's oc for the resource name and my ipv4 address. It was that easy. Now the issue I have is the ip address is associated with the apache test page. I need it to go to x.x.x.x/owncloud not x.x.x.x
you can add a redirect in your apache conf for that
Interesting issue. This is what the config looks like:
The redirect worked except for the owncloud part. The URL looks like: http://45.63.4.232/owncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloud/index.php
-
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
You need to create a custom resource record for Google Domains and the default is @ which should be changed to the hostname. So in my case it's oc for the resource name and my ipv4 address. It was that easy. Now the issue I have is the ip address is associated with the apache test page. I need it to go to x.x.x.x/owncloud not x.x.x.x
you can add a redirect in your apache conf for that
Interesting issue. This is what the config looks like:
The redirect worked except for the owncloud part. The URL looks like: http://45.63.4.232/owncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloud/index.php
ROFL... I wonder if it was the space between http:// and the Ip address that broke it?
-
@dafyre said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
You need to create a custom resource record for Google Domains and the default is @ which should be changed to the hostname. So in my case it's oc for the resource name and my ipv4 address. It was that easy. Now the issue I have is the ip address is associated with the apache test page. I need it to go to x.x.x.x/owncloud not x.x.x.x
you can add a redirect in your apache conf for that
Interesting issue. This is what the config looks like:
The redirect worked except for the owncloud part. The URL looks like: http://45.63.4.232/owncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloud/index.php
ROFL... I wonder if it was the space between http:// and the Ip address that broke it?
lol. no i just edited it and accidentally did that. Don't want travis listed as the admin
-
@dafyre said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 Take a gander at this
[root@travisdh1 ~]# nslookup oc.skynetli.com ns-cloud-a1.googledomains.com Server: ns-cloud-a1.googledomains.com Address: 2001:4860:4802:32::6a#53 ** server can't find oc.skynetli.com: NXDOMAIN
So, something is wrong with your name server settings/config. I'd open a support ticket with Google Domains, probably get you sorted out quickly.
It was a syntax issue. Ughhhhh
and that was....
You need to create a custom resource record for Google Domains and the default is @ which should be changed to the hostname. So in my case it's oc for the resource name and my ipv4 address. It was that easy. Now the issue I have is the ip address is associated with the apache test page. I need it to go to x.x.x.x/owncloud not x.x.x.x
you can add a redirect in your apache conf for that
Interesting issue. This is what the config looks like:
The redirect worked except for the owncloud part. The URL looks like: http://45.63.4.232/owncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloud/index.php
ROFL... I wonder if it was the space between http:// and the Ip address that broke it?
There. Edited.
-
@wirestyle22 why are yo redirecting to the IP? everything should be DNS names
-
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 why are yo redirecting to the IP? everything should be DNS names
How do I point directly to x.x.x.x/owncloud then?
EDIT: nvm got it.
-
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 why are yo redirecting to the IP? everything should be DNS names
How do I point directly to x.x.x.x/owncloud then?
EDIT: nvm got it.
Did you also fix the url issue? is so post your cleaned up config
-
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 why are yo redirecting to the IP? everything should be DNS names
How do I point directly to x.x.x.x/owncloud then?
EDIT: nvm got it.
Did you also fix the url issue? is so post your cleaned up config
No, I'm working on it though. Great learning experience.
-
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 why are yo redirecting to the IP? everything should be DNS names
How do I point directly to x.x.x.x/owncloud then?
EDIT: nvm got it.
Did you also fix the url issue? is so post your cleaned up config
No, I'm working on it though. Great learning experience.
I would start by removing all of the rewrites and redirects.
Then add in a single one.
Make sure it works right. then add in more functionality. one at a time.
-
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
@wirestyle22 why are yo redirecting to the IP? everything should be DNS names
How do I point directly to x.x.x.x/owncloud then?
EDIT: nvm got it.
Did you also fix the url issue? is so post your cleaned up config
No, I'm working on it though. Great learning experience.
I would start by removing all of the rewrites and redirects.
Then add in a single one.
Make sure it works right. then add in more functionality. one at a time.
On it. Thanks
-
http://oc.skynetli.com/owncloud/ works with no redirects or rewrites so now I have to figure out what part of it is breaking.
Note: It's the redirect. Checking syntax.
-
Everything I see written has it exactly as I do. Unsure of why the redirect is breaking.
-
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
Everything I see written has it exactly as I do. Unsure of why the redirect is breaking.
Current conf file (as text not image)?
-
And were you looking at the Apache documentation itself? Or random examples?
-
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
And were you looking at the Apache documentation itself? Or random examples?
Random examples I guess. Thought they were reputable though.
-
@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):
@JaredBusch said in Using Certbot (OwnCloud 9.0.2):
And were you looking at the Apache documentation itself? Or random examples?
Random examples I guess. Thought they were reputable though.
Every last example is going to be a little different than what you're particular install will need to work correctly, so study that documentation.
-
Also make sure the documentation you are looking at is for the same version of Apache! Between 2.2 and 2.4, there were a lot of changes under the hood with that.