Connection refused: Operation Timed out in Postgres












0















Ever since upgrading my Mac OS to Mohave, I have been having issues running my rails server locally at my home network. The reason I say home network is because it works just fine when I'm connected on the network at my office. When I run rails s and to go localhost:3000, I see the logs working and running queries to get data from my PG database, until it ultimately stops and times out with the following error:



[2019-01-02T20:13:21.417980 #65251]  INFO -- : method=GET path=/ format=html controller=DashboardController action=index status=500 error='ActionView::Template::Error: could not connect to server: Operation timed out
Is the server running on host "172.18.8.52" and accepting
TCP/IP connections on port 5432?


I tried reinstalling PG with brew, I also tried changing the ports. I checked my firewall and nothing is blocking 5432 port. And oddly enough, I can connect to PG using my PSequel GUI through localhost at port 5432.



The next thing that caught my attention is the IP address listed in the error message. I don't recognize it. After doing nslookup 172.18.8.52 I get:



nslookup 172.18.8.52
Server: 2001:558:feed::1
Address: 2001:558:feed::1#53

** server can't find 52.8.18.172.in-addr.arpa: NXDOMAIN


Can anyone point me to the right direction? This is driving me nuts!



I'm running Rails 5.1.4.



Thank you in advanced!










share|improve this question





























    0















    Ever since upgrading my Mac OS to Mohave, I have been having issues running my rails server locally at my home network. The reason I say home network is because it works just fine when I'm connected on the network at my office. When I run rails s and to go localhost:3000, I see the logs working and running queries to get data from my PG database, until it ultimately stops and times out with the following error:



    [2019-01-02T20:13:21.417980 #65251]  INFO -- : method=GET path=/ format=html controller=DashboardController action=index status=500 error='ActionView::Template::Error: could not connect to server: Operation timed out
    Is the server running on host "172.18.8.52" and accepting
    TCP/IP connections on port 5432?


    I tried reinstalling PG with brew, I also tried changing the ports. I checked my firewall and nothing is blocking 5432 port. And oddly enough, I can connect to PG using my PSequel GUI through localhost at port 5432.



    The next thing that caught my attention is the IP address listed in the error message. I don't recognize it. After doing nslookup 172.18.8.52 I get:



    nslookup 172.18.8.52
    Server: 2001:558:feed::1
    Address: 2001:558:feed::1#53

    ** server can't find 52.8.18.172.in-addr.arpa: NXDOMAIN


    Can anyone point me to the right direction? This is driving me nuts!



    I'm running Rails 5.1.4.



    Thank you in advanced!










    share|improve this question



























      0












      0








      0








      Ever since upgrading my Mac OS to Mohave, I have been having issues running my rails server locally at my home network. The reason I say home network is because it works just fine when I'm connected on the network at my office. When I run rails s and to go localhost:3000, I see the logs working and running queries to get data from my PG database, until it ultimately stops and times out with the following error:



      [2019-01-02T20:13:21.417980 #65251]  INFO -- : method=GET path=/ format=html controller=DashboardController action=index status=500 error='ActionView::Template::Error: could not connect to server: Operation timed out
      Is the server running on host "172.18.8.52" and accepting
      TCP/IP connections on port 5432?


      I tried reinstalling PG with brew, I also tried changing the ports. I checked my firewall and nothing is blocking 5432 port. And oddly enough, I can connect to PG using my PSequel GUI through localhost at port 5432.



      The next thing that caught my attention is the IP address listed in the error message. I don't recognize it. After doing nslookup 172.18.8.52 I get:



      nslookup 172.18.8.52
      Server: 2001:558:feed::1
      Address: 2001:558:feed::1#53

      ** server can't find 52.8.18.172.in-addr.arpa: NXDOMAIN


      Can anyone point me to the right direction? This is driving me nuts!



      I'm running Rails 5.1.4.



      Thank you in advanced!










      share|improve this question
















      Ever since upgrading my Mac OS to Mohave, I have been having issues running my rails server locally at my home network. The reason I say home network is because it works just fine when I'm connected on the network at my office. When I run rails s and to go localhost:3000, I see the logs working and running queries to get data from my PG database, until it ultimately stops and times out with the following error:



      [2019-01-02T20:13:21.417980 #65251]  INFO -- : method=GET path=/ format=html controller=DashboardController action=index status=500 error='ActionView::Template::Error: could not connect to server: Operation timed out
      Is the server running on host "172.18.8.52" and accepting
      TCP/IP connections on port 5432?


      I tried reinstalling PG with brew, I also tried changing the ports. I checked my firewall and nothing is blocking 5432 port. And oddly enough, I can connect to PG using my PSequel GUI through localhost at port 5432.



      The next thing that caught my attention is the IP address listed in the error message. I don't recognize it. After doing nslookup 172.18.8.52 I get:



      nslookup 172.18.8.52
      Server: 2001:558:feed::1
      Address: 2001:558:feed::1#53

      ** server can't find 52.8.18.172.in-addr.arpa: NXDOMAIN


      Can anyone point me to the right direction? This is driving me nuts!



      I'm running Rails 5.1.4.



      Thank you in advanced!







      ruby-on-rails postgresql macos






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 4 at 7:51









      anothermh

      3,36431733




      3,36431733










      asked Jan 3 at 1:18









      Sixers17Sixers17

      2451316




      2451316
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I figured it out. It was an issue with the ssh tunneling.






          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%2f54015189%2fconnection-refused-operation-timed-out-in-postgres%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 figured it out. It was an issue with the ssh tunneling.






            share|improve this answer




























              0














              I figured it out. It was an issue with the ssh tunneling.






              share|improve this answer


























                0












                0








                0







                I figured it out. It was an issue with the ssh tunneling.






                share|improve this answer













                I figured it out. It was an issue with the ssh tunneling.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 24 at 2:13









                Sixers17Sixers17

                2451316




                2451316
































                    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%2f54015189%2fconnection-refused-operation-timed-out-in-postgres%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

                    MongoDB - Not Authorized To Execute Command

                    How to fix TextFormField cause rebuild widget in Flutter

                    in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith