nginx erreur it didn't open












7















please nginx in my server did start please follow me



root@s45-****:/home/arabico# nmap 45.****

PORT STATE SERVICE
22/tcp open ssh
5/tcp open smtp
80/tcp open http

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
root@s45-****:/home/arabico# sudo service apache2 stop
* Stopping web server apache2 *
root@s45-****:/home/arabico# nmap 45.****

Starting Nmap 6.40 ( http://nmap.org ) at 2015-06-05 19:33 MST

PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
root@s45-***:/home/arabico# sudo service nginx restart
* Restarting nginx nginx
[fail]


root@s45-***:/home/arabico# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: configuration file /etc/nginx/nginx.conf test failed

root@s45***:/home/arabico# sudo nginx
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)


how to let it start please










share|improve this question

























  • What exactly are you asking?

    – spacegeek224
    Jun 6 '15 at 3:05











  • it didn'y work how to let it start

    – user14576
    Jun 6 '15 at 3:19
















7















please nginx in my server did start please follow me



root@s45-****:/home/arabico# nmap 45.****

PORT STATE SERVICE
22/tcp open ssh
5/tcp open smtp
80/tcp open http

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
root@s45-****:/home/arabico# sudo service apache2 stop
* Stopping web server apache2 *
root@s45-****:/home/arabico# nmap 45.****

Starting Nmap 6.40 ( http://nmap.org ) at 2015-06-05 19:33 MST

PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
root@s45-***:/home/arabico# sudo service nginx restart
* Restarting nginx nginx
[fail]


root@s45-***:/home/arabico# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: configuration file /etc/nginx/nginx.conf test failed

root@s45***:/home/arabico# sudo nginx
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)


how to let it start please










share|improve this question

























  • What exactly are you asking?

    – spacegeek224
    Jun 6 '15 at 3:05











  • it didn'y work how to let it start

    – user14576
    Jun 6 '15 at 3:19














7












7








7


1






please nginx in my server did start please follow me



root@s45-****:/home/arabico# nmap 45.****

PORT STATE SERVICE
22/tcp open ssh
5/tcp open smtp
80/tcp open http

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
root@s45-****:/home/arabico# sudo service apache2 stop
* Stopping web server apache2 *
root@s45-****:/home/arabico# nmap 45.****

Starting Nmap 6.40 ( http://nmap.org ) at 2015-06-05 19:33 MST

PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
root@s45-***:/home/arabico# sudo service nginx restart
* Restarting nginx nginx
[fail]


root@s45-***:/home/arabico# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: configuration file /etc/nginx/nginx.conf test failed

root@s45***:/home/arabico# sudo nginx
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)


how to let it start please










share|improve this question
















please nginx in my server did start please follow me



root@s45-****:/home/arabico# nmap 45.****

PORT STATE SERVICE
22/tcp open ssh
5/tcp open smtp
80/tcp open http

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
root@s45-****:/home/arabico# sudo service apache2 stop
* Stopping web server apache2 *
root@s45-****:/home/arabico# nmap 45.****

Starting Nmap 6.40 ( http://nmap.org ) at 2015-06-05 19:33 MST

PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
root@s45-***:/home/arabico# sudo service nginx restart
* Restarting nginx nginx
[fail]


root@s45-***:/home/arabico# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: configuration file /etc/nginx/nginx.conf test failed

root@s45***:/home/arabico# sudo nginx
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)


how to let it start please







networking server ssh apache2 nginx






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 6 '15 at 3:55







user14576

















asked Jun 6 '15 at 2:42









user14576user14576

101118




101118













  • What exactly are you asking?

    – spacegeek224
    Jun 6 '15 at 3:05











  • it didn'y work how to let it start

    – user14576
    Jun 6 '15 at 3:19



















  • What exactly are you asking?

    – spacegeek224
    Jun 6 '15 at 3:05











  • it didn'y work how to let it start

    – user14576
    Jun 6 '15 at 3:19

















