Solved Traccar Port 5004 ?

[timconsidine]

I have bought a Queclink GL320 (mobile device or stick in trailer etc) and a GB130 (car battery fitting).

O am told that Queclink needs port 5004.

But I have phone devices added using port 5055.

• is port 5004 enabled already ?
  or I must set in the app settings ?

• can I set both 5055 and 5004 ports in app settings e.g. 5055,5004 ?

Oh, and does the Cloudron Traccar support device communicating over UDP or I must set them to TCP ?

Sadly I don't have time (pre-trip) to figure all this out by trial and error, and good to have experienced/authoritative answer.

Many thanks.

[nebulon]

So instead of port ranges, we have decided for a start to simply add the various protocol ports upon request to the package. The full list of devices with corresponding ports is https://www.traccar.org/devices/

For the moment we added port 5004 for the gl200 protocol now. Let us know if you need further ports and we add those to the package.

Given that those ports are kinda hardcoded/standardized, changing ports via Cloudron will likely not work.

[timconsidine]

@timconsidine so I found some moments to test a bit

• I can't set 5055 and 5004 at the same time
• setting port 5004 still allows 2 phones to connect and show online using 5055
  setting port 5004 does not allow the Queclink GL320 to connect

I'm wondering if :

• port 5055 is hard coded ?
• port 5004 is closed on the Cloudron server

Any thoughts ?

[timconsidine]

hmmm running ss -ltn shows port 5004 is open
[if I understand the output correctly]

Also I see on web that GL320 uses same config as GL300
Traccar docs show GL300 uses the gl200 protocol

Checking /app/code/conf/default.xml (i.e. hard-coded effectively) uses port 5004. Which is good.

So scratching my head why the GL320 device does not show up in traccar app. Added it as a device but just shows offline.

[nebulon]

The current app manifest indeed has essentially only one port (default 5055) exposed for traccar https://git.cloudron.io/cloudron/traccar-app/-/blob/master/CloudronManifest.json#L34

Having portranges requires platform changes, which we will discuss for next release, however there seems to be some limitations on docker side when lots of ports are exposed.

[timconsidine]

@nebulon thank you !

[nebulon]

So instead of port ranges, we have decided for a start to simply add the various protocol ports upon request to the package. The full list of devices with corresponding ports is https://www.traccar.org/devices/

For the moment we added port 5004 for the gl200 protocol now. Let us know if you need further ports and we add those to the package.

Given that those ports are kinda hardcoded/standardized, changing ports via Cloudron will likely not work.

[timconsidine]

@nebulon thank you !

Let me try it out and I will report back.

I think for now I only need the standard port and the gl200/5004.

It really comes down to the devices being connected.

The Teltonika range is popular, especially the FMT100, but approaching end of life as 2G gets phased out. But there is still life in them for few years, and they seem very widespread. So somebody might need those (teltonika/5027). I don't know if the newer Teltonika products use the same protocol/port - quick look suggests they may well do.

[StevenVB]

@nebulon
Hello, Where can I request the addon for the port 5001 (GPS103)

[nebulon]

@StevenVB the forum is the right place and I have added it to the package now, you should be able to update your app instance to have it enabled.

[StevenVB]

@nebulon Thanks works like a charm