Wrong location issue

Afrer deleting the device and reregistration the gps location is correct again

1. Have you checked logs to see what the device is sending?
2. Have you checked the timestamps to see if they are correct?
3. Are you using default config? If not, have you tried with it?

1. Yes I've identified the device by it's id.
2. Yes, they are correct.
3. No, I will try it just with the default.xml

This is my traccar.xml:

 <entry key='logger.level'>config</entry>
 <entry key='geocoder.enable'>false</entry>
 <entry key='status.timeout'>15</entry>
    
<entry key='filter.zero'>true</entry>
 <entry key='distance.enable'>true</entry>
 <entry key='coordinates.filter'>true</entry>
 <entry key='coordinates.maxError'>200</entry>

Thank you for your response

Hi Anton
I've switched from Postgres DB to the H2 DB and the issue is gone.

here my docker compose configuration,. Did I miss something here?

services:

trackcar:

container_name: traccar-server
hostname: traccar-server
restart: always
image: traccar/traccar:latest

volumes:
   - /mnt/localvolumes/traccar-server/app/logs:/opt/traccar/logs:rw 
   - /mnt/localvolumes/traccar-server/app/conf:/opt/traccar/conf:ro 
   - /mnt/localvolumes/traccar-server/app/lib/opt/traccar/lib

ports:
  - 80:8082
  - 5000-5150:5000-5150
  - 5000-5150:5000-5150/udp

networks:
  default:
    ipv4_address: 192.168.1.xx

db:
image: postgres
container_name: traccar_db
hostname: traccar_db
restart: always

volumes:
  - /mnt/localvolumes/traccar-server/db/data:/var/lib/postgresql/data
  - /mnt/localvolumes/traccar-server/db/scripts:/var/lib/postgresql/scripts
  - /init_db.sql:/docker-entrypoint-initdb.d/init_db.sql
  
ports:
  - "5432:5432"
environment:
  - POSTGRES_HOST_AUTH_METHOD=trust
  - POSTGRES_USER=traccar
  - POSTGRES_PASSWORD=traccar
  - POSTGRES_DB=traccar
        
healthcheck: 
    test: "pg_isready -U \"$$POSTGRES_USER\" -d \"$$POSTGRES_DB\""
    interval: 10s
    timeout: 5s
    retries: 5
    
networks:
   default:
      ipv4_address: 192.168.1.xx

I'm pretty sure it has nothing to do with the database type.

Hi Anton,

you are right. The issue is not database related. I investigated the following:

1. Traccar on Docker (operated on a virtual machine described in 2): lost connection
2. Traccar on VMWare ESXi virtual machine with Ubuntu os: lost connection
3. Traccar on baremetal Ubuntu: working so far

Since you are offering traccar cloud portal I assume the software is desinged to be operated on hypervisors. Any idea what could cause this problem on docker or virtual enviroments. I couldn't find anything in the log. Do I miss something here?

No ideas.