Pgadmin4: Invalid HTTP Version 'Invalid HTTP Version: 'on postgres@domain.tld HTTP/1.0''












0















--------------------------------------------------------
| Pgadmin version | 4.3.5 |
--------------------------------------------------------
| PostgreSQL server version | pg_ctl (PostgreSQL) 11.1 |
--------------------------------------------------------
| Docker image | dpage/pgadmin4 |
--------------------------------------------------------


I ran into a problem using PGAdmin4 in Docker container. When i'm connecting to my host`s machine postgresql server and trying to view/edit data - i'm getting such error: https://pasteboard.co/HO1w7jS.png



Note that:




  • I have default postgresql configuration, except listen_addresses = '127.0.0.1, 172.17.0.1.

  • PGAdmin container is behind nginx proxy mydomain.tld -> localhost:5050


As i understand, it is a problem with postgresql HTTP API. But i'm not an expert neither in postgresql nor in pgadmin. Maybe anyone have solution to this problem?










share|improve this question























  • I'm seeing a similar issue. Did you find a resolution?

    – psychemedia
    Feb 4 at 11:12











  • @psychemedia yep. See the answer

    – Bloody Altair
    Feb 6 at 22:00
















0















--------------------------------------------------------
| Pgadmin version | 4.3.5 |
--------------------------------------------------------
| PostgreSQL server version | pg_ctl (PostgreSQL) 11.1 |
--------------------------------------------------------
| Docker image | dpage/pgadmin4 |
--------------------------------------------------------


I ran into a problem using PGAdmin4 in Docker container. When i'm connecting to my host`s machine postgresql server and trying to view/edit data - i'm getting such error: https://pasteboard.co/HO1w7jS.png



Note that:




  • I have default postgresql configuration, except listen_addresses = '127.0.0.1, 172.17.0.1.

  • PGAdmin container is behind nginx proxy mydomain.tld -> localhost:5050


As i understand, it is a problem with postgresql HTTP API. But i'm not an expert neither in postgresql nor in pgadmin. Maybe anyone have solution to this problem?










share|improve this question























  • I'm seeing a similar issue. Did you find a resolution?

    – psychemedia
    Feb 4 at 11:12











  • @psychemedia yep. See the answer

    – Bloody Altair
    Feb 6 at 22:00














0












0








0








--------------------------------------------------------
| Pgadmin version | 4.3.5 |
--------------------------------------------------------
| PostgreSQL server version | pg_ctl (PostgreSQL) 11.1 |
--------------------------------------------------------
| Docker image | dpage/pgadmin4 |
--------------------------------------------------------


I ran into a problem using PGAdmin4 in Docker container. When i'm connecting to my host`s machine postgresql server and trying to view/edit data - i'm getting such error: https://pasteboard.co/HO1w7jS.png



Note that:




  • I have default postgresql configuration, except listen_addresses = '127.0.0.1, 172.17.0.1.

  • PGAdmin container is behind nginx proxy mydomain.tld -> localhost:5050


As i understand, it is a problem with postgresql HTTP API. But i'm not an expert neither in postgresql nor in pgadmin. Maybe anyone have solution to this problem?










share|improve this question














--------------------------------------------------------
| Pgadmin version | 4.3.5 |
--------------------------------------------------------
| PostgreSQL server version | pg_ctl (PostgreSQL) 11.1 |
--------------------------------------------------------
| Docker image | dpage/pgadmin4 |
--------------------------------------------------------


I ran into a problem using PGAdmin4 in Docker container. When i'm connecting to my host`s machine postgresql server and trying to view/edit data - i'm getting such error: https://pasteboard.co/HO1w7jS.png



Note that:




  • I have default postgresql configuration, except listen_addresses = '127.0.0.1, 172.17.0.1.

  • PGAdmin container is behind nginx proxy mydomain.tld -> localhost:5050


As i understand, it is a problem with postgresql HTTP API. But i'm not an expert neither in postgresql nor in pgadmin. Maybe anyone have solution to this problem?







