Yes, I think lack of HTTPS is what’s causing the issue.
I got it to work after setting a reverse proxy (Caddy, using these instructions HTTPS in Development) and changing the extension’s setting to use “Other server” (and setting it to https://localhost:8082/v2).
I wish Safari made it easier to find the issue.