gramps.js requires username and password about gramps-web HOT 8 CLOSED

Firefox when I click on submit for random usernames gives a NetworkError when attempting to fetch resource, and the terminal says the below:

Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
at new NodeError (node:internal/errors:259:15)
at ReadStream.onclose (node:internal/streams/end-of-stream:117:38)
at ReadStream.emit (node:events:339:22)
at emitCloseNT (node:internal/streams/destroy:169:10)
at processTicksAndRejections (node:internal/process/task_queues:79:21)

from gramps-web.

Can you please try again? It happens e.g. when the backend cannot be reached. Since the backend is hosted on a free Heroku instance, it goes to sleep after 30 min of inactivity and then always takes some time to wake up again. So it could help trying again after one minute.

Of course, it's not good that there is no informative error message.

from gramps-web.

Thank you for responding. In this instance, the backend is supposed to be the Gramps webapi installed on the same VM, running on port 5555. I suspect I misconfigured the webapi if this is the behavior when the frontend can't reach the backend. Is Gramps.js configurable?

from gramps-web.

Sorry, I misread your question, I thought this was about the demo server.

By default, the frontend looks for the backend on localhost:5555. Check if you can open any of the API endpoints without authentication (e.g. http://localhost:5555/api/metadata/).

from gramps-web.

Is this still an issue?

from gramps-web.

It is still an issue, but it appears to be an issue with getting the webapi to work with apache2.

from gramps-web.

the result of curl http://localhost:5555/api/metadata is a 404 error. Same 404 error with curl http://localhost:5555. The webapi is started with gunicorn -e GRAMPS_API_CONFIG=/usr/local/www/gramps-webapi-0.1/config.cfg --bind localhost:5555 gramps_webapi.wsgi:app. I suspect it is an issue with getting apache2 to work with the webapi, specifically configuring python3 apps to be configured properly with apache2.

I was trying to get it to work with apache2 instead of nginx because I already set up my home server to work with apache2 and didn't want to switch the entire thing to nginx when the webapi reached the production stage.

from gramps-web.

I'm not sure I understand what Apache has to do with this. If you start gunicorn, you should be able to curl the endpoints from within the VM.

I'll close this issue just because it's not caused by Gramps.js, but feel free to continue posting below or to open an issue at Gramps Web API.

from gramps-web.