Auth working on dev, not so on stage
App has been working, logging in/creating users works on dev, moving it to stage & now running into issues. I'm using the SaaS template & its default authentication. Now on both the /login and /signup routes, the action button is giving a 404. That's all coming from the <LoginForm> which is part of wasp.
Who is supposed to be handling these /auth/email/signup and /auth/email/login routes? Why do they work on the dev environment, but are not there in prod?
9 Replies
Hi @Conspyre. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Sorry @Conspyre, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@kapa.ai are you online?
Let me check the knowledge base for you. One moment! :books:
----------------------
As an AI, I'm always online and ready to assist you with your questions about Wasp. How can I help you today?
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Conspyre, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@kapa.ai App has been working, logging in/creating users works on dev, moving it to stage & now running into issues. I'm using the SaaS template & its default authentication. Now on both the /login and /signup routes, the action button is giving a 404. That's all coming from the <LoginForm> which is part of wasp.
Who is supposed to be handling these /auth/email/signup and /auth/email/login routes? Why do they work on the dev environment, but are not there in prod?
Let me check the knowledge base for you. One moment! :books:
----------------------
The
/auth/email/signup and /auth/email/login routes are handled by the Wasp framework. They are part of the default authentication provided by Wasp, as mentioned in the documentation (https://wasp-lang.dev/docs/auth/email#4-create-the-client-pages).
The issue you're experiencing could be due to a variety of reasons. Here are a few things you could check:
1. Environment Configuration: Ensure that your production environment is correctly set up and that all necessary configurations are in place. This includes checking your .env files and any other environment-specific settings.
2. Build Process: Make sure that your application is being correctly built for the production environment. This includes running any necessary build scripts and ensuring that all dependencies are correctly installed.
3. Server Setup: Check that your server is correctly set up to handle the routes. This includes ensuring that the server is correctly routing requests to your Wasp application.
4. Differences between Dev and Prod: There might be differences in how your development and production environments are set up. It's important to ensure that both environments are as similar as possible to avoid issues like this.
If you're still having trouble, I would recommend checking the Wasp Github issues (https://github.com/wasp-lang/wasp/issues) to see if anyone else has experienced a similar problem. You could also consider opening a new issue to get help from the Wasp community.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Conspyre, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@kapa.ai the issue is solved.
Let me check the knowledge base for you. One moment! :books:
----------------------
I'm glad to hear that your issue is resolved! If you have any more questions or run into any other issues with Wasp, feel free to ask. Happy coding!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Conspyre, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
wasp
What was the issue?