Basic nginx proxy_pass fails with HTTP 500 Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!How to make nginx reverse proxy let 503 error pages pass through to client?Blank Page: wordpress on nginx+php-fpmTrouble with nginx and serving from multiple directories under the same domainnginx returns error 500 when doing nagios checkNginx gives 504 Gateway Time-out once moved to livenginx load balancer rewrite to listen portNginx proxy_pass confignginx rewrite throw 404 with last and breaknginx configuration troubleUniversal HTTPS to HTTP reverse proxy using nginx

Did Deadpool rescue all of the X-Force?

Why wasn't DOSKEY integrated with COMMAND.COM?

Why do we need to use the builder design pattern when we can do the same thing with setters?

Why weren't discrete x86 CPUs ever used in game hardware?

Drawing without replacement: why is the order of draw irrelevant?

Is there any word for a place full of confusion?

Central Vacuuming: Is it worth it, and how does it compare to normal vacuuming?

Has negative voting ever been officially implemented in elections, or seriously proposed, or even studied?

If Windows 7 doesn't support WSL, then what does Linux subsystem option mean?

Converted a Scalar function to a TVF function for parallel execution-Still running in Serial mode

What is the difference between globalisation and imperialism?

Hangman Game with C++

Disembodied hand growing fangs

Can a new player join a group only when a new campaign starts?

What is "gratricide"?

Find 108 by using 3,4,6

How to tell that you are a giant?

An adverb for when you're not exaggerating

How come Sam didn't become Lord of Horn Hill?

Question about debouncing - delay of state change

Why is Nikon 1.4g better when Nikon 1.8g is sharper?

How often does castling occur in grandmaster games?

Do any jurisdictions seriously consider reclassifying social media websites as publishers?

How can I reduce the gap between left and right of cdot with a macro?



Basic nginx proxy_pass fails with HTTP 500



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!How to make nginx reverse proxy let 503 error pages pass through to client?Blank Page: wordpress on nginx+php-fpmTrouble with nginx and serving from multiple directories under the same domainnginx returns error 500 when doing nagios checkNginx gives 504 Gateway Time-out once moved to livenginx load balancer rewrite to listen portNginx proxy_pass confignginx rewrite throw 404 with last and breaknginx configuration troubleUniversal HTTPS to HTTP reverse proxy using nginx



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















I have an extremely minimal configuration that I believe should reverse proxy what I see on example.com:1234 to example.com[:80].



error_log /var/log/nginx/error.log info;

events


http
server
listen 80;
server_name example.com;

location /
proxy_pass http://example.com:1234;
proxy_redirect default;





However, navigating to port 80 results in an internal server error 500 - while navigating to port 1234 renders the expected output.



The log contains only "signal process started" entries.



What have I done wrong, or missed? How can I log a better (any!) description of the server error; I anticipate this is not the last time that would be useful.










