It looks like you aren’t getting the SSH error now at least. So the errors you are getting can happen if the connection is being lost and it seems that maybe it’s because of how large some of your files are. Do you have very large files somewhere like wp-content? Or is the large size due to the database?
We had an issue like this in the past but that was fixed for everyone a while ago. I’m going to have more tests done on Linux to make sure this isn’t the same issue and have our devs investigate.
Hi Kevin, I have freshly created another env and push the site it works fine and after some changes when I try to push it gives error but only database is pushed. Whats the problem . I will send you the main.log file in message
Hi @PuspaRaj_Subedi, can you please update your DevKinsta version then retry? Your logs show that your were version 2.4.1, can you update to 2.6.0 then try again and share the log?
Even if that doesn’t fix it, we might get better error information when you update.
Also did you ever try a manual migration? Did that work?
Hi yes, @PuspaRaj_Subedi, if you just download and run the installation again, it will only replace the application files. It will not delete your website.
Sorry @PuspaRaj_Subedi, it was a holiday but I am back. So since it’s still the same error but it only occurs with this specific staging, I think the problem is with the files that are currently on that staging environment.
Can you please private message the staging URL to me? I will properly reset it so that there are no files. That might allow the Push to work without this error.