Q: Date/Time this occurred (Provide your time zone also) A: 18.1.2021 21:31 GMT+2
Q: DevKinsta Version A: Version 1.0.1 (126.96.36.1993)
Q: OS Version A: Mac OS 11.1 (20C69)
Q: VirtualBox Version A: ???
Q: Were any error codes or messages observed? If so, what were they? A: not
Q: Detailed Description of the Problem A:
when importing a website from kinsta, site size is much bigger then expected.
My site should be ~3 GB but I’m downloading ~11GB for some reason.
[2021-01-18 21:03:07.848] [info] Using devkinsta-updates for auto update
[2021-01-18 21:10:13.245] [info] Checking for update
[2021-01-18 21:10:13.251] [info] Generated new staging user ID: 284cba33-51f1-5034-afc6-6b6b7d54e07d
[2021-01-18 21:10:14.054] [info] Update for version 1.0.1 is not available (latest version: 1.0.1, downgrade is disallowed).
Q: Date/Time this occurred (Provide your time zone also) A: 09.04.2021 16:30 UTC+2
Q: DevKinsta Version A: 1.0.3 (188.8.131.523)
Q: OS Version A: macOS 11.2.3 (20D91)
Q: Docker Desktop Version A: 3.3.0 (62632)
Q: Were any error codes or messages observed? If so, what were they? A: DK0025 (Only when force closing DevKinsta while creating new site and DK0025 shows when I open up DevKinsta again. When I click “Retry” the error message goes away and it continues the download)
Q: Detailed Description of the Problem A: While creating a new site from site on MyKinsta the creation process freezes while downloading the site. The site shows as 2.9GB in the MyKinsta Dashboard, but shows as 92.9GB in DevKinsta. When reaching 2.89GB in the download process it just keeps spinning/loading and nothing more happens. (arround 41%). This is one specific site (tried downloading both live and staging), other sites from our account works fine and shows the correct size when downloading.
I’m uploading my local site to staging, and the upload says it’s going to be 47.9 GB, which is roughly 6 times the size of my production site and more on its own than our available disk space on the server with our plan. So I have a couple of questions:
Is this accurate?
If it is, how do I kill the upload safely? I don’t want to get stuck paying for overages using this push feature, but there doesn’t seem to be any way to stop the upload once it’s in progress.
Thanks for the update @gfitech . It appears related to another bug we had with downloads. If this is indeed the case, while the numbers are incorrect, it will only upload the actual amount (the 7.7GB) and not the number that was shown.
I’ve gone ahead and moved this conversation over to our bug reporting category for our developers to review. I’m sorry again for the issues here!
Hello! I’ve merged together a few threads here that were related. Apologies for the confusion! Just letting everyone know that this issue should be resolved now. Please update and let us know if you continue to see any issues. Thank you very much!