BOX Tracker, Docs attached, is this supported?

Luke Crooks6 years ago

Is this protocol supported? Currently when I sent a request to Traccar I get a

"400/bad request response. Bad Message 400, Bad EOL."

So I assume it isn't currently supported, The documentation for the protocol can be found here:

https://drive.google.com/file/d/1hPCRt4SFs3Gn-BSYz_McYngKzaQUodcw/view?usp=sharing

parelius6 years ago

Port 5065

Luke Crooks6 years ago

So say I am hosting traccar on port 10.1.1.1:8082, do I simply set this device to connect to 10.1.1.1:5065 will traccar be listening on this port? Or do I need to do anything else to make this available? I can't imagine traccar lists on multiple ports automatically, or do I have to change my main traccar port to 5065?

parelius6 years ago

Let tracker connect to host:5065 and open port in firewall.

Anton Tananaev6 years ago

Traccar listens for all device ports by default:

https://www.traccar.org/devices/

Luke Crooks6 years ago

If I run traccar behind nginx, is the best way to connect to a specific port to say create a new vhost, box.mytraccar.example.com listening on port 80 that then proxys All requests to say localhost:5065?

Anton Tananaev6 years ago

Box is not an HTTP-based protocol, so you can't proxy it with regular HTTP proxy.

Luke Crooks6 years ago

Thanks Anton, I currently run traccar on private IP address on a server that hosts many other applications, currently I'm using nginx to proxy all the traffic, what would you suggest setup wise to forward all traffic for this box?

Currently I have traccar.example.com listening on 443 for ssl, which I proxy to 10.1.1.15:8082 and I only currently use iphone/android clients and simply point them to https://traccar.example.com (without specifying a port) and the applications connect perfectly.

Anton Tananaev6 years ago

You need a separate TCP port. You can't re-use same port for HTTP and non-HTTP traffic.