Created attachment 1240936 [details] Data from bug reporting tool. Description of problem: When I launch Pterodactyl Daemon, Node.js runs until begins listening to port 8080 for connections from Pterodactyl Panel. After it begins listening, it unexpectedly terminates. Version-Release number of selected component (if applicable): 6.9.1-4.el7 How reproducible: 100% Steps to Reproduce: 1. Install Pterodactyl Panel -- https://docs.pterodactyl.io/docs/installing 2. Install Pterodactyl Daemon -- https://daemon.pterodactyl.io/docs/install-dependencies 3. Start Pterodactyl Daemon Actual results: Node.js terminates. Expected results: Node.js is expected to continue running Pterodactyl Daemon to listen for incoming connections from Pterodactyl Panel so that it can handle installing/managing game servers. Additional info: Server is rented from Limestone Networks, and uses Limestone's own mirrors of CentOS and EPEL repositories. Only third-party repositories used (other than Limestone's mirrored EPEL) are remi-safe and remi-php71 for PHP 7.1, NGINX mainline, and Vivaldi. I posted about this on the Pterodactyl Panel forums as well, just in case it's not a bug in the EPEL Node.js package: https://forums.pterodactyl.io/d/14-node-js-crashing-centos-7
The developers of Pterodactyl Panel have let me know that this appears to be related to an SSL issue with the version of Node.js from the EPEL repo. There is a bug report on their tracker where another user encountered the issue, and it was resolved by replacing EPEL's Node.js with the official version: https://github.com/Pterodactyl/Panel/issues/196
See https://github.com/nodejs/node/issues/9551#issuecomment-265574463 for a workaround.https://github.com/nodejs/node/issues/9551#issuecomment-265574463 *** This bug has been marked as a duplicate of bug 1394948 ***