Skip to content
Back

[SOLVED] SPA Not working

  • 0
  • Resolved
  • 2
  • Web
  • Cloud
★ Remi ★
24 Dec, 2025, 05:10

So I'm using vite/react, which is spa, and it used to work before, but now whenever I go to any route except the root it shows appwrites 404 page, instead of using my routing, why is this?

TL;DR
The issue was with the routing in the SPA. By replacing anchor tags with `Link` components from `react-router-dom`, the problem was resolved. Additionally, setting the Fallback file in build settings to index.html fixed it.
Devika
24 Dec, 2025, 05:13

Do you get any errors while deploying the site? Also, which region you're using?

★ Remi ★
24 Dec, 2025, 05:13

NY, and I don't think so, let me check

★ Remi ★
24 Dec, 2025, 05:13

other than from postcss, no

Devika
24 Dec, 2025, 05:15

You said it used to work before and it's a SPA, then what do you mean by routing? Have you added more routes/pages recently?

★ Remi ★
24 Dec, 2025, 05:17

Everything should route to index.html, and the code inside my project is what should do the routing, using react-router. I belive their are new routes, I don't think that could be a cause

★ Remi ★
24 Dec, 2025, 05:17

And it used to work.

Devika
24 Dec, 2025, 05:20

Can you share with me the deployed link?

★ Remi ★
24 Dec, 2025, 05:20
Devika
24 Dec, 2025, 05:28

As I can see, you're directly using /account route here upon clicking the login/signup button instead of a /login or /signup route which means the user is getting redirected directly to the /account route even before he/she could login or signup. Don't you have any /login or /signup route?

★ Remi ★
24 Dec, 2025, 05:32

/account redirects to the login page if no account is signed in, but that route doesnt work either, which would be /auth/login

★ Remi ★
24 Dec, 2025, 05:33

it could be the lazy loading, but it's work in the past with it so

★ Remi ★
24 Dec, 2025, 05:35

my other vite project still works fine, which is werid because its basically the same setup

★ Remi ★
24 Dec, 2025, 05:35

idk if I fucked something up or not, but it's still weird

24 Dec, 2025, 06:24

If you don't mind and if you're comfortable, can you share the code for this? Then only I'll be able to tell if it's a mistake from your side or anything else

24 Dec, 2025, 06:28

I just set it to a public repo for a sec

24 Dec, 2025, 06:46

In this part of your AccountCard.jsx :

TypeScript
<a href="/account">
   <GlintButton>Manage Account</GlintButton>
</a>
.
.
<a href="/account">
   <GlintButton>Log In or Sign Up</GlintButton>
</a>

Can you try replacing it with Link component from react-router-dom? Like this:

TypeScript
<Link to="/account">
  <GlintButton>Manage Account</GlintButton>
</Link>
.
.
<Link to="/account">
  <GlintButton>Log In or Sign Up</GlintButton>
</Link>
24 Dec, 2025, 06:47

If it's really a routing issue, then this will solve it. And if it's something else, it won't. Try this and let me know the results.

24 Dec, 2025, 08:38

ok so going back to old builds on appwrite, i discovered this is the commit that broke it

https://github.com/Flamality/index/commits/b2ed49e90ae21684f6af5331e8d6f8b54e5075de

24 Dec, 2025, 08:39

so anything after alpha 10 doesnt work

24 Dec, 2025, 08:40

ima fuck with some things and see if anything does anything

24 Dec, 2025, 22:39

the output files are basically identical apart from the assets folder which contains the javascript, so I'm pretty sure its an appwrite issue. Im not sure why it isn't putting all routes to index.html

24 Dec, 2025, 22:44

I FIXED IT

24 Dec, 2025, 22:44

inside build settings I didn't have a Fallback file set, changing it to index.html fixed it!!!

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more