404 error and WARNING: This is a development server. Do not use it in a production deployment

I have version 14 of frappe, erpnext
into it i have installed erpnext and latest hrms
now when i try running frappe bench I’m unable to run it,
im getting this

bench start
13:58:27 system        | redis_cache.1 started (pid=58167)
13:58:27 system        | redis_queue.1 started (pid=58170)
13:58:27 system        | web.1 started (pid=58173)
13:58:27 system        | socketio.1 started (pid=58177)
13:58:27 system        | watch.1 started (pid=58183)
13:58:27 system        | schedule.1 started (pid=58184)
13:58:27 redis_cache.1 | 58171:C 09 Oct 2023 13:58:27.052 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
13:58:27 redis_cache.1 | 58171:C 09 Oct 2023 13:58:27.052 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
13:58:27 redis_cache.1 | 58171:C 09 Oct 2023 13:58:27.052 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pid=58171, just started
13:58:27 redis_cache.1 | 58171:C 09 Oct 2023 13:58:27.052 * Configuration loaded
13:58:27 system        | worker.1 started (pid=58189)
13:58:27 redis_cache.1 | 58171:M 09 Oct 2023 13:58:27.052 * Increased maximum number of open files to 10032 (it was originally set to 1024).
13:58:27 redis_cache.1 | 58171:M 09 Oct 2023 13:58:27.052 * monotonic clock: POSIX clock_gettime
13:58:27 redis_cache.1 | 58171:M 09 Oct 2023 13:58:27.053 * Running mode=standalone, port=13000.
13:58:27 redis_queue.1 | 58175:C 09 Oct 2023 13:58:27.053 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
13:58:27 redis_queue.1 | 58175:C 09 Oct 2023 13:58:27.053 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
13:58:27 redis_queue.1 | 58175:C 09 Oct 2023 13:58:27.053 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pid=58175, just started
13:58:27 redis_queue.1 | 58175:C 09 Oct 2023 13:58:27.053 * Configuration loaded
13:58:27 redis_cache.1 | 58171:M 09 Oct 2023 13:58:27.053 * Server initialized
13:58:27 redis_cache.1 | 58171:M 09 Oct 2023 13:58:27.053 * Ready to accept connections tcp
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.053 * Increased maximum number of open files to 10032 (it was originally set to 1024).
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.053 * monotonic clock: POSIX clock_gettime
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.054 * Running mode=standalone, port=11000.
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.054 * Server initialized
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.054 * Loading RDB produced by version 7.2.1
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.054 * RDB age 241 seconds
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.054 * RDB memory usage when created 1.27 Mb
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.054 * Done loading RDB, keys loaded: 3, keys expired: 1.
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.054 * DB loaded from disk: 0.000 seconds
13:58:27 redis_queue.1 | 58175:M 09 Oct 2023 13:58:27.054 * Ready to accept connections tcp
13:58:27 watch.1       | 
13:58:27 watch.1       | yarn run v1.22.19
13:58:27 watch.1       | $ node esbuild --watch --live-reload
13:58:27 web.1         | WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
13:58:27 web.1         |  * Running on all addresses (0.0.0.0)
13:58:27 web.1         |  * Running on http://127.0.0.1:8000
13:58:27 web.1         |  * Running on http://192.168.25.45:8000
13:58:27 web.1         | Press CTRL+C to quit
13:58:27 web.1         |  * Restarting with stat
13:58:27 web.1         |  * Debugger is active!
13:58:27 web.1         |  * Debugger PIN: 125-529-604
13:58:28 watch.1       | clean: postcss.plugin was deprecated. Migration guide:
13:58:28 watch.1       | https://evilmartians.com/chronicles/postcss-8-plugin-migration
13:58:28 watch.1       | clean: postcss.plugin was deprecated. Migration guide:
13:58:28 watch.1       | https://evilmartians.com/chronicles/postcss-8-plugin-migration
13:58:28 watch.1       | clean: postcss.plugin was deprecated. Migration guide:
13:58:28 watch.1       | https://evilmartians.com/chronicles/postcss-8-plugin-migration
13:58:28 watch.1       | clean: postcss.plugin was deprecated. Migration guide:
13:58:28 watch.1       | https://evilmartians.com/chronicles/postcss-8-plugin-migration
13:58:28 watch.1       | Browserslist: caniuse-lite is outdated. Please run:
13:58:28 watch.1       |   npx browserslist@latest --update-db
13:58:28 watch.1       |   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
13:58:33 watch.1       | Watching for changes...
13:58:36 web.1         | 127.0.0.1 - - [09/Oct/2023 13:58:36] "GET / HTTP/1.1" 404 -
13:58:44 web.1         | 192.168.25.45 - - [09/Oct/2023 13:58:44] "GET / HTTP/1.1" 404 -

Please help me in resolving the problem, im unable to identify whats the problem, Im a newbie and would appreciate if i get some help
thank you in advance

Did you use

bench new-site ...
bench install-app ...

(with parameters appropriate for what you want to do)

to install the desired apps on your development site?

Yes I did use it

bench new-site site1.local

and then

bench get-app --branch version-14 erpnext

bench get-app hrms

as well I didnt create any custom app as of now i just want to run the hrms application but im unable to start the bench

If you don’t use the bench --site yoursitename install-app appname function, it will not be available for use.

new-site creates a site (what you type into the browser).
get-app fetches an app from somewhere and makes it available for installation (and/or development) “on a bench”.

install-app makes it available for USE on one of your sites created with new-site.

See here:
Bench Commands (frappeframework.com)

Thanks for the reply :slightly_smiling_face:, Its resolved acctually!

The thing which caused the above issue was i didn’t use the site I just installed the app onto the site and was starting the bench which gave me 404 error

Use the command below to use the bench (for those who faced the issue as mine)

bench use [site-name]

the you are good to go