Some of you are running n8n as a service using the PM2 tool as per Run n8n as a Service with PM2. When a new version of n8n is released, it is important to properly manage the n8n service with PM2 prior to upgrading.
The upgrade process follows these steps:
- Stop the n8n service with PM2
- Upgrade n8n
- Restart the n8n service
- Check that n8n has upgraded
Most of these tasks are completed via the CLI.
As an example, this is how my upgrade process looked:
pm2 stop n8n npm install -g [email protected] pm2 restart n8n
Once the service restarts, you can go back into the n8n webUI and click on the ? and then About n8n:
This should show that you now have the latest version of n8n installed and running (which is 0.78.0 as of the writing of this post. You results may be different.):
If you do not get these results, here are a few tips to finding the problem.
n8n Version is Still Old Version
After following the process, the version of n8n shown in the webUI is still the old version
- Make sure that the PM2 service has restarted the n8n service. If in doubt, reboot the server.
- Confirm that there were no errors during the n8n upgrade process
- Clear your web browser cache
WebUI Not Working
When you go back into the webUI, it is unavailable
- Wait for a few minutes as it can sometimes take a bit for the webUI to come back online after a restart, depending on how much power your host server has
- Make sure that the pm2 service has restarted n8n properly by issuing a
PM2 listcommand. Your n8n service should come up as
online. If not attempt to restart it again. If that fails, try to reboot the server.