I was facing the exact same issue and could find out that there was a bug in the plugin itself.
I already created a pull-request that fixes that issue. In the meantime you could also apply the changes according to the pull request directly in the files on your server.