Using Certbot (OwnCloud 9.0.2)

wirestyle22

@travisdh1 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):
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
This would be https://skynetoc.skynetli.com -- https://hostname.domain.com correct?
Right idea, wrong line
ServerName www.travisdh1.net
replace www.travisdh1.net with skynetoc.skynetli.com and remove the ServerAlias line

Is the hostname required? If I only have one server I am pointing to that is an oC server couldn't I get away with just https://skynetli.com ?

JaredBusch

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

@travisdh1 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):
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
This would be https://skynetoc.skynetli.com -- https://hostname.domain.com correct?
Right idea, wrong line
ServerName www.travisdh1.net
replace www.travisdh1.net with skynetoc.skynetli.com and remove the ServerAlias line
Is the hostname required? If I only have one server I am pointing to that is an oC server couldn't I get away with just https://skynetli.com ?

The servername needs to be whatever the incoming servername is in the URL.

wirestyle22

@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 said in Using Certbot (OwnCloud 9.0.2):
@travisdh1 said in Using Certbot (OwnCloud 9.0.2):
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
This would be https://skynetoc.skynetli.com -- https://hostname.domain.com correct?
Right idea, wrong line
ServerName www.travisdh1.net
replace www.travisdh1.net with skynetoc.skynetli.com and remove the ServerAlias line
Is the hostname required? If I only have one server I am pointing to that is an oC server couldn't I get away with just https://skynetli.com ?
The servername needs to be whatever the incoming servername is in the URL.

Alright. Thanks for the info. Now I have to figure out what to do with my google domain. This is all new to me

stacksofplates

@travisdh1 said in Using Certbot (OwnCloud 9.0.2):

replace www.travisdh1.net

Nice test page

wirestyle22

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned:

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

I'm unsure what I need to do with my A record to fix it if that is actually the problem.

dafyre

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Do you have oc.skynetli.com in your public DNS?

JaredBusch

@dafyre said in Using Certbot (OwnCloud 9.0.2):

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Do you have oc.skynetli.com in your public DNS?

And what does your owncloud server think of that DNS address? is it resolving locally?

travisdh1

@johnhooks said in Using Certbot (OwnCloud 9.0.2):

@travisdh1 said in Using Certbot (OwnCloud 9.0.2):

replace www.travisdh1.net

Nice test page

According to ssllabs.com, I have an A rating for SSL security on my test page

wirestyle22

@dafyre said in Using Certbot (OwnCloud 9.0.2):

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Do you have oc.skynetli.com in your public DNS?

I believe so? Unsure how long it takes to apply. Or do I need to create a custom resource? I used to do this a long time ago just in a text document I uploaded using cpanel.

I can ping oc.skynetli.com but it 404's if I try to go to the URL. Is this due to it trying to access 45.63.4.232 instead of 45.63.4.232/owncloud?

wirestyle22

@JaredBusch said in Using Certbot (OwnCloud 9.0.2):

@dafyre said in Using Certbot (OwnCloud 9.0.2):

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Do you have oc.skynetli.com in your public DNS?

And what does your owncloud server think of that DNS address? is it resolving locally?

Unsure of how to check that

travisdh1

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

@JaredBusch said in Using Certbot (OwnCloud 9.0.2):

@dafyre said in Using Certbot (OwnCloud 9.0.2):

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Do you have oc.skynetli.com in your public DNS?

And what does your owncloud server think of that DNS address? is it resolving locally?

Unsure of how to check that

nslookup os.skynetli.com

wirestyle22

@travisdh1 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):

@dafyre said in Using Certbot (OwnCloud 9.0.2):

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Do you have oc.skynetli.com in your public DNS?

And what does your owncloud server think of that DNS address? is it resolving locally?

Unsure of how to check that
nslookup os.skynetli.com

non-existent domain

JaredBusch

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

@travisdh1 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):

@dafyre said in Using Certbot (OwnCloud 9.0.2):

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Do you have oc.skynetli.com in your public DNS?

And what does your owncloud server think of that DNS address? is it resolving locally?

Unsure of how to check that
nslookup os.skynetli.com
non-existent domain

so that means certbot will have no idea how to set stuff up

wirestyle22

@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 said in Using Certbot (OwnCloud 9.0.2):

@JaredBusch said in Using Certbot (OwnCloud 9.0.2):

@dafyre said in Using Certbot (OwnCloud 9.0.2):

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Do you have oc.skynetli.com in your public DNS?

And what does your owncloud server think of that DNS address? is it resolving locally?

Unsure of how to check that
nslookup os.skynetli.com
non-existent domain
so that means certbot will have no idea how to set stuff up

no it means I suck at typing. Totally typo'd.

wirestyle22

@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 said in Using Certbot (OwnCloud 9.0.2):

@JaredBusch said in Using Certbot (OwnCloud 9.0.2):

@dafyre said in Using Certbot (OwnCloud 9.0.2):

@wirestyle22 said in Using Certbot (OwnCloud 9.0.2):

I edited everything for it to be oc.skynetli.com and when I ran ./certbot-auto this is what it returned

Failed authorization procedure. oc.skynetli.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: oc.skynetli.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for oc.skynetli.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Do you have oc.skynetli.com in your public DNS?

And what does your owncloud server think of that DNS address? is it resolving locally?

Unsure of how to check that
nslookup os.skynetli.com
non-existent domain
so that means certbot will have no idea how to set stuff up
no it means I suck at typing. Totally typo'd.

From what I can see it's correct on the server side? I'm guessing my settings on Google Domains are wrong. These are my options:

I'm using Google DNS:

ns-cloud-a1.googledomains.com
ns-cloud-a2.googledomains.com
ns-cloud-a3.googledomains.com
ns-cloud-a4.googledomains.com

travisdh1

@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.

wirestyle22

This post is deleted!

wirestyle22

@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

JaredBusch

@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....

wirestyle22

@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