I encountered the same issue today and finally found the solution to disable the content block:
- Access
about:configfromchrome://geckoview/content/config.xhtml
Source: About:config missing - #47 by Ash9 - Optionally, you can enable
about:configpermanently by settinggeneral.aboutConfig.enabletotrue. - Search for
safebrowsingand toggle the option that may be relevant to the blocking. This requires some trial and error because there are so many possible reasons for the block. For my specific case, settingbrowser.safebrowsing.malware.enabledtofalsesolves the problem.