All backend REST calls fail with bad request

diegomoises1

My front end functions can call rest api just fine but using the template provided for REST AUTH calls it always gives the error:
api is calling POST 'https://{mywebsite}/v1/auth'
2025-03-06 15:34:47 api failed to execute REST call POST 'https://{mywebsite}/v1/auth', Post "https://{mywebsite}/v1/auth": Bad Request

I have confirmed that the site responses to calls through curl and from the logs of the api server I can see no requests being made. My environment is docker compose with REI3 3.10, no other changes.

gabriel

Hello and welcome to the forum 🙂

Bad request is a standard code, provided by the server if the client request is judged to be invalid. r3 does nothing special, it just sends the REST call as defined.

To find the issue, you could print out the parts of the request that the REST call is doing in the backend (like the request headers and body) and copy past them into any REST dev utility (like Postman).

Executing calls from the frontend might set different headers, or maybe the request body is formed differently.

diegomoises1

The problem is I see nothing being logged to the server providing the api. I execute the backend function from R3, I see in the logs of R3 the request being started, after one second another log says bad request but nothing being logged to the api server. I have logged both request headers and request body to the R3 server and everything looks normal. This only happens with backend requests.
Edit: This happens with both GET and POST
Edit2: Tested this on a fresh install built from source with go, running in http and the call works normally. seems to be a docker issue or something in my setup with https. I forgot to mention my instance is running behind nginx, could that cause an issue?

gabriel

The major difference between calls from the frontend and the backend is the source. The backend is executed from the r3 server host, which may not have access to the internet or does not trust the certificates from the API endpoint - your browser (where frontend calls originate) probably is fine on both points.

You could try curl from inside the Docker container to see what the issue is.

diegomoises1

Running the CURL command from within the docker succeeds with no issues. Additional note, calling an http url returns an EOF error.

gabriel

Then I would take a look at the proxy - does it have traffic logs?

diegomoises1

I managed to "fix" this by creating my own repository with dockerfile and docker compose integrated which builds and runs the official repo with go. This is currently working for me and correctly running backend REST calls