postgresql docker pgadmin pgadmin-4






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 20 '18 at 10:31









Bloody AltairBloody Altair

112




112













  • I'm seeing a similar issue. Did you find a resolution?

    – psychemedia
    Feb 4 at 11:12











  • @psychemedia yep. See the answer

    – Bloody Altair
    Feb 6 at 22:00



















  • I'm seeing a similar issue. Did you find a resolution?

    – psychemedia
    Feb 4 at 11:12











  • @psychemedia yep. See the answer

    – Bloody Altair
    Feb 6 at 22:00

















I'm seeing a similar issue. Did you find a resolution?

– psychemedia
Feb 4 at 11:12





I'm seeing a similar issue. Did you find a resolution?

– psychemedia
Feb 4 at 11:12













@psychemedia yep. See the answer

– Bloody Altair
Feb 6 at 22:00





@psychemedia yep. See the answer

– Bloody Altair
Feb 6 at 22:00












1 Answer
1






active

oldest

votes


















0














The problem was in regular expression for nginx location. Nginx somehow strangely truncates the URL parameters.



Perhaps this is due to the use of this patch: https://stackoverflow.com/a/50515636/9547899 (I use it to redirect requests to pgadmin to a subdirectory)



It was:



location ~ /PostgreSQL(.*)$ {
proxy_pass http://127.0.0.1:23301$1;


It became:



location ~ PostgreSQL {
proxy_pass http://127.0.0.1:23301;





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%2f53391031%2fpgadmin4-invalid-http-version-invalid-http-version-on-postgresdomain-tld-ht%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














    The problem was in regular expression for nginx location. Nginx somehow strangely truncates the URL parameters.



    Perhaps this is due to the use of this patch: https://stackoverflow.com/a/50515636/9547899 (I use it to redirect requests to pgadmin to a subdirectory)



    It was:



    location ~ /PostgreSQL(.*)$ {
    proxy_pass http://127.0.0.1:23301$1;


    It became:



    location ~ PostgreSQL {
    proxy_pass http://127.0.0.1:23301;





    share|improve this answer




























      0














      The problem was in regular expression for nginx location. Nginx somehow strangely truncates the URL parameters.



      Perhaps this is due to the use of this patch: https://stackoverflow.com/a/50515636/9547899 (I use it to redirect requests to pgadmin to a subdirectory)



      It was:



      location ~ /PostgreSQL(.*)$ {
      proxy_pass http://127.0.0.1:23301$1;


      It became:



      location ~ PostgreSQL {
      proxy_pass http://127.0.0.1:23301;





      share|improve this answer


























        0












        0








        0







        The problem was in regular expression for nginx location. Nginx somehow strangely truncates the URL parameters.



        Perhaps this is due to the use of this patch: https://stackoverflow.com/a/50515636/9547899 (I use it to redirect requests to pgadmin to a subdirectory)



        It was:



        location ~ /PostgreSQL(.*)$ {
        proxy_pass http://127.0.0.1:23301$1;


        It became:



        location ~ PostgreSQL {
        proxy_pass http://127.0.0.1:23301;





        share|improve this answer













        The problem was in regular expression for nginx location. Nginx somehow strangely truncates the URL parameters.



        Perhaps this is due to the use of this patch: https://stackoverflow.com/a/50515636/9547899 (I use it to redirect requests to pgadmin to a subdirectory)



        It was:



        location ~ /PostgreSQL(.*)$ {
        proxy_pass http://127.0.0.1:23301$1;


        It became:



        location ~ PostgreSQL {
        proxy_pass http://127.0.0.1:23301;






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 6 at 22:00









        Bloody AltairBloody Altair

        112




        112
































            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%2f53391031%2fpgadmin4-invalid-http-version-invalid-http-version-on-postgresdomain-tld-ht%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







            這個網誌中的熱門文章

            Xamarin.form Move up view when keyboard appear

            Post-Redirect-Get with Spring WebFlux and Thymeleaf

            Anylogic : not able to use stopDelay()