ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Using Certbot (OwnCloud 9.0.2)

    IT Discussion
    5
    46
    11.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch @wirestyle22
      last edited by

      @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

      wirestyle22W 1 Reply Last reply Reply Quote 1
      • wirestyle22W
        wirestyle22 @JaredBusch
        last edited by 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.

        0_1464279872316_ugh.jpg

        wirestyle22W 1 Reply Last reply Reply Quote 2
        • wirestyle22W
          wirestyle22 @wirestyle22
          last edited by 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:

          0_1464280111831_sad.jpg

          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

          travisdh1T 1 Reply Last reply Reply Quote 0
          • travisdh1T
            travisdh1 @wirestyle22
            last edited by

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

            wirestyle22W 2 Replies Last reply Reply Quote 1
            • wirestyle22W
              wirestyle22 @travisdh1
              last edited by

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • wirestyle22W
                wirestyle22 @travisdh1
                last edited by

                @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

                JaredBuschJ 1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch @wirestyle22
                  last edited by

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

                  wirestyle22W 1 Reply Last reply Reply Quote 0
                  • wirestyle22W
                    wirestyle22 @JaredBusch
                    last edited by 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

                    JaredBuschJ 1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch @wirestyle22
                      last edited by

                      @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

                      wirestyle22W 2 Replies Last reply Reply Quote 0
                      • wirestyle22W
                        wirestyle22 @JaredBusch
                        last edited by

                        @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

                        1 Reply Last reply Reply Quote 0
                        • wirestyle22W
                          wirestyle22 @JaredBusch
                          last edited by wirestyle22

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

                          0_1464360559243_config.jpg

                          The redirect worked except for the owncloud part. The URL looks like: http://45.63.4.232/owncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloudowncloud/index.php

                          dafyreD JaredBuschJ 2 Replies Last reply Reply Quote 0
                          • dafyreD
                            dafyre @wirestyle22
                            last edited by

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

                            0_1464360175273_config.jpg

                            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?

                            wirestyle22W 2 Replies Last reply Reply Quote 0
                            • wirestyle22W
                              wirestyle22 @dafyre
                              last edited by

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

                              0_1464360175273_config.jpg

                              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

                              1 Reply Last reply Reply Quote 0
                              • wirestyle22W
                                wirestyle22 @dafyre
                                last edited by

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

                                0_1464360175273_config.jpg

                                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.

                                1 Reply Last reply Reply Quote 0
                                • JaredBuschJ
                                  JaredBusch @wirestyle22
                                  last edited by

                                  @wirestyle22 why are yo redirecting to the IP? everything should be DNS names

                                  wirestyle22W 1 Reply Last reply Reply Quote 1
                                  • wirestyle22W
                                    wirestyle22 @JaredBusch
                                    last edited by wirestyle22

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

                                    JaredBuschJ 1 Reply Last reply Reply Quote 2
                                    • JaredBuschJ
                                      JaredBusch @wirestyle22
                                      last edited by

                                      @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

                                      wirestyle22W 1 Reply Last reply Reply Quote 1
                                      • wirestyle22W
                                        wirestyle22 @JaredBusch
                                        last edited by

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

                                        JaredBuschJ 1 Reply Last reply Reply Quote 0
                                        • JaredBuschJ
                                          JaredBusch @wirestyle22
                                          last edited by

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

                                          wirestyle22W 1 Reply Last reply Reply Quote 0
                                          • wirestyle22W
                                            wirestyle22 @JaredBusch
                                            last edited by

                                            @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

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post