What exactly are you asking?

– spacegeek224
Jun 6 '15 at 3:05





What exactly are you asking?

– spacegeek224
Jun 6 '15 at 3:05













it didn'y work how to let it start

– user14576
Jun 6 '15 at 3:19





it didn'y work how to let it start

– user14576
Jun 6 '15 at 3:19










3 Answers
3






active

oldest

votes


















9














nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)


From the error message this seems ipv6 is disabled on your server.
Edit nginx default server configuration and changed it to listen on ipv4 only or enable ipv6.



listen 80 default_server;
# comment to disable ipv6
# listen [::]:80 default_server;





share|improve this answer































    6














    just i deleted this line



    listen [::]:80 default_server ipv6only=on;



    from



    /etc/nginx/sites-available/default
    and it works :D






    share|improve this answer


























    • I did the same and it also works. But can anyone explain why the default config did not work?

      – Loredra L
      Nov 16 '18 at 13:08



















    0














    Thanks for mentioning ipv6.



    In my case, I got a line in nginx conf of



    proxy_pass http://localhost:3028/;


    The problem happened when I disable ipv6 in the kernel config. Reenabling ipv6 can solve the problem, but it is not what I want.



    the solution is delete



    ::1     localhost ip6-localhost ip6-loopback
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters


    in /etc/hosts.



    so the localhost will alway follow the default ipv4 target, which is 127.0.0.1.



    Just deleting the ::1 line could be enough. Since ipv6 is totally disabled, I would delete all of them.



    Changing the localhost in nginx config to 127.0.0.1 may solve this problem as well.






    share|improve this answer

























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      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%2faskubuntu.com%2fquestions%2f632874%2fnginx-erreur-it-didnt-open%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      9














      nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)


      From the error message this seems ipv6 is disabled on your server.
      Edit nginx default server configuration and changed it to listen on ipv4 only or enable ipv6.



      listen 80 default_server;
      # comment to disable ipv6
      # listen [::]:80 default_server;





      share|improve this answer




























        9














        nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)


        From the error message this seems ipv6 is disabled on your server.
        Edit nginx default server configuration and changed it to listen on ipv4 only or enable ipv6.



        listen 80 default_server;
        # comment to disable ipv6
        # listen [::]:80 default_server;





        share|improve this answer


























          9












          9








          9







          nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)


          From the error message this seems ipv6 is disabled on your server.
          Edit nginx default server configuration and changed it to listen on ipv4 only or enable ipv6.



          listen 80 default_server;
          # comment to disable ipv6
          # listen [::]:80 default_server;





          share|improve this answer













          nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)


          From the error message this seems ipv6 is disabled on your server.
          Edit nginx default server configuration and changed it to listen on ipv4 only or enable ipv6.



          listen 80 default_server;
          # comment to disable ipv6
          # listen [::]:80 default_server;






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jun 6 '15 at 4:23









          moonstruckmoonstruck

          30127




          30127

























              6














              just i deleted this line



              listen [::]:80 default_server ipv6only=on;



              from



              /etc/nginx/sites-available/default
              and it works :D






              share|improve this answer


























              • I did the same and it also works. But can anyone explain why the default config did not work?

                – Loredra L
                Nov 16 '18 at 13:08
















              6














              just i deleted this line



              listen [::]:80 default_server ipv6only=on;



              from



              /etc/nginx/sites-available/default
              and it works :D






              share|improve this answer


























              • I did the same and it also works. But can anyone explain why the default config did not work?

                – Loredra L
                Nov 16 '18 at 13:08














              6












              6








              6







              just i deleted this line



              listen [::]:80 default_server ipv6only=on;



              from



              /etc/nginx/sites-available/default
              and it works :D






              share|improve this answer















              just i deleted this line



              listen [::]:80 default_server ipv6only=on;



              from



              /etc/nginx/sites-available/default
              and it works :D







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jun 6 '15 at 14:34

























              answered Jun 6 '15 at 12:57









              user14576user14576

              101118




              101118













              • I did the same and it also works. But can anyone explain why the default config did not work?

                – Loredra L
                Nov 16 '18 at 13:08



















              • I did the same and it also works. But can anyone explain why the default config did not work?

                – Loredra L
                Nov 16 '18 at 13:08

















              I did the same and it also works. But can anyone explain why the default config did not work?

              – Loredra L
              Nov 16 '18 at 13:08





              I did the same and it also works. But can anyone explain why the default config did not work?

              – Loredra L
              Nov 16 '18 at 13:08











              0














              Thanks for mentioning ipv6.



              In my case, I got a line in nginx conf of



              proxy_pass http://localhost:3028/;


              The problem happened when I disable ipv6 in the kernel config. Reenabling ipv6 can solve the problem, but it is not what I want.



              the solution is delete



              ::1     localhost ip6-localhost ip6-loopback
              ff02::1 ip6-allnodes
              ff02::2 ip6-allrouters


              in /etc/hosts.



              so the localhost will alway follow the default ipv4 target, which is 127.0.0.1.



              Just deleting the ::1 line could be enough. Since ipv6 is totally disabled, I would delete all of them.



              Changing the localhost in nginx config to 127.0.0.1 may solve this problem as well.






              share|improve this answer






























                0














                Thanks for mentioning ipv6.



                In my case, I got a line in nginx conf of



                proxy_pass http://localhost:3028/;


                The problem happened when I disable ipv6 in the kernel config. Reenabling ipv6 can solve the problem, but it is not what I want.



                the solution is delete



                ::1     localhost ip6-localhost ip6-loopback
                ff02::1 ip6-allnodes
                ff02::2 ip6-allrouters


                in /etc/hosts.



                so the localhost will alway follow the default ipv4 target, which is 127.0.0.1.



                Just deleting the ::1 line could be enough. Since ipv6 is totally disabled, I would delete all of them.



                Changing the localhost in nginx config to 127.0.0.1 may solve this problem as well.






                share|improve this answer




























                  0












                  0








                  0







                  Thanks for mentioning ipv6.



                  In my case, I got a line in nginx conf of



                  proxy_pass http://localhost:3028/;


                  The problem happened when I disable ipv6 in the kernel config. Reenabling ipv6 can solve the problem, but it is not what I want.



                  the solution is delete



                  ::1     localhost ip6-localhost ip6-loopback
                  ff02::1 ip6-allnodes
                  ff02::2 ip6-allrouters


                  in /etc/hosts.



                  so the localhost will alway follow the default ipv4 target, which is 127.0.0.1.



                  Just deleting the ::1 line could be enough. Since ipv6 is totally disabled, I would delete all of them.



                  Changing the localhost in nginx config to 127.0.0.1 may solve this problem as well.






                  share|improve this answer















                  Thanks for mentioning ipv6.



                  In my case, I got a line in nginx conf of



                  proxy_pass http://localhost:3028/;


                  The problem happened when I disable ipv6 in the kernel config. Reenabling ipv6 can solve the problem, but it is not what I want.



                  the solution is delete



                  ::1     localhost ip6-localhost ip6-loopback
                  ff02::1 ip6-allnodes
                  ff02::2 ip6-allrouters


                  in /etc/hosts.



                  so the localhost will alway follow the default ipv4 target, which is 127.0.0.1.



                  Just deleting the ::1 line could be enough. Since ipv6 is totally disabled, I would delete all of them.



                  Changing the localhost in nginx config to 127.0.0.1 may solve this problem as well.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 8 mins ago

























                  answered 13 mins ago









                  aGueguaGuegu

                  1011




                  1011






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • 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%2faskubuntu.com%2fquestions%2f632874%2fnginx-erreur-it-didnt-open%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

                      GameSpot

                      日野市

                      Tu-95轟炸機