algora-io / algora-io/algora

[Bug] Successful GitHub login redirects to /home which returns 404

Open
#329 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Elixir
Stars
1.5k
Forks
152
PR merge metrics
No merged PRs in 30d

Description

Summary

After signing in with GitHub, authentication succeeds and my account is created correctly, but Algora redirects me to /home, which returns a 404 page.

Account

GitHub username: Youngboy1609

What works

  • Login with GitHub succeeds
  • https://algora.io/bounties loads correctly
  • Transactions / payout pages load correctly
  • Account information is visible in the top-right corner

What fails

All return 404.

Steps to reproduce

  1. Sign in with GitHub
  2. Authentication succeeds
  3. Redirect occurs to https://algora.io/home
  4. Page returns 404

Troubleshooting already performed

  • Verified GitHub email
  • Revoked Algora OAuth access and re-authorized
  • Cleared cookies
  • Tested in incognito mode
  • Tested multiple URLs manually

Observed behavior

Authentication appears successful because bounties and payout pages work normally, but the post-login redirect target appears broken or unavailable.

Expected behavior

Users should be redirected to a valid dashboard, profile, or landing page after successful login.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the GitHub sign-in flow and verify the redirect to /home, then compare the behavior of /home, /dashboard, /profile, /settings, and /users/Youngboy1609. Trace the post-login redirect and route handling from the GitHub authentication entry point. Done means successful login reaches a valid dashboard, profile, or landing page instead of a 404.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
authentication, backend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.