Plugin Support
Saransh
(@saranshwpm)
Hi,
Thank you for the details.
We’ve seen similar download behavior in some cases where the cause was related to the browser or caching rather than the backup archive itself. Could you please help us rule that out first?
- Try downloading the backup using a different browser or an incognito/private window.
- Temporarily disable any download manager, caching, or security-related plugins and check if the behavior changes.
- Check whether the backup archive itself exists correctly at the storage destination. If it does, please try downloading it directly via FTP or your hosting File Manager.
Since you’ve noticed that deactivating Avada changes the behavior on both sites, that’s useful information. Once we rule out the points above, we can better determine whether there is indeed a conflict with Avada and investigate further.
Best regards,
Thread Starter
Zaffy
(@zaffy)
Tried Firefox and Chrome and Edge
Tried in Private window
Deactivated security plugin
Checked with ftp app and the archive exists and downloaded ok
delete site data and cookies
Same result
Maybe Avada was a coincidence, cause now another site with a different theme has the same issue.
In inspect>console both sites show the same error when we are in backup page. but only in Firefox. In chrome no errors in console
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://firefox-source-docs.mozilla.org/performance/scroll-linked_effects.html for further details and to join the discussion on related tools and features!
Plugin Support
Saransh
(@saranshwpm)
Hello,
Thank you for the reply.
This is likely something very specific to the installation and would require a closer investigation.
In that case, please reach out through the support option in the plugin (bottom-right corner) or via:
https://backwpup.com/contact/
We’ll be happy to investigate it further.
Thread Starter
Zaffy
(@zaffy)
3 different sites, 2 different themes and there is something specific in the installation?
There was another person here that also had the same issue…
Plugin Support
Saransh
(@saranshwpm)
Hello, @zaffy.
I understand your concern. For the other user, it turned out to be a cache issue.
Given that you had already ruled out the majority of the possible issues, I recommended contacting support for a more thorough investigation.
Best regards.