Hey @Nshiab, first of all, thanks for the kind words. The repository might be broken in the meantime due to some security update. I can take a look shortly to see whether I can reproduce the issue.
I can’t reproduce it, even with the last chrome version. It seems as if Fauna upgrades response header to https://localhost:3000 instead of http://localhost:3000 but I could be wrong since it’s been a while that I dealt with CORS issues.
This has something to do with mixed content (http local and https for Fauna) but I find it strange that it doesn’t happen on my side. You could always try to run it from https locally if you just want to get it working. I’ll try to find an answer though.
I am sorry I bothered you for something like that… But maybe you could add a sentence just saying “In case of a problem when trying to log in, disable your extensions and try again” ?