I’m out of the loop right now but I think WK still supports API v2. I think the problem may be if you have popups disabled in your browsers, since I currently use the native browser confirm() dialog. Normally that dialog would appear after you click on one of the 4 Wanikani modes. After clicking on a mode, does a blurb appear in your URL bar about a popup getting blocked?
Ah, no popups are coming up, but I wonder if they’re being blocked because the security certificate is out of date of date according to various browsers
That could be it. I’ve been thinking about moving it to a site like itch.io so that I don’t have to worry about hosting issues like SSL certs. But I also like to use custom dialogs instead of the native browser dialogs, and that seems like it could be a quick fix.
I set up a custom dialog, does it work for you now?
Nope, I still can’t progress past the select a mode screen. I opened the website in both Chrome and Firefox, but got the same result
Do you have the issue if you use this link that uses http? It looks like it doesn’t work if you use https, which is the one that gives the cert warning because I don’t have SSL certs set up.
Yes, that works! Thank you so much!!
I’m sorry to always bug you 
kana games are working fine but vocab ones get stuck in a loading loop. What should I do?
Ah, I can’t even successfully click any of the buttons atm. When I tried to go to the website just now, I got the security certificate error. I proceeded against browser recommendations (tried Chrome and Firefox) but when I got to the kana/kanji selection screen, it won’t let me select any of them.
That sounds like the same issue as before where you’re accessing the https version of the site. Does this link still work?
This is so strange. So I cleared my cache and browser history, but even when I click this link or navigate from google, it adds an s back in on this Chrome user browser. If I navigate from a separate user, I go to the page just fine. Once there, I can use my API, but if I leave it blank, it won’t load.
Interesting, it’s not too surprising that https is being forced in certain cases. Ideally I want to support https properly so that these sort of issues don’t happen.