Gt06n 4G won't show up, have tried the trouble shooting

Cemara2 days ago

How should you be able to open a page on port 5023 when its just the protocol port for your device?

well because the traccar server which is located in localhost:8082 is being forwarded to ippublic:5023

Track-trace2 days ago

Yes thats not how it works.

You run your local traccar server on port 8082 then forward your internet ip to port 8082 on your local ip traccar server.

You point your device to your internet ip port 5023 then forward your internet ip to port 5023 on your local ip traccar server.
Make sure you run the protocol port on port 5023

Anton Tananaev2 days ago

So the conclusion is this one is not compatible?

Don't know how you made such conclusion. I think the most likely issue is your networking setup, not a device compatibility.

Track-trace2 days ago

Better example (could not edit the above).

Yes thats not how it works.

You run your local traccar server on port 8082 then forward your internet ip to port 8082 on your local ip traccar server.

example ip's:

local traccar server ip: 192.168.1.25
Iocal traccar web interface port: 8082
Device protocol port: 5023

Your router:

Internet ip: 88.88.88.88
Open port 8082 to the internet
Open port 5023 to the internet

For your traccar webserver:
You point your browser to your internet IP or Domain name that points to your internet ip: 88.88.88.88 port 8082
then in your router you forward your internet ip: 88.88.88.88 port 8082 to local ip:192.168.1.25 port 8082 on your local ip traccar server.
Make sure you run the traccar server on example ip: 192.168.1.25

For your tracking device:
You point your tracking device to your internet ip: 88.88.88.88 port 5023
then forward your internet ip: 88.88.88.88 port 5023 to local ip:192.168.1.25 port 5023 on your local ip traccar server.
Make sure you run the protocol on protocol port 5023

Cemara2 days ago

Ahh finally its detected! thanks track-trace
I have to change 8082 to 5023.

There are 2 issues though,
1 . Time is showing 1980
2. zero latitude and longitude 

