Page not found for Google SSO

Support
,
1

Hi,

I need a solution to the error I’m encountering. I keep getting Page not Found error when employees are logging in through Goolge SSO. I’ve setup the API through Google Cloud, input the required information into Supadash dashboard, and using bolt to write the code for my site. I’ve went through the help section and ensured the netlify.toml file is located in within the index.html file. I’ve run out of ideas on how to get around this.

cheery-capybara-1562a9.netlify.app

2

It seems like you just need to debug your project.
Unfortunately assistance with this is ‘out of scope’ on Netlify’s side of things.

See:
https://www.netlify.com/support-scope/

Base functionality of Netlify’s build and deploy pipeline is supported, but we cannot help you debug any source code used either during build or after deployment.

Since you’ve built the site with AI, you should talk through your issues with the AI.
Or contact Bolt’s support here:
https://support.bolt.new/home

If you’re trying to work through it yourself, you should determine:

  • If the code works when not hosted on Netlify (e.g. when run locally)
  • What URL the user is being redirected to when they try and login
  • If that URL exists as a static file (or not)
  • If that URL should be being handled by a ‘function’ (or not)
  • If any kind of redirects/rewrites are required
    • If so, if it exists and is being applied correctly

etc.

Separate from that, you are encountering 404 errors when directly accessing sub-pages:
https://cheery-capybara-1562a9.netlify.app/about

If your project is a ‘Single Page Application’ (SPA), which it appears to be, it will require a rewrite as mentioned in the documentation. (This may be why you mention the netlify.toml yourself).

The documentation is here:
https://docs.netlify.com/configure-builds/javascript-spas/

Avoid 404s for SPAs
If your project is a single page app (SPA) that uses the history pushState method to get clean URLs, you must add a rewrite rule to serve the index.html file no matter what URL the browser requests.

The rewrite rule itself is here:
https://docs.netlify.com/routing/redirects/rewrites-proxies/#history-pushstate-and-single-page-apps

You can place it either in a _redirects file or netlify.toml

If using a netlify.toml file, it should be in your Base directory.
If using a _redirects file, it should end up in your Deploy directory when your build completes.

You may find that you can just mention it to Bolt, and have it place it correctly.