I installed this plugin for the first time tonight, and ran into the same problem. I tried logging in as the “superadmin” (which I assume is the user with an ID of 1), but no luck.
Because several users have reported this issue in the last few hours, I suspected there might be a newly created bug, so I tried downgrading to the previous version (6.0.03), and the problem went away.
