Clone : Source project 68c8bc57d5f4fb1e8d4ba688 → region server-6a2954fa15fc55f468146890
Clone : Source project 68c8bc57d5f4fb1e8d4ba688 → region server-6a2954fa15fc55f468146890
Hello, we have identified the cause of the cloning failure and have assisted you in completing the project migration.
There were two reasons for the failure: First, the PostgreSQL database in the original project had been stopped since 6/9. During the cloning process, the system needs to connect to the database to export content, which is why it failed at this step every time (your n8n was also crashing and being suspended because it couldn't connect to the database). Second, the 2GB RAM machine was insufficient to execute the data restoration process during the cloning; the restoration could not be scheduled and eventually timed out.
We have manually migrated the complete data for both n8n and PostgreSQL to your server. In the new project 'decreprip-urous', both services are now operating normally:
Reminder: Running both n8n and PostgreSQL on a 2C 2GB machine will be memory-intensive. While it is fine in an idle state, it may crash if you have many workflows or high traffic. We recommend upgrading the server to 4GB or more if needed.
Please log in to verify that your workflows and credentials are normal, and let us know if you have any further questions.
Hello,
After testing, the functionality is working correctly. Thank you for your assistance.
Additionally, I would like to ask how to properly upgrade the n8n version. Is there any tutorial documentation or SOP available?
Please guide me further.
Thank you.