Gcloud internal Loadbalancer unable to connect












0















I have created 1 Instance Group having two instances of Redis running on port 6379.



Created 1 internal load balancer (TCP) having backend of Redis instance group.



Issue 1 - If i add Healthcheck of TCP 6379 LB status shows no healthy instance, when I change to tcp 80 LB shows healthy.



Issue 2 - Unable to connect to LB IP from another instance of same project.










share|improve this question





























    0















    I have created 1 Instance Group having two instances of Redis running on port 6379.



    Created 1 internal load balancer (TCP) having backend of Redis instance group.



    Issue 1 - If i add Healthcheck of TCP 6379 LB status shows no healthy instance, when I change to tcp 80 LB shows healthy.



    Issue 2 - Unable to connect to LB IP from another instance of same project.










    share|improve this question



























      0












      0








      0








      I have created 1 Instance Group having two instances of Redis running on port 6379.



      Created 1 internal load balancer (TCP) having backend of Redis instance group.



      Issue 1 - If i add Healthcheck of TCP 6379 LB status shows no healthy instance, when I change to tcp 80 LB shows healthy.



      Issue 2 - Unable to connect to LB IP from another instance of same project.










      share|improve this question
















      I have created 1 Instance Group having two instances of Redis running on port 6379.



      Created 1 internal load balancer (TCP) having backend of Redis instance group.



      Issue 1 - If i add Healthcheck of TCP 6379 LB status shows no healthy instance, when I change to tcp 80 LB shows healthy.



      Issue 2 - Unable to connect to LB IP from another instance of same project.







      google-cloud-platform google-compute-engine






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 22 '18 at 21:19









      montrealist

      2,98283850




      2,98283850










      asked Nov 22 '18 at 8:49









      Hemant RaiHemant Rai

      1




      1
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I would suggest the following checks to be performed in order to isolate both the issues.




          1. Make sure the redis service is running on the specific port and is not bind to a specific address (e.g., localhost) and is listening for all addresses (0.0.0.0/0) on port 6379.

          2. Make sure proper firewall rules are set to allow health check probes (130.211.0.0/22 and 35.191.0.0/16) to the reach the redis backends on port 6379.

          3. Make sure the client instance originating traffic, i.e., the instance trying to connect to Internal Load Balancer (ILB), belongs to the same VPC network (but can be in a different subnet) and region as the internal load balancing forwarding rule IP, backend services, and instance groups.


          Further details on internal load balancing can be found in this help center article.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426988%2fgcloud-internal-loadbalancer-unable-to-connect%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I would suggest the following checks to be performed in order to isolate both the issues.




            1. Make sure the redis service is running on the specific port and is not bind to a specific address (e.g., localhost) and is listening for all addresses (0.0.0.0/0) on port 6379.

            2. Make sure proper firewall rules are set to allow health check probes (130.211.0.0/22 and 35.191.0.0/16) to the reach the redis backends on port 6379.

            3. Make sure the client instance originating traffic, i.e., the instance trying to connect to Internal Load Balancer (ILB), belongs to the same VPC network (but can be in a different subnet) and region as the internal load balancing forwarding rule IP, backend services, and instance groups.


            Further details on internal load balancing can be found in this help center article.






            share|improve this answer




























              0














              I would suggest the following checks to be performed in order to isolate both the issues.




              1. Make sure the redis service is running on the specific port and is not bind to a specific address (e.g., localhost) and is listening for all addresses (0.0.0.0/0) on port 6379.

              2. Make sure proper firewall rules are set to allow health check probes (130.211.0.0/22 and 35.191.0.0/16) to the reach the redis backends on port 6379.

              3. Make sure the client instance originating traffic, i.e., the instance trying to connect to Internal Load Balancer (ILB), belongs to the same VPC network (but can be in a different subnet) and region as the internal load balancing forwarding rule IP, backend services, and instance groups.


              Further details on internal load balancing can be found in this help center article.






              share|improve this answer


























                0












                0








                0







                I would suggest the following checks to be performed in order to isolate both the issues.




                1. Make sure the redis service is running on the specific port and is not bind to a specific address (e.g., localhost) and is listening for all addresses (0.0.0.0/0) on port 6379.

                2. Make sure proper firewall rules are set to allow health check probes (130.211.0.0/22 and 35.191.0.0/16) to the reach the redis backends on port 6379.

                3. Make sure the client instance originating traffic, i.e., the instance trying to connect to Internal Load Balancer (ILB), belongs to the same VPC network (but can be in a different subnet) and region as the internal load balancing forwarding rule IP, backend services, and instance groups.


                Further details on internal load balancing can be found in this help center article.






                share|improve this answer













                I would suggest the following checks to be performed in order to isolate both the issues.




                1. Make sure the redis service is running on the specific port and is not bind to a specific address (e.g., localhost) and is listening for all addresses (0.0.0.0/0) on port 6379.

                2. Make sure proper firewall rules are set to allow health check probes (130.211.0.0/22 and 35.191.0.0/16) to the reach the redis backends on port 6379.

                3. Make sure the client instance originating traffic, i.e., the instance trying to connect to Internal Load Balancer (ILB), belongs to the same VPC network (but can be in a different subnet) and region as the internal load balancing forwarding rule IP, backend services, and instance groups.


                Further details on internal load balancing can be found in this help center article.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 '18 at 21:07









                IshtiaqueIshtiaque

                202




                202
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426988%2fgcloud-internal-loadbalancer-unable-to-connect%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Can a sorcerer learn a 5th-level spell early by creating spell slots using the Font of Magic feature?

                    Does disintegrating a polymorphed enemy still kill it after the 2018 errata?

                    A Topological Invariant for $pi_3(U(n))$