Hostname/IP doesn't match certificate's altnames | Node & NginxAfter performing apt-get dist-upgrade Perl...

Was it really inappropriate to write a pull request for the company I interviewed with?

Outlet with 3 sets of wires

Does Christianity allow for believing on someone else's behalf?

What do *foreign films* mean for an American?

Having the player face themselves after the mid-game

How many characters using PHB rules does it take to be able to have access to any PHB spell at the start of an adventuring day?

What is Tony Stark injecting into himself in Iron Man 3?

Can the alpha, lambda values of a glmnet object output determine whether ridge or Lasso?

Can one live in the U.S. and not use a credit card?

Gaining more land

I reported the illegal activity of my boss to his boss. My boss found out. Now I am being punished. What should I do?

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

Is a piano played in the same way as a harmonium?

Doesn't allowing a user mode program to access kernel space memory and execute the IN and OUT instructions defeat the purpose of having CPU modes?

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

Does "Until when" sound natural for native speakers?

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

How exactly does an Ethernet collision happen in the cable, since nodes use different circuits for Tx and Rx?

Is it a Cyclops number? "Nobody" knows!

What ability score modifier does a javelin's damage use?

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

Should I take out a loan for a friend to invest on my behalf?

How to resolve: Reviewer #1 says remove section X vs. Reviewer #2 says expand section X

Why is there an extra space when I type "ls" in the Desktop directory?



Hostname/IP doesn't match certificate's altnames | Node & Nginx


After performing apt-get dist-upgrade Perl scripts will no longer ignore invalid SSL certificates on 14.04LetsEncrypt - “Can't connect to the client for DV”Ubuntu Server 16.04 Letsencrypt SSL Website Configuration FileApache2 - SSH - LetsEncrypt SSL - Certbot - Proxy - Manual Setup: How to achieve this?Ubuntu 16.04, Apache, certbot, how to?Apache2: SSL not workingProblem installing certificates with letsencryptNginx failing to redirect to docker containerCA root install issue on Ubuntu 16.04 LTS Servernginx : websocket failed to connect













0















Among several subdomains, I have node servers running on different ports. I have a subdomain called alexa-service.healform.de, which runs a node server that should execute some functions and requests. One function of this is a GET query of data provided by another subdomain, hosted on my server too - oauth2.healform.de. If I let this function run, I get the following error message in the terminal and that is also the curious part:



Error message:



Hostname / IP does not match certificate's altnames: "Host: localhost." Is not in the cert's altnames: DNS: ampinbaunatal.de, DNS: www.ampinbaunatal.de "


When I saw that, I thought I was asking AskUbuntu rather than Stack. The domains ampinbaunatal.de and www.ampinbaunatal.de are also hosted on my server and also have a valid SSL certificate issued by Let's Encrypt. But why does the function of oauth2.healform.de differ on ampinbaunatal.de? The domains have nothing to do with the function.



