Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

http://localhost:3001/signup #315

Open
appbomb opened this issue Nov 10, 2024 · 1 comment
Open

http://localhost:3001/signup #315

appbomb opened this issue Nov 10, 2024 · 1 comment

Comments

@appbomb
Copy link

appbomb commented Nov 10, 2024

Auth and signup Request failed with status code 404
Starting a PostgreSQL dev database (based on your Wasp config) ✨

Additional info:
ℹ Connection URL, in case you might want to connect with external tools:
postgresql://postgresWaspDevUser:postgresWaspDevPass@localhost:5432/OpenSaaS-7bb96641a8
ℹ Database data is persisted in a docker volume with the following name (useful to know if you will want to delete it at some point):
wasp-dev-db-OpenSaaS-7bb96641a8

...

PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-11-10 19:36:58.339 UTC [1] LOG: starting PostgreSQL 17.0 (Debian 17.0-1.pgdg120+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-11-10 19:36:58.339 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-11-10 19:36:58.339 UTC [1] LOG: listening on IPv6 address "::", port 5432
2024-11-10 19:36:58.340 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-11-10 19:36:58.342 UTC [29] LOG: database system was shut down at 2024-11-10 19:36:33 UTC
2024-11-10 19:36:58.346 UTC [1] LOG: database system is ready to accept connections

[ Server ] > [email protected] watch
[ Server ] > nodemon --exec 'npm run bundle-and-start || exit 1'
[ Server ]
[ Client ] > [email protected] start
[ Client ] > npm run validate-env && vite
[ Client ]
[ Client ]
[ Client ] > [email protected] validate-env
[ Client ] > node -r dotenv/config ./scripts/validate-env.mjs
[ Client ]
[ Server ] [nodemon] 2.0.22
[ Server ] [nodemon] to restart at any time, enter rs
[ Server ] [nodemon] watching path(s): src//* ../../../src//* .env
[ Server ] [nodemon] watching extensions: ts,mts,js,mjs,json
[ Server ] [nodemon] starting npm run bundle-and-start || exit 1
[ Client ] 🔍 Validating environment variables...
[ Server ]
[ Server ] > [email protected] bundle-and-start
[ Server ] > npm run bundle && npm run start
[ Server ]
[ Server ]
[ Server ] > [email protected] bundle
[ Server ] > rollup --config --silent
[ Server ]
[ Client ] Port 3000 is in use, trying another one...
[ Client ]
[ Client ] VITE v5.4.10 ready in 402 ms
[ Client ]
[ Client ] ➜ Local: http://localhost:3001/
[ Client ] ➜ Network: http://10.195.65.150:3001/
[ Client ] ➜ press h + enter to show help
[ Server ]
[ Server ] > [email protected] start
[ Server ] > npm run validate-env && node --enable-source-maps -r dotenv/config bundle/server.js
[ Server ]
[ Server ]
[ Server ] > [email protected] validate-env
[ Server ] > node -r dotenv/config ./scripts/validate-env.mjs
[ Server ]
[ Server ] 🔍 Validating environment variables...
[ Server ] 🚀 "Email and password" auth initialized
[ Server ] Starting pg-boss...
[ Server!] (node:12709) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
[ Server!] (Use node --trace-deprecation ... to show where the warning was created)
[ Server ] pg-boss started!
[ Server ] Server listening on port 3001

@vincanger
Copy link
Collaborator

vincanger commented Nov 11, 2024

@appbomb It looks like you may have another app running on port 3000. Try stopping this app first before running your wasp app. Wasp apps run on port 3000 for the client and 3001 for the server, so these need to be free for the app to work correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants