Bitdefender blocked my first backup attempt to my Google drive

What issue or error are you experiencing?

I’m running Local on Windows 10. My first backup to my google drive had started and Bitdefender (I later realized) blocked it, claiming files had been infected with malware, giving me the immediate choice to proceed with quarantining or restore the files. Not understanding what had just happened, I chose the safe path. I soon realized the backup had been compromised by a Failed indication in Local and looking at the quarantined files. I tried to restore the quarantined Local files through Bitfefender, seemingly to no avail (not sure the full list was displayed). Backup is now permanently blocked in Local : is starts, but soon displays a warning after a second saying the backup cannot proceed.
I closed Local and started it again, attempted a backup. Same.

Looking more closely into Bitdefender, it now shows no quarantined files. It had identified rclone.exe as malware If they have been restored, why is the backup still failing ?

The file rclone.exe (that I could only copy in the cmd window with xcopy .) was sent to Bitdefender for analysis as a false positive.

Help!

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc


System Details

  • Local Version: 9.2.0 windows

  • Operating System (OS) and OS version: Windows 10


Local Logs

local-lightning.log (622.4 KB)
Attach your Local Logs here (Help Doc - Retrieving Local’s Log)


Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

Hi @Guy1

So are you able to access your site okay you just aren’t able to create a backup at this time?

As a workaround for now you can always manually export your Local site and then just save that zip backup to your device or your own Cloud storage.

Thanks for the info. I was really trying to use the cloud backup to include someone else with Local installed on his PC in the development of the site.

Ah okay so this was so that you could each access the Cloud Backup and be able to import and export with each other?

Did the other person have any issues getting the add on set up?

Kinda, yes. I wanted to implement the backup first to show how easy it can be once the other person has Local installed on his PC. This other person is far from convinced, and a third party with more abilities would probably be the one involved. A long shot, but successful implementation would go a long way.

Your workaround is dully noted and practical as a start to a less “seamless” collaborative process.

Although the post below was not exactly the same issue, you could try the steps shared by one of our Devs here for “resetting” your Cloud Backups. This might get things working again.

Done all that and I cannot get the Backup Tool to display. I install the Add-on, put it on, Local automatically restarts and there is no backup function available in Tools :


I reverted to the initial sites.json file and it’s the same. A Local update came up, I installed it. No difference. I guess a fresh Local install after exporting my site might work.

When I look back at the Add-on, it’s still off.

@Guy1 a full uninstall/reinstall might do the trick. Here is an outline of the steps if helpful.

  • Export any sites that you have on Local and save them to a folder somewhere on your computer: Backup a Local Site - Local

  • Fully uninstall Local from your computer using your OS specific steps here: Uninstall Local - Local

  • Install the latest version of Local on this link: Releases - Local

  • Once installed, please restart the computer.

  • When the computer is restarted and turned on, close any applications that automatically run in the background (AntiVirus, Firewall, and other Developer applications included).

  • Check and see if the issue still persists. If so, please provide us with an updated log: Retrieve Local’s Log File - Local