When I call the endpoint of the data, the function should retrieve, with Postman, I get a correct response. But as soon as I run the API query in localhost via the node server (I'm on Ubuntu Server 18.04 btw.), it somehow switches to the other domain and I get this error message.



Does anyone have an idea what's wrong with the certificates? Both have valid SSL certificates. And why does he accidentally switch to the ampinbaunatal.de domain?





Nginx config for both servers:



server {
server_name oauth2.healform.de;
location / {
proxy_pass http://localhost:51001;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}

listen 443 ssl; # managed by Certbot
ssl_certificate /path/to/fullchain.pem; # managed by Certbot
ssl_certificate_key /path/to/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

server {
server_name alexa-services.healform.de;
location / {
proxy_pass http://localhost:51002;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}

listen 443 ssl; # managed by Certbot
ssl_certificate /path/to/fullchain.pem; # managed by Certbot
ssl_certificate_key /path/to/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}








share



























    0















    Among several subdomains, I have node servers running on different ports. I have a subdomain called alexa-service.healform.de, which runs a node server that should execute some functions and requests. One function of this is a GET query of data provided by another subdomain, hosted on my server too - oauth2.healform.de. If I let this function run, I get the following error message in the terminal and that is also the curious part:



    Error message:



    Hostname / IP does not match certificate's altnames: "Host: localhost." Is not in the cert's altnames: DNS: ampinbaunatal.de, DNS: www.ampinbaunatal.de "


    When I saw that, I thought I was asking AskUbuntu rather than Stack. The domains ampinbaunatal.de and www.ampinbaunatal.de are also hosted on my server and also have a valid SSL certificate issued by Let's Encrypt. But why does the function of oauth2.healform.de differ on ampinbaunatal.de? The domains have nothing to do with the function.



    When I call the endpoint of the data, the function should retrieve, with Postman, I get a correct response. But as soon as I run the API query in localhost via the node server (I'm on Ubuntu Server 18.04 btw.), it somehow switches to the other domain and I get this error message.



    Does anyone have an idea what's wrong with the certificates? Both have valid SSL certificates. And why does he accidentally switch to the ampinbaunatal.de domain?





    Nginx config for both servers:



    server {
    server_name oauth2.healform.de;
    location / {
    proxy_pass http://localhost:51001;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /path/to/fullchain.pem; # managed by Certbot
    ssl_certificate_key /path/to/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
    }

    server {
    server_name alexa-services.healform.de;
    location / {
    proxy_pass http://localhost:51002;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /path/to/fullchain.pem; # managed by Certbot
    ssl_certificate_key /path/to/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
    }








    share

























      0












      0








      0








      Among several subdomains, I have node servers running on different ports. I have a subdomain called alexa-service.healform.de, which runs a node server that should execute some functions and requests. One function of this is a GET query of data provided by another subdomain, hosted on my server too - oauth2.healform.de. If I let this function run, I get the following error message in the terminal and that is also the curious part:



      Error message:



      Hostname / IP does not match certificate's altnames: "Host: localhost." Is not in the cert's altnames: DNS: ampinbaunatal.de, DNS: www.ampinbaunatal.de "


      When I saw that, I thought I was asking AskUbuntu rather than Stack. The domains ampinbaunatal.de and www.ampinbaunatal.de are also hosted on my server and also have a valid SSL certificate issued by Let's Encrypt. But why does the function of oauth2.healform.de differ on ampinbaunatal.de? The domains have nothing to do with the function.



      When I call the endpoint of the data, the function should retrieve, with Postman, I get a correct response. But as soon as I run the API query in localhost via the node server (I'm on Ubuntu Server 18.04 btw.), it somehow switches to the other domain and I get this error message.



      Does anyone have an idea what's wrong with the certificates? Both have valid SSL certificates. And why does he accidentally switch to the ampinbaunatal.de domain?





      Nginx config for both servers:



      server {
      server_name oauth2.healform.de;
      location / {
      proxy_pass http://localhost:51001;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection 'upgrade';
      proxy_set_header Host $host;
      proxy_cache_bypass $http_upgrade;
      }

      listen 443 ssl; # managed by Certbot
      ssl_certificate /path/to/fullchain.pem; # managed by Certbot
      ssl_certificate_key /path/to/privkey.pem; # managed by Certbot
      include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
      ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
      }

      server {
      server_name alexa-services.healform.de;
      location / {
      proxy_pass http://localhost:51002;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection 'upgrade';
      proxy_set_header Host $host;
      proxy_cache_bypass $http_upgrade;
      }

      listen 443 ssl; # managed by Certbot
      ssl_certificate /path/to/fullchain.pem; # managed by Certbot
      ssl_certificate_key /path/to/privkey.pem; # managed by Certbot
      include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
      ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
      }








      share














      Among several subdomains, I have node servers running on different ports. I have a subdomain called alexa-service.healform.de, which runs a node server that should execute some functions and requests. One function of this is a GET query of data provided by another subdomain, hosted on my server too - oauth2.healform.de. If I let this function run, I get the following error message in the terminal and that is also the curious part:



      Error message:



      Hostname / IP does not match certificate's altnames: "Host: localhost." Is not in the cert's altnames: DNS: ampinbaunatal.de, DNS: www.ampinbaunatal.de "


      When I saw that, I thought I was asking AskUbuntu rather than Stack. The domains ampinbaunatal.de and www.ampinbaunatal.de are also hosted on my server and also have a valid SSL certificate issued by Let's Encrypt. But why does the function of oauth2.healform.de differ on ampinbaunatal.de? The domains have nothing to do with the function.



      When I call the endpoint of the data, the function should retrieve, with Postman, I get a correct response. But as soon as I run the API query in localhost via the node server (I'm on Ubuntu Server 18.04 btw.), it somehow switches to the other domain and I get this error message.



      Does anyone have an idea what's wrong with the certificates? Both have valid SSL certificates. And why does he accidentally switch to the ampinbaunatal.de domain?





      Nginx config for both servers:



      server {
      server_name oauth2.healform.de;
      location / {
      proxy_pass http://localhost:51001;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection 'upgrade';
      proxy_set_header Host $host;
      proxy_cache_bypass $http_upgrade;
      }

      listen 443 ssl; # managed by Certbot
      ssl_certificate /path/to/fullchain.pem; # managed by Certbot
      ssl_certificate_key /path/to/privkey.pem; # managed by Certbot
      include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
      ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
      }

      server {
      server_name alexa-services.healform.de;
      location / {
      proxy_pass http://localhost:51002;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection 'upgrade';
      proxy_set_header Host $host;
      proxy_cache_bypass $http_upgrade;
      }

      listen 443 ssl; # managed by Certbot
      ssl_certificate /path/to/fullchain.pem; # managed by Certbot
      ssl_certificate_key /path/to/privkey.pem; # managed by Certbot
      include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
      ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
      }






      networking server nginx ssl certificates





      share












      share










      share



      share










      asked 1 min ago









      dmnktoedmnktoe

      12




      12






















          0






          active

          oldest

          votes











          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%2f1124645%2fhostname-ip-doesnt-match-certificates-altnames-node-nginx%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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%2f1124645%2fhostname-ip-doesnt-match-certificates-altnames-node-nginx%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

          Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

          Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

          Should I use Docker or LXD?How to cache (more) data on SSD/RAM to avoid spin up?Unable to get Windows File...