This is the second time I am facing this issue while setting up a new site with netlify.
Issue: The publii app says that sync complete and go to your website now, but when you go to netlify dashboard, you would see the under Deploy section as UPLOADING. Same issue is here as well
The screenshot the user has attached is what I see and what I have seen a couple of times in the past. The new files are not getting pushed actually. i have tried several times during past 24 hours. All the files are there in my site's folder but changed are not being uploaded. There is no syncing issue at all.
How did it happen: As the user in the above thread has asked that index file is not being replaced - that was one issue I faced last month as well. But this time, I pushed all my site's files to netlify and the site was live. Now I added a file "netlify.toml" in the site root folder and then I synced again. Publii says synced but netlify says UPLOADING forerver. I deleted that toml file from root folder and tried to sync again but netlify says UPLOADING. It's been 10 hours I have been seeing this msz.
Now, when I create a new site and sync my site again, I can see the site as PUBLISHED.
Netlify support team says the issue is not related to their server as they cannot see any new files in my websites.
Can anyone help me out here pls.
Hi Ajeet,Could you provide a backup of your website - I will try to reproduce this issue on my Netlify account.I have tested few websites, but I am unable to reproduce this problem. If website on Netlify is marked as UPLOADING it can suggest that some file transfer was interrupted and Netlify waits for a file which will never come (so waiting few hours after deploying a website via Publii won't help).
--Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!
I have downloaded the backup and I can now see the same issue as you have described.
I will debug it and I will come back to you with a potential solution.
BTW - which OS are you using with Publii?
I have debug the connection with Netlify and I have found the following response while uploading files:
Max site size exceeded (104857600)
It seems that Netlify free plan allows only sites which weights up to 100MB per site and your website weights around 160MB now.
I will implement a notification about this error in Publii v.0.35.1, because as I see people gets this error more and more.
Issue with lack of notifications regarding the problems, solved here: https://github.com/GetPublii/Publii/issues/449
Thanks so much Thomas.
I am using Windows 10 Pro latest build. One thing if you can clarify me - If netlify site size restriction is 100 mb max, than how am I able to upload manually 157 mb ( my current site size). I am creating the non-compressed folder in using publii server settings and uploading the file.
the question regarding size is a question for Netlify. Their API behaves strangely - I was able to upload a website which weights 110MB, so it must be an issue with their API.
Thank you. I will ask them
I have asked this in Netlify community, and here is the response from the Head of their Support,
"There is no intended size limitation in normal use, but in case you try to upload a file with a newline in the name, you hit an unintended area of the code where we do check your total deploy size and output an error about 100MB limitation.So, don’t do that and there is no site size limit".
Full thread: https://community.netlify.com/t/free-plan-website-size-limit/2084/6
Can you please check once, the thread
That's weird, because we are not uploading files with newline in the name. The problem must lie somewhere else. I suppose that it can be connected with images contents as when your website is processed by our improved thumbnails regeneration engine (will be available at Publii 0.35.1) then all is uploading correctly.
But in fact it still looks like Netlify API error.
Thanks for the information. One of the users had the similar issue (https://publii.ticksy.com//ticket/2041174/). Whatever be the reason, the manual upload thing is working smoothly. So, there might be the issue with this current v0.35 (or not). To verify if there is any issue due the images with the current version of Publii, I can send the website backup to their support team to look into it but it will be the last thing to do.
When is v0.35.1 getting released on ?
I'm running into the same issue.
Regenerating thumbnails doesn't solve the problem for me.
I can do a manual deploy via the Netlify website, as a workaround.
I was also doing the manual deploy as my site size was 175 mb. With version .35.1, my site size reduced and within 100 mb and now I can sync it without any issue.
A couple of my friends are deploying their static sites with Gatsby + Netlify CLI ( size more than 100 mb), and they don't find any issue. In this thread, I also mentioned one of the users had faced same issue but Thomas was sure the issue is with the Netlify, so I better thought to close this issue at Netlify's forum. I also sent my site backup to them, on which they responded there was no change in the files, that's why the changes were not reflected.
The issue is not caused by not uploading some files, but by some unhandled error in the Netlify API. API returns senseless error about exceeding quota (which is much higher). So most probably some files are not properly handled by Netlify API. We are unable to do anything more at this moment with it. In my opinion it is an issue on the Netlify side, as probably ZIP handling and API are using different code.
I argued on the Netlify forum:
"Well, what you are saying is that Publii is not sending all the files, correct? Then at least Netlify API should report this error, and not say “Storage quota exceeded”, which does not accurately describe the problem. So, in my opinion, there’s also an aspect which Netlify should look at?"
If our Thomas is positively convinced that Publii is not to blame, then surely the Netlify API-developers will discover what the problem really is when they're correcting the error message.
"Sure, that is a bad error message, I agree, I’ll get a bug filed on that."
But just for my understanding, Thomas: during the syncing, does Publii detect which files are changed, and then only upload those files? Or does Publii upload the entire "Output"-directory always, and is it up to the Netlify-API to detect the changes? Is it conceivable that we have a conflict here, ie. that Publii is really only sending the updated files while Netlify always expects a complete website?
The sync with Netlify API works as following:
1) We are sending hashes from all files in the directory
2) Netlify API sends us a list of hashes which are not existing on their servers (so even if your website weights around 200MB it can need only few files to upload if somebody else sent the same files earlier)
3) Publii uploads only files which are mentioned by Netlify API response
The problem is caused in my opinion on the Netlify API side with wrong error handling.