Skip to main content

Trouble creating an account via GitHub / other options for auth?

First let me say, this tool is fantastic, and we’ve had a lot of success using it at our institution already!

We’re interested in subscribing, but Google isn’t a great fit for a shared account at our institution. GitHub would work, but I'm getting a "Page not found" issue when I try to create an account for Liiive via GitHub. I wondered:

  • Are there known issues with creating Liiive accounts via GitHub?

  • Separately, do you have plans for adding other authentication options, such as an arbitrary email address?

Thanks!

9 comments

Log in to comment and vote

Comments9

  • Ian Spangler

    •

    Oct 6, 2025

    Hmm -- I did verify that I’m logged in correctly, but am having no luck logging in via GitHub. On a variety of browsers, I keep hitting the same “Page not found” error. I was able to successfully log in via Google, though, so we’ll just stick with that for now and I’ll see if someone else on my team can get in via GitHub!

    • Ian Spangler

      •

      Oct 6, 2025

      @Rainer Simon- a quick follow up to let you know that I had someone else on my team try to authenticate their accounts, and they ran into the same 404 Oauth page on GitHub. Not sure where the hiccup is, but we’re stumped!

      • Rainer Simon

        Team•

        Oct 7, 2025

        Hm, that’s really weird. Can you confirm that they were able to log in to their Github accounts without problems? When they hit the 404, is that on a liiive URL, or one on github.com?

        • Ian Spangler

          •

          Oct 7, 2025

          Yes, we were both able to log into Github on its own, but something gets tripped up while redirecting through Oauth. We hit a 404 on Github, but it has a bunch of URL params that redirect through liiive and supabase. it resembles:

          https://github.com/login/oauth/authorize?client_id={{CLIENT_ID}}&redirect_to=https://liiive.now/dashboard&redirect_uri=https://ewcknamfmichzisbasxs.supabase.co/auth/v1/callback&response_type=code&scope=user:email&state={{REALLY_LONG_STATE_KEY}}

          • Rainer Simon

            Team•

            Oct 7, 2025

            Sorry for that… I’ll investigate. For now, all I can say is that this looks exactly like the URL you’re supposed to hit, and which I’ve verified with a test account just now. Is there anything at all that might be special about your setup? (Are there any institiutional firewalls in between that might strip things off? Does the Github account have 2FA activated or not?)

            • Ian Spangler

              •

              Oct 7, 2025

              Thanks Rainer—no apology necessary!

              I tried it authenticating in a I’m not aware of any firewalls (I’m usually able to authenticate via Github for similar third-party services like Netlify). I’m pretty sure 2FA is enabled on all the accounts that were tested, it definitely is on mine. In case it’s helpful, here’s what happens when I try testing it in an incognito window or a browser like Tor:

              • Go to liiive > Click “Create account”

              • Redirected to Github login page > enter credentials

              • Enter 2FA code (I use Duo Mobile for this)

              • Hit the 404 at Github

              • Rainer Simon

                Team•

                Oct 9, 2025

                Sorry for the delay - can you try again?

                • Ian Spangler

                  •

                  Oct 20, 2025

                  hi @Rainer Simon - sorry for the delay, i was at a conference last week and am just getting back to this. the GitHub auth works perfectly for me now! thanks a bunch for resolving this so quickly.

  • Rainer Simon

    Team•

    Oct 6, 2025

    Thanks! I just checked and Github login seems to work ok. Did you verify that you logged in to your Github account correctly?

    I might add other login options in the future, but TBH no specific timeline yet.