Apologies for this, it was caused by attempting to limit the URL permissions required by the extension. I'm pushing a new release (v2.8.1) now, so this should be fixed very soon.