POST not working on prod but OK on dev

[Anoerak]

Describe the bug
When environment set up on prod, impossible to modify your email address, add your Wakatime API...
If set up on dev, everything is working.

System information
Please provide information on:

• Wakapi version => latest
• Operating system => ghcr.io/muety/wakapi:latest
• Database => postgres 17

Docker Compose

[muety]

Can you please give some more details? What exact error message are you getting, etc.?

[Anoerak]

Can you please give some more details? What exact error message are you getting, etc.?

Hi,

sure:

• for the API key => Failed to connect to wakatime, api key or endpoint url invalid but works fine in devmode.
• fir the email address => Error: Invalid parameters - perhaps invalid e-mail address? but again works fine in devmode.

I tried to replace devwith prod or production but couldn't change the email address or use my API key.

[muety]

Can you check the Wakapi server logs as well, please? And additionally send a screenshot of the browser console?

[Anoerak]

Can you check the Wakapi server logs as well, please? And additionally send a screenshot of the browser console?

[muety]

Thanks, can you please also share a screenshot of your browser console (F12 / DevTools)?

[Anoerak]

Thanks, can you please also share a screenshot of your browser console (F12 / DevTools)?

[muety]

Can't reproduce this. Can you additionally share a screenshot of the dev console's "Console" tab (JavaScript / HTML errors)? Also, can you please try (a) to reproduce this in an incognito browser window and (b) re-pull the image (make sure it's 2.12.3) and restart the server?

Are there any other errors or warning being shown in Wakapi server's logs? A screenshot of the full log from starting Wakapi up to the faulty request would be helpful.

[Anoerak]

Can't reproduce this. Can you additionally share a screenshot of the dev console's "Console" tab (JavaScript / HTML errors)? Also, can you please try (a) to reproduce this in an incognito browser window and (b) re-pull the image (make sure it's 2.12.3) and restart the server?

Are there any other errors or warning being shown in Wakapi server's logs? A screenshot of the full log from starting Wakapi up to the faulty request would be helpful.

Merry Christmas,

OK,
Sorry for the late answer.

I've redeployed the stack using the latest image.
Here are the console for the wakapi and Db from start:
_Wakapi_logs.txt
_Wakapi-DB_logs.txt

The screenshot of the console:
[

]

I tried in private mode, on Firefox and Chrome, but get the same errors.

[muety]

The log file is really hard to read as you somehow managed to squash many log statements into a single line. But from what I can see, there's nothing wrong on the server side. I'd need (a) your specific configuration (compose file) and (b) a screenshot of that failing POST request's body params to debug this further.

[Anoerak]

The log file is really hard to read as you somehow managed to squash many log statements into a single line. But from what I can see, there's nothing wrong on the server side. I'd need (a) your specific configuration (compose file) and (b) a screenshot of that failing POST request's body params to debug this further.

Here is the link to the docker-compose, it will work only once:
docker-compose

and here are the screenshots:

[muety]

The link to the compose file that you sent is not working.

Had another look into the code again.

• For updating the e-mail address: in prod mode, there is an additional check in place that requires a valid MX DNS record to be set for the e-mail address' domain, i.e. verifies that there's a publicly accessible mail server behind the domain.
• For updating the WakaTime API Key: no idea, why it's working in dev mode, but not in prod. Can your server make outgoing requests (specifically to wakatime.com)? Also, what are you settings as the API URL?

[muety]

Any updates on this?