Hi Chris,
Two separate things are going on, and the browser one is a false alarm.
The "Not authenticated" you get when you open the URL in a browser is not your problem. The ingest endpoint only accepts POST (that's how Traccar sends positions). A browser sends a GET, which falls through to the normal signed-in part of the page: so seeing that message actually means your URL is correct. (I just made that friendlier in the latest release so it won't send people down this path.)
The real issue is the 404 Traccar reports: that means the forward.url isn't reaching api/location.php. Two things to check:
Your exact forward.url line. It should be exactly:
http://YOUR-HOST/api/location.php?provider=traccar(if you set a token, add it XML-escaped: ...
?provider=traccar&token=YOURTOKEN)
A 404 usually means a typo in the path, or TicketsCAD isn't at the web root (if it lives in a subfolder, that folder has to be in the URL).
From the Traccar machine, run this — it POSTs a test position exactly the way Traccar does:
curl -X POST "http://YOUR-HOST/api/location.php?provider=traccar" -H "Content-Type: application/json" -d "{"device":{"uniqueId":"TEST"},"position":{"latitude":44.97,"longitude":-93.26}}"A correct URL returns:
{"ok":true,"provider":"traccar"}Whatever URL makes that curl succeed is exactly what forward.url should be.
Also confirm the Traccar provider is switched on in TicketsCAD: Config, then Location Providers, then Traccar, Enabled.
One note on http vs https: plain http is fine on a LAN. Just make sure the app is actually being served on http at that host/port — if it only answers on https, a plain-http URL will fail. The curl test above settles it either way.