after successfully integrating everything, i am wondering why my localhost is different from main website and i am also not able to add books and hence cannot see the form page.
Hey @Prabhleen
I also faced the same issue at the start.
One thing you should know about our bookbrainz project…
It is SERVER SIDE RENDERED(SSR) react application meaning whenever you click on a button eg. Add button it triggers a route and then server sends a markup and other required stuffs to client side.
So in my case my server was not running well, and that’s why whenever I clicked ADD button I get nothing…
So please check in console, if something is wrong or what!!!
In short, check the console where server is running…
@prabalsingh24 i did npm start -- --config ./config/config.json because i made changes to config.json like below but the problem is not resolved. @mr_monkey clearly mentioned here to use npm start:
@endurance21 i am getting this elasticsearch error:
Warning: Failed prop type: Invalid prop error.detailedMessage of type array supplied to ErrorPage, expected string.
in ErrorPage
HEAD /bookbrainz 404 126.682 ms - 8489
HEAD /bookbrainz 404 19.137 ms - 8489
PUT /bookbrainz 404 1539.929 ms - 8489
(node:29861) UnhandledPromiseRejectionWarning: Error: Not Found
at respond (/home/prabh_leen/bookbrainz-site/node_modules/elasticsearch/src/lib/transport.js:308:15)
at checkRespForFailure (/home/prabh_leen/bookbrainz-site/node_modules/elasticsearch/src/lib/transport.js:267:7)
at HttpConnector. (/home/prabh_leen/bookbrainz-site/node_modules/elasticsearch/src/lib/connectors/http.js:165:7)
at IncomingMessage.wrapper (/home/prabh_leen/bookbrainz-site/node_modules/lodash/lodash.js:4929:19)
at IncomingMessage.emit (events.js:323:22)
at endReadableNT (_stream_readable.js:1204:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:29861) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line API | Node.js v21.5.0 Documentation). (rejection id: 1)
(node:29861) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
@Prabhleen
Please confirm that, elastisearch is running
By applying this in terminal.
“Sudo systemctl status elastisearch”
and report the message it gives.
ok, so i started elasticsearch and confirmed the same from status, but then again when i run npm start, the problm is still the same, and error message too.