2025-04-26 19:23:02  INFO: [Tcd7645b0: osmand > 127.0.0.1] HTTP/1.1 200 OK\r\ncontent-length: 0\r\n\r\n
2025-04-26 19:23:32  INFO: [Tcd7645b0] disconnected
2025-04-26 19:28:43  INFO: [T14671785] connected
2025-04-26 19:28:43  INFO: [T14671785: osmand < 127.0.0.1] POST /?>id=850086×tamp=1745670523&lat=-7.7853172&lon=110.3649966&speed=0.0&bearing=0.0&altitude=145.10000610351562&accuracy=10>0.0&batt=64.0 HTTP/1.1\r\nUse>
2025-04-26 19:28:43  INFO: [T14671785] id: 850086, time: 2025-04-26 19:28:43, lat: -7.78532, lon: 110.36500, course: 0.0, accuracy: 100.0
2025-04-26 19:28:43  INFO: [T14671785: osmand > 127.0.0.1] HTTP/1.1 200 OK\r\ncontent-length: 0\r\n\r\n
2025-04-26 19:29:13  INFO: [T14671785] disconnected
2025-04-26 19:33:41  INFO: [Tb8f27b4b] connected
2025-04-26 19:33:41  INFO: [Tb8f27b4b: gt06 < 182.2.46.227] 78781101086683307027553980932bc1067ae82c0d0a
2025-04-26 19:33:41  INFO: Event id: 866833070275539, time: 2025-04-26 19:33:41, type: deviceOnline, notifications: 0
2025-04-26 19:33:41  INFO: [Tb8f27b4b: gt06 > 182.2.46.227] 78780501067a40580d0a
2025-04-26 19:33:41  INFO: [Tb8f27b4b] disconnected
2025-04-26 19:33:41  INFO: Event id: 866833070275539, time: 2025-04-26 19:33:41, type: deviceOffline, notifications: 0
2025-04-26 19:33:44  INFO: [T5eb2a950] connected
2025-04-26 19:33:44  INFO: [T5eb2a950: gt06 < 182.2.46.227] 78781101086683307027553980932bc1067bf9a50d0a
2025-04-26 19:33:44  INFO: Event id: 866833070275539, time: 2025-04-26 19:33:44, type: deviceOnline, notifications: 0
2025-04-26 19:33:44  INFO: [T5eb2a950: gt06 > 182.2.46.227] 78780501067b51d10d0a
2025-04-26 19:33:45  INFO: [T5eb2a950: gt06 < 182.2.46.227] >7979015c9404414c4d313d37353b414c4d323d44353b414c4d333d35463b535441313d34303b4459443d30313b534f533d2c2c3b43454e5445523d3>b4746454e4345312c4f46462c302c302e303030>
2025-04-26 19:33:45  INFO: [T5eb2a950] id: 866833070275539, time: 1980-01-06 07:00:19, lat: 0.00000, lon: 0.00000, course: 0.0
2025-04-26 19:33:46  INFO: [T5eb2a950: gt06 < 182.2.46.227] 78780a130406040002067d97e90d0a
2025-04-26 19:33:46  INFO: [T5eb2a950] id: 866833070275539, time: 1980-01-06 07:00:19, lat: 0.00000, lon: 0.00000, course: 0.0
2025-04-26 19:33:46  INFO: [T5eb2a950: gt06 > 182.2.46.227] 78780513067d04ca0d0a
2025-04-26 19:34:18  INFO: [T5eb2a950] disconnected
2025-04-26 19:34:18  INFO: Event id: 866833070275539, time: 2025-04-26 19:34:18, type: deviceOffline, notifications: 0
2025-04-26 19:34:21  INFO: [T16617fe1] connected
2025-04-26 19:34:21  INFO: [T16617fe1: gt06 < 182.2.46.227] 78781101086683307027553980932bc1067eae080d0a
2025-04-26 19:34:21  INFO: Event id: 866833070275539, time: 2025-04-26 19:34:21, type: deviceOnline, notifications: 0
2025-04-26 19:34:21  INFO: [T16617fe1: gt06 > 182.2.46.227] 78780501067e067c0d0a
2025-04-26 19:34:21  WARN: [T16617fe1] error - Connection reset - SocketException (...)
2025-04-26 19:34:21  INFO: [T16617fe1] disconnected
2025-04-26 19:34:21  INFO: Event id: 866833070275539, time: 2025-04-26 19:34:21, type: deviceOffline, notifications: 0
2025-04-26 19:34:24  INFO: [T775e00ff] connected
2025-04-26 19:34:24  INFO: [T775e00ff: gt06 < 182.2.46.227] 78781101086683307027553980932bc1067fbf810d0a
2025-04-26 19:34:24  INFO: Event id: 866833070275539, time: 2025-04-26 19:34:24, type: deviceOnline, notifications: 0
2025-04-26 19:34:24  INFO: [T775e00ff: gt06 > 182.2.46.227] 78780501067f17f50d0a
2025-04-26 19:34:25  INFO: [T775e00ff: gt06 < 182.2.46.227] >7979015c9404414c4d313d37353b414c4d323d44353b414c4d333d35463b535441313d34303b4459443d30313b534f533d2c2c3b43454e5445523d3b4746454e4345312c4f46462c302c302e303030>
2025-04-26 19:34:25  INFO: [T775e00ff] id: 866833070275539, time: 1980-01-06 07:00:19, lat: 0.00000, lon: 0.00000, course: 0.0
2025-04-26 19:34:26  INFO: [T775e00ff: gt06 < 182.2.46.227] 78780a1304060400020681aa0a0d0a
2025-04-26 19:34:26  INFO: [T775e00ff] id: 866833070275539, time: 1980-01-06 07:00:19, lat: 0.00000, lon: 0.00000, course: 0.0
2025-04-26 19:34:26  INFO: [T775e00ff: gt06 > 182.2.46.227] 78780513068139290d0a
2025-04-26 19:34:58  INFO: user: 1, action: login, from: 36.90.18.35
2025-04-26 19:35:12  WARN: Geocoder network error - HTTP 404 Not Found - NotFoundException (... < JsonGeocoder:126 < ServerResource:121 >< ... < OverrideFilter:50 < ...)
2025-04-26 19:35:48  WARN: Geocoder network error - HTTP 404 Not Found - NotFoundException (... < JsonGeocoder:126 < ServerResource:121 >< ... < OverrideFilter:50 < ...)

I have searched about this and looks like i need to filter the protocol ? But how do i do it for docker install?

Anton Tananaev2 days ago

Both issues mean that your device hasn't reported a GPS location yet.