Web Server: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→PM2) |
||
Line 3: | Line 3: | ||
PM2 serves the NPM process. Upon restarting, you will to restart PM2 in <code>/volume1/wreckroom.nyc/wreckroom</code> | PM2 serves the NPM process. Upon restarting, you will to restart PM2 in <code>/volume1/wreckroom.nyc/wreckroom</code> | ||
If you are having issues with '''PM2''' process manager serving the NextJs app (when <code>sudo npm run start</code> works fine), run: <code>sudo pm2 delete all</code>. | If you are having issues with '''PM2''' process manager serving the NextJs app (when <code>sudo npm run start</code> works fine), run: <code>sudo pm2 delete all</code>. This will end all processes. | ||
This will end all processes | |||
Then, run <code>sudo pm2 start npm -- start</code> and that should cause '''PM2''' to serve correctly. | |||
===Certificates=== | ===Certificates=== | ||
If you make changes to a Certificate's FQDN, in addition to migrating the certificate, you ''must'' go to Control Panel / Login Portal / Advanced / Reverse Proxy. The hostname must be changed there for everything to work properly! This took half a day to figure out last time, hope it saves you some time in the future :) | If you make changes to a Certificate's FQDN, in addition to migrating the certificate, you ''must'' go to Control Panel / Login Portal / Advanced / Reverse Proxy. The hostname must be changed there for everything to work properly! This took half a day to figure out last time, hope it saves you some time in the future :) |
Revision as of 22:07, 29 December 2023
PM2
PM2 serves the NPM process. Upon restarting, you will to restart PM2 in /volume1/wreckroom.nyc/wreckroom
If you are having issues with PM2 process manager serving the NextJs app (when sudo npm run start
works fine), run: sudo pm2 delete all
. This will end all processes.
Then, run sudo pm2 start npm -- start
and that should cause PM2 to serve correctly.
Certificates
If you make changes to a Certificate's FQDN, in addition to migrating the certificate, you must go to Control Panel / Login Portal / Advanced / Reverse Proxy. The hostname must be changed there for everything to work properly! This took half a day to figure out last time, hope it saves you some time in the future :)