Joomla Extension Uninstall Causes 502 Bad GatewayNginx + PHP-FPM = “Random” 502 Bad GatewayNginx +...

Source permutation

MySQL importing CSV files really slow

Giving a career talk in my old university, how prominently should I tell students my salary?

Why is a very small peak with larger m/z not considered to be the molecular ion?

How do we create new idioms and use them in a novel?

Does an unused member variable take up memory?

What will happen if my luggage gets delayed?

The meaning of ‘otherwise’

Making a kiddush for a girl that has hard time finding shidduch

Which situations would cause a company to ground or recall a aircraft series?

Is this Paypal Github SDK reference really a dangerous site?

What materials can be used to make a humanoid skin warm?

In the late 1940’s to early 1950’s what technology was available that could melt ice?

What do you call someone who likes to pick fights?

Does a difference of tense count as a difference of meaning in a minimal pair?

Shifting between bemols and diesis in the key signature

What are some noteworthy "mic-drop" moments in math?

Why does cron require MTA for logging?

How does Ehrenfest's theorem apply to the quantum harmonic oscillator?

Professor forcing me to attend a conference, I can't afford even with 50% funding

From an axiomatic set theoric approach why can we take uncountable unions?

Plausibility of Mushroom Buildings

Dynamic Linkage of LocatorPane and InputField

PTIJ: Why does only a Shor Tam ask at the Seder, and not a Shor Mu'ad?



Joomla Extension Uninstall Causes 502 Bad Gateway


Nginx + PHP-FPM = “Random” 502 Bad GatewayNginx + PHP-FPM on Ubuntu giving “upstream sent invalid status” on uploading Joomla extension zip fileNginx: Bad Gateway 502 errorGetting 502 bad gateway after updating php to 5.5502 Bad Gateway NginxDocker + nginx + Php-FPM 502 Bad Gateway504 Gateway timeout / 502 Bad gateway after installing php curl - server nginx502 bad gateway error nginx connection reset by peerNGINX and PHP-FPM 502 bad gateway502 Bad Gateway with dockerized PHP-FPM













0















We have a VPS with some PHP websites hosted on our Ubuntu 12.04 LTS servers using NGINX. In a Joomla 3 site, when uninstalling an extension that errors out, the page shows an NGINX error page with a 502 Bad Gateway rather than showing the error message within Joomla like it does in Apache.



The error log message produces an obvious error as to why the site broke and easy to fix from the extension itself (db connectivity error from PostgreSQL).



2014/05/06 16:26:12 [error] 17702#0: *26 upstream sent invalid status "0 Error connecting to PGSQL database." while reading response header from upstream, client: xx.xx.xxx.xx, server: sub.example.com, request: "POST /administrator/index.php?option=com_installer&view=manage HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "sub.example.com", referrer: "http://sub.example.com/administrator/index.php?option=com_installer&view=manage"


As the error points out, it's a PostgreSQL database connection error.



In my research, I found that 502 Bad Gateway is usually the result of an incorrectly set configuration file. This is what leads me to think that when something errors out in Joomla, the error isn't handled properly and display the 502 error page.



What I need to know is: why does the site error out as a 502 Bag Gateway error in NGINX + PHP-FPM when the DB connectivity error occurs? Is this an incorrect configuration in NGINX and/or PHP-FPM or is this how this usually handles errors?



Image of how Joomla w/apache handles the same error:



Joomla w/apache postgres connection error



Note: I've used the Joomla configuration from http://docs.joomla.org/Nginx










share|improve this question
