share|improve this question




























    1















    I have an extremely minimal configuration that I believe should reverse proxy what I see on example.com:1234 to example.com[:80].



    error_log /var/log/nginx/error.log info;

    events


    http
    server
    listen 80;
    server_name example.com;

    location /
    proxy_pass http://example.com:1234;
    proxy_redirect default;





    However, navigating to port 80 results in an internal server error 500 - while navigating to port 1234 renders the expected output.



    The log contains only "signal process started" entries.



    What have I done wrong, or missed? How can I log a better (any!) description of the server error; I anticipate this is not the last time that would be useful.










    share|improve this question
























      1












      1








      1








      I have an extremely minimal configuration that I believe should reverse proxy what I see on example.com:1234 to example.com[:80].



      error_log /var/log/nginx/error.log info;

      events


      http
      server
      listen 80;
      server_name example.com;

      location /
      proxy_pass http://example.com:1234;
      proxy_redirect default;





      However, navigating to port 80 results in an internal server error 500 - while navigating to port 1234 renders the expected output.



      The log contains only "signal process started" entries.



      What have I done wrong, or missed? How can I log a better (any!) description of the server error; I anticipate this is not the last time that would be useful.










      share|improve this question














      I have an extremely minimal configuration that I believe should reverse proxy what I see on example.com:1234 to example.com[:80].



      error_log /var/log/nginx/error.log info;

      events


      http
      server
      listen 80;
      server_name example.com;

      location /
      proxy_pass http://example.com:1234;
      proxy_redirect default;





      However, navigating to port 80 results in an internal server error 500 - while navigating to port 1234 renders the expected output.



      The log contains only "signal process started" entries.



      What have I done wrong, or missed? How can I log a better (any!) description of the server error; I anticipate this is not the last time that would be useful.







      nginx






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 23 '15 at 1:16









      OJFordOJFord

      11614




      11614




















          2 Answers
          2






          active

          oldest

          votes


















          1














          If your backend is on the same host try using proxy_pass http://127.0.0.1:1234; instead proxy_pass http://example.com:1234;. NGINX invokes an internal name resolution logic before using DNS, since your server_name is the same as hostname in proxy_pass directive, this may be source of your problem.






          share|improve this answer
































            0














            Just remove proxy_redirect and send another request to the NGINX. If there is still Internal Server error investigate the log file.


            Also, It will not harm if you check the backend (proxy_pass http://example.com) with curl from your server to getting sure your backend is healthy.






            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%2f738225%2fbasic-nginx-proxy-pass-fails-with-http-500%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              1














              If your backend is on the same host try using proxy_pass http://127.0.0.1:1234; instead proxy_pass http://example.com:1234;. NGINX invokes an internal name resolution logic before using DNS, since your server_name is the same as hostname in proxy_pass directive, this may be source of your problem.






              share|improve this answer





























                1














                If your backend is on the same host try using proxy_pass http://127.0.0.1:1234; instead proxy_pass http://example.com:1234;. NGINX invokes an internal name resolution logic before using DNS, since your server_name is the same as hostname in proxy_pass directive, this may be source of your problem.






                share|improve this answer



























                  1












                  1








                  1







                  If your backend is on the same host try using proxy_pass http://127.0.0.1:1234; instead proxy_pass http://example.com:1234;. NGINX invokes an internal name resolution logic before using DNS, since your server_name is the same as hostname in proxy_pass directive, this may be source of your problem.






                  share|improve this answer















                  If your backend is on the same host try using proxy_pass http://127.0.0.1:1234; instead proxy_pass http://example.com:1234;. NGINX invokes an internal name resolution logic before using DNS, since your server_name is the same as hostname in proxy_pass directive, this may be source of your problem.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 2 days ago

























                  answered Nov 23 '15 at 5:00









                  dtoubelisdtoubelis

                  3,90612028




                  3,90612028























                      0














                      Just remove proxy_redirect and send another request to the NGINX. If there is still Internal Server error investigate the log file.


                      Also, It will not harm if you check the backend (proxy_pass http://example.com) with curl from your server to getting sure your backend is healthy.






                      share|improve this answer



























                        0














                        Just remove proxy_redirect and send another request to the NGINX. If there is still Internal Server error investigate the log file.


                        Also, It will not harm if you check the backend (proxy_pass http://example.com) with curl from your server to getting sure your backend is healthy.






                        share|improve this answer

























                          0












                          0








                          0







                          Just remove proxy_redirect and send another request to the NGINX. If there is still Internal Server error investigate the log file.


                          Also, It will not harm if you check the backend (proxy_pass http://example.com) with curl from your server to getting sure your backend is healthy.






                          share|improve this answer













                          Just remove proxy_redirect and send another request to the NGINX. If there is still Internal Server error investigate the log file.


                          Also, It will not harm if you check the backend (proxy_pass http://example.com) with curl from your server to getting sure your backend is healthy.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Oct 9 '18 at 12:36









                          Daniel GordiDaniel Gordi

                          846




                          846



























                              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%2f738225%2fbasic-nginx-proxy-pass-fails-with-http-500%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

                              Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

                              Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

                              What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company