Welcome! Log In Create A New Profile

Advanced

Node.js stopped working on nginx after installing new cert

fbs
September 09, 2023 01:13PM
So this is very strange. We use nginx for our reactJS website as well as proxy_pass to asp pages on another windows box. I recently installed a new cert from digicert, and now I can't get Node.js to work. The proxy pass works fine, and digicert says our cert is correctly installed. But I get a ton of the same errors in the nginx error.log -- basically at Bad Gateway (502) error:

2023/09/09 03:06:34 [error] 4318#0: *57057 connect() failed (111: Connection refused) while connecting to upstream, client: 66.249.79.138, server: www.emergencyuniversity.com, request: "GET /robots.txt HTTP/1.1", upstream: http://127.0.0.1:8080/robots_www.txt, host: www.emergencyuniversity.com

So I did a netstat -tulpn and it shows that port 8080 is not open. We have our QA server that works fine -- it shows that 8080 is open. It shows:

tcp 0 0 :::8080 LISTEN 20210/node So node is running on 8080 there. That's what I want on our production server, and it always worked before I added the new cert. The config files on these 2 servers are basically the same.

How can I get Node running on port 8080? Thanks a lot.
Subject Author Posted

Node.js stopped working on nginx after installing new cert

fbs September 09, 2023 01:13PM

Re: Node.js stopped working on nginx after installing new cert

fbs September 09, 2023 02:36PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 59
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready