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

    Nginx not re-directing to host

    Scheduled Pinned Locked Moved IT Discussion
    26 Posts 6 Posters 4.6k Views
    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.
    • wirestyle22W
      wirestyle22 @dbeato
      last edited by wirestyle22

      @dbeato said in Nginx not re-directing to host:

      @wirestyle22 said in Nginx not re-directing to host:

      failed (113: No route to host) while connecting to upstream

      I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.

      Unsure where to really look config-wise to resolve it. From what I see, everything is correct

      dbeatoD 1 Reply Last reply Reply Quote 0
      • coliverC
        coliver
        last edited by

        What ports see you using to communicate with the upstream server?

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

          @wirestyle22 said in Nginx not re-directing to host:

          @dbeato said in Nginx not re-directing to host:

          @wirestyle22 said in Nginx not re-directing to host:

          failed (113: No route to host) while connecting to upstream

          I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.

          Unsure where to really look config-wise to resolve it. From what I see, everything is correct

          I usually try to setup the port on the configuration:

          proxy_Pass http://192.168.1.202:80;
          wirestyle22W 1 Reply Last reply Reply Quote 0
          • wirestyle22W
            wirestyle22 @dbeato
            last edited by wirestyle22

            @dbeato said in Nginx not re-directing to host:

            @wirestyle22 said in Nginx not re-directing to host:

            @dbeato said in Nginx not re-directing to host:

            @wirestyle22 said in Nginx not re-directing to host:

            failed (113: No route to host) while connecting to upstream

            I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.

            Unsure where to really look config-wise to resolve it. From what I see, everything is correct

            I usually try to setup the port on the configuration:

            proxy_Pass http://192.168.1.202:80;
            

            I noticed that JB didn't specify the port in his most recent guide but did in his original guide (was port 80). I tried both ways with the same result.

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

              @coliver said in Nginx not re-directing to host:

              What ports see you using to communicate with the upstream server?

              That's specified in proxy_Pass correct? Port 80 if I am correct. I'm reaching the end of my knowledge with nginx. I was trying to test this to manage my SSL certs with a reverse proxy for learning purposes.

              Syntax:	proxy_pass URL;
              Default:	—
              Context:	location, if in location, limit_except
              Sets the protocol and address of a proxied server and an optional URI to which a location should be mapped. As a protocol, “http” or “https” can be specified. The address can be specified as a domain name or IP address, and an optional port:
              
              proxy_pass http://localhost:8000/uri/;
              
              1 Reply Last reply Reply Quote 0
              • JaredBuschJ
                JaredBusch @wirestyle22
                last edited by

                @wirestyle22 said in Nginx not re-directing to host:

                @dbeato said in Nginx not re-directing to host:

                @wirestyle22 said in Nginx not re-directing to host:

                @dbeato said in Nginx not re-directing to host:

                @wirestyle22 said in Nginx not re-directing to host:

                failed (113: No route to host) while connecting to upstream

                I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.

                Unsure where to really look config-wise to resolve it. From what I see, everything is correct

                I usually try to setup the port on the configuration:

                proxy_Pass http://192.168.1.202:80;
                

                I noticed that JB didn't specify the port in his most recent guide but did in his original guide (was port 80). I tried both ways with the same result.

                Port is not required for 80 or 443 because those are default.

                I can post another example I guess.

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

                  @jaredbusch said in Nginx not re-directing to host:

                  @wirestyle22 said in Nginx not re-directing to host:

                  @dbeato said in Nginx not re-directing to host:

                  @wirestyle22 said in Nginx not re-directing to host:

                  @dbeato said in Nginx not re-directing to host:

                  @wirestyle22 said in Nginx not re-directing to host:

                  failed (113: No route to host) while connecting to upstream

                  I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.

                  Unsure where to really look config-wise to resolve it. From what I see, everything is correct

                  I usually try to setup the port on the configuration:

                  proxy_Pass http://192.168.1.202:80;
                  

                  I noticed that JB didn't specify the port in his most recent guide but did in his original guide (was port 80). I tried both ways with the same result.

                  Port is not required for 80 or 443 because those are default.

                  I can post another example I guess.

                  For sure. I just noticed a difference, not assuming it's wrong. Thanks

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

                    So two things:

                    1. I must have typo'd when opening ports on the Nextcloud server as the proper ports were not actually open as @coliver mentioned.

                    2. I also found a typo in my config.php

                    nc.skynetli.com

                    Working. I knew I did something wrong.

                    Thank you for all of the help @scottalanmiller and @dbeato

                    1 Reply Last reply Reply Quote 1
                    • scottalanmillerS
                      scottalanmiller
                      last edited by

                      I see I get no credit for figuring it out 😉

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

                        @scottalanmiller Sorry! I was tallking to dbeato and got distracted

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