Hello everyone,
What works :
From the command line, a direct POST to https://www.traccar.org/sms/ with the correct Authorization header and the JSON payload {"to":"{phone}","message":"{message}"} successfully sends an SMS.
In the Traccar UI, the "test" action returns 204 No Content.
What doesn’t work :
Despite the 204 response, the SMS does not actually arrive when triggered via the UI.
Traccar logs show activity on the Jetty side and occasionally a NameNotFoundException thrown by HttpSmsClient.
Context & configuration expectations :
Overall interpretation :
The successful curl test proves that the OVH network → traccar.org/sms endpoint and the token are working fine.
The UI’s 204 response indicates that Traccar is using HttpSmsClient, without any fatal errors.
The “Unconsumed content” message likely suggests that the user’s phone number isn’t being recognized—even though it appears correctly formatted and populated.
Your configuration doesn't look correct. At the very least you're missing sms.http.template.
Hello Anton;
Thanks for your quick response!
I've been using Traccar since 2018, and congratulations!
This installation is completely new via Docker Traccar/latest.
Sorry, bad screenshot.
Yes, and the curl works from the server.
Where do you think I can investigate?
Maybe capture traffic between the server and the messaging URL and see what the difference is.
Hello everyone,
What works :
From the command line, a direct POST to https://www.traccar.org/sms/ with the correct Authorization header and the JSON payload
{"to":"{phone}","message":"{message}"}successfully sends an SMS.In the Traccar UI, the "test" action returns 204 No Content.
What doesn’t work :
Despite the 204 response, the SMS does not actually arrive when triggered via the UI.
Traccar logs show activity on the Jetty side and occasionally a NameNotFoundException thrown by HttpSmsClient.
Context & configuration expectations :
Overall interpretation :
The successful curl test proves that the OVH network → traccar.org/sms endpoint and the token are working fine.
The UI’s 204 response indicates that Traccar is using HttpSmsClient, without any fatal errors.
The “Unconsumed content” message likely suggests that the user’s phone number isn’t being recognized—even though it appears correctly formatted and populated.