@SiteGround No, *I* troubleshooted the issue. Your team tried to disable all my plugins, which had nothing to do with the error.