bumped to the homepage by Community 4 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    We have a VPS with some PHP websites hosted on our Ubuntu 12.04 LTS servers using NGINX. In a Joomla 3 site, when uninstalling an extension that errors out, the page shows an NGINX error page with a 502 Bad Gateway rather than showing the error message within Joomla like it does in Apache.



    The error log message produces an obvious error as to why the site broke and easy to fix from the extension itself (db connectivity error from PostgreSQL).



    2014/05/06 16:26:12 [error] 17702#0: *26 upstream sent invalid status "0 Error connecting to PGSQL database." while reading response header from upstream, client: xx.xx.xxx.xx, server: sub.example.com, request: "POST /administrator/index.php?option=com_installer&view=manage HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "sub.example.com", referrer: "http://sub.example.com/administrator/index.php?option=com_installer&view=manage"


    As the error points out, it's a PostgreSQL database connection error.



    In my research, I found that 502 Bad Gateway is usually the result of an incorrectly set configuration file. This is what leads me to think that when something errors out in Joomla, the error isn't handled properly and display the 502 error page.



    What I need to know is: why does the site error out as a 502 Bag Gateway error in NGINX + PHP-FPM when the DB connectivity error occurs? Is this an incorrect configuration in NGINX and/or PHP-FPM or is this how this usually handles errors?



    Image of how Joomla w/apache handles the same error:



    Joomla w/apache postgres connection error



    Note: I've used the Joomla configuration from http://docs.joomla.org/Nginx










    share|improve this question
















    bumped to the homepage by Community 4 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      We have a VPS with some PHP websites hosted on our Ubuntu 12.04 LTS servers using NGINX. In a Joomla 3 site, when uninstalling an extension that errors out, the page shows an NGINX error page with a 502 Bad Gateway rather than showing the error message within Joomla like it does in Apache.



      The error log message produces an obvious error as to why the site broke and easy to fix from the extension itself (db connectivity error from PostgreSQL).



      2014/05/06 16:26:12 [error] 17702#0: *26 upstream sent invalid status "0 Error connecting to PGSQL database." while reading response header from upstream, client: xx.xx.xxx.xx, server: sub.example.com, request: "POST /administrator/index.php?option=com_installer&view=manage HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "sub.example.com", referrer: "http://sub.example.com/administrator/index.php?option=com_installer&view=manage"


      As the error points out, it's a PostgreSQL database connection error.



      In my research, I found that 502 Bad Gateway is usually the result of an incorrectly set configuration file. This is what leads me to think that when something errors out in Joomla, the error isn't handled properly and display the 502 error page.



      What I need to know is: why does the site error out as a 502 Bag Gateway error in NGINX + PHP-FPM when the DB connectivity error occurs? Is this an incorrect configuration in NGINX and/or PHP-FPM or is this how this usually handles errors?



      Image of how Joomla w/apache handles the same error:



      Joomla w/apache postgres connection error



      Note: I've used the Joomla configuration from http://docs.joomla.org/Nginx










      share|improve this question
















      We have a VPS with some PHP websites hosted on our Ubuntu 12.04 LTS servers using NGINX. In a Joomla 3 site, when uninstalling an extension that errors out, the page shows an NGINX error page with a 502 Bad Gateway rather than showing the error message within Joomla like it does in Apache.



      The error log message produces an obvious error as to why the site broke and easy to fix from the extension itself (db connectivity error from PostgreSQL).



      2014/05/06 16:26:12 [error] 17702#0: *26 upstream sent invalid status "0 Error connecting to PGSQL database." while reading response header from upstream, client: xx.xx.xxx.xx, server: sub.example.com, request: "POST /administrator/index.php?option=com_installer&view=manage HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "sub.example.com", referrer: "http://sub.example.com/administrator/index.php?option=com_installer&view=manage"


      As the error points out, it's a PostgreSQL database connection error.



      In my research, I found that 502 Bad Gateway is usually the result of an incorrectly set configuration file. This is what leads me to think that when something errors out in Joomla, the error isn't handled properly and display the 502 error page.



      What I need to know is: why does the site error out as a 502 Bag Gateway error in NGINX + PHP-FPM when the DB connectivity error occurs? Is this an incorrect configuration in NGINX and/or PHP-FPM or is this how this usually handles errors?



      Image of how Joomla w/apache handles the same error:



      Joomla w/apache postgres connection error



      Note: I've used the Joomla configuration from http://docs.joomla.org/Nginx







      nginx postgresql ubuntu-12.04 php-fpm fastcgi






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 6 '14 at 22:21







      RNickMcCandless

















      asked May 6 '14 at 17:03









      RNickMcCandlessRNickMcCandless

      1139




      1139





      bumped to the homepage by Community 4 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 4 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          It's probably related to an invalid status header I had the same issue when an exception is thrown without a http status code as exception code it will fail:
          Hopefully it's merged soon ;) you can patch it manually for the time being: https://github.com/joomla/joomla-cms/compare/staging...Mech7:fix-nginx-status?expand=1






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "2"
            };
            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%2fserverfault.com%2fquestions%2f593447%2fjoomla-extension-uninstall-causes-502-bad-gateway%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














            It's probably related to an invalid status header I had the same issue when an exception is thrown without a http status code as exception code it will fail:
            Hopefully it's merged soon ;) you can patch it manually for the time being: https://github.com/joomla/joomla-cms/compare/staging...Mech7:fix-nginx-status?expand=1






            share|improve this answer




























              0














              It's probably related to an invalid status header I had the same issue when an exception is thrown without a http status code as exception code it will fail:
              Hopefully it's merged soon ;) you can patch it manually for the time being: https://github.com/joomla/joomla-cms/compare/staging...Mech7:fix-nginx-status?expand=1






              share|improve this answer


























                0












                0








                0







                It's probably related to an invalid status header I had the same issue when an exception is thrown without a http status code as exception code it will fail:
                Hopefully it's merged soon ;) you can patch it manually for the time being: https://github.com/joomla/joomla-cms/compare/staging...Mech7:fix-nginx-status?expand=1






                share|improve this answer













                It's probably related to an invalid status header I had the same issue when an exception is thrown without a http status code as exception code it will fail:
                Hopefully it's merged soon ;) you can patch it manually for the time being: https://github.com/joomla/joomla-cms/compare/staging...Mech7:fix-nginx-status?expand=1







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 9 '15 at 10:51









                user42816user42816

                1113




                1113






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Server Fault!


                    • 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%2fserverfault.com%2fquestions%2f593447%2fjoomla-extension-uninstall-causes-502-bad-gateway%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

                    117736 Шеррод Примітки | Див. також | Посилання | Навігаційне...

                    As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

                    Маріан Котлеба Зміст Життєпис | Політичні погляди |...