Hey Gustavo,
I am really sorry that delay of this reply,
It seems like after you added WAF exception for com_easyblog, it seems like still the same.
Hmm, that was very hard for us troubleshoot using eXplorer is because If I debugging half way and put
var_dump("debug");exit; and suddenly happen, then it will causing your site become blank page and can't revert back my changes(because already getting blank page, unable to view back eXplorer to revert back the changes), so until now I don't recommended to use this.
For another reason why we need that is because we would like to get rid out of these possibilities and see is it related some of the plugin, some of the component or server restrict the script load on your site.
If your hosting still can't accept provide us with your FTP access, if you can modify the folder from your server, perhaps you can try rename this few folder and see how it goes?
#1. Try Rename JoomlaFolder/plugins to plugins_bak
Then refresh the Easyblog backend dashboard page and see is it still hitting these error on console?
#2. Try Rename JoomlaFolder/.htaccess and .htaccess.admintools to .htaccess_bak and .htaccess.admintools_bak
Then refresh the Easyblog backend dashboard page and see is it still hitting these error on console?
#3. Go to your phpmyadmin > find this table #_easyblog_configs > edit the config data > search `easyblog_environment` > change `
production` to `
development` > save
Then refresh the Easyblog backend dashboard page and see is it still hitting these error on console?
If above method still can't help, revert back all the changes and keep us updated then.