I have been playing around with n8n lately, and today I have discovered a very funny thing.
Decided to go with self-hosting option of n8n. I spun up an EC2 instance on AWS (which in turn is racking up the bill rn with its uncontrolled VPC configs that I have never opted for) and set up n8n using docker.
Until last night I have been developing a workflow and had some progress. Today I woke up to AWS alert – instance reachability check failed. For no reason, my EC2 instance became unreachable and everthing just shut down. Then I tried fixing it and came to a point of stopping the instance and starting it again. It assigned a new IP to the instance!!!
FUNNY enough, all my work from previous couple of days has been lost, and I find myself to the initial setup with some sketch workflows on the dashboard being active.
What could be the problem here? Is it n8n? Is it persistent storage failed by n8n? Or is it AWS instance?
Today is 9 Sep, 6.06pm at the time of publication