All devices are offline since the last update!
Have you checked logs?
Hey,
The only information I've been able to find so far is this. Could it be a DNS problem? Because the Traccar servers have been running flawlessly for over a year.
But we haven't changed anything in our nameserver infrastructure either!
The funny thing is, it doesn't suddenly work on a fresh installation in our virtual data center in Berlin either. And it doesn't work on the production server located in Düsseldorf either.
Here's the log that I consider unusual so far!
Dec 01 14:59:11 box:tasks updating task 3509 with: {"message":"Waiting for propagation of gps.DOMAIN.de"}
Dec 01 14:59:11 box:dns/waitfordns waitForDns: waiting for gps.DOMAIN.de to be 123.123.123.123 in zone DOMAIN.de
Dec 01 14:59:11 box:dns/waitfordns waitForDns: nameservers are ["ns1.DOMAIN.de","ns2.DOMAIN.de","ns3.DOMAIN.de"]
Dec 01 14:59:11 box:dns/waitfordns resolveIp: Checking A for gps.DOMAIN.de at 456.456.456.465
Dec 01 14:59:11 box:dns/waitfordns isChangeSynced: gps.DOMAIN.de (A) was resolved to 123.123.123.123 at NS ns1.DOMAIN.de (456.456.456.465). Expecting 123.123.123.123. Match true
Dec 01 14:59:11 box:dns/waitfordns resolveIp: Checking A for gps.DOMAIN.de at 2001:1680:101:1::2
Dec 01 14:59:16 box:dns/waitfordns resolveIp: No A. Checking CNAME for gps.DOMAIN.de at 2001:1680:101:1::2
Dec 01 14:59:21 box:dns/waitfordns isChangeSynced: NS ns1.DOMAIN.de (2001:1680:101:1::2) not resolving gps.DOMAIN.de (A): Error: queryCname ETIMEOUT gps.DOMAIN.de. Ignoring
Dec 01 14:59:21 box:dns/waitfordns waitForDns: gps.DOMAIN.de at ns ns1.DOMAIN.de: done
Dec 01 14:59:21 box:dns/waitfordns resolveIp: Checking A for gps.DOMAIN.de at 5.79.97.178
Dec 01 14:59:21 box:dns/waitfordns isChangeSynced: gps.DOMAIN.de (A) was resolved to 123.123.123.123 at NS ns2.DOMAIN.de (5.79.97.178). Expecting 123.123.123.123. Match true
Dec 01 14:59:21 box:dns/waitfordns resolveIp: Checking A for gps.DOMAIN.de at 2001:1af8:4700:a120:4::2
Dec 01 14:59:26 box:dns/waitfordns resolveIp: No A. Checking CNAME for gps.DOMAIN.de at 2001:1af8:4700:a120:4::2
Dec 01 14:59:31 box:dns/waitfordns isChangeSynced: NS ns2.DOMAIN.de (2001:1af8:4700:a120:4::2) not resolving gps.DOMAIN.de (A): Error: queryCname ETIMEOUT gps.DOMAIN.de. Ignoring
Dec 01 14:59:31 box:dns/waitfordns waitForDns: gps.DOMAIN.de at ns ns2.DOMAIN.de: done
Dec 01 14:59:31 box:dns/waitfordns resolveIp: Checking A for gps.DOMAIN.de at 94.130.74.45
Dec 01 14:59:31 box:dns/waitfordns isChangeSynced: gps.DOMAIN.de (A) was resolved to 123.123.123.123 at NS ns3.DOMAIN.de (94.130.74.45). Expecting 123.123.123.123. Match true
Dec 01 14:59:31 box:dns/waitfordns resolveIp: Checking A for gps.DOMAIN.de at 2a01:4f8:c0c:289d::2
Dec 01 14:59:36 box:dns/waitfordns resolveIp: No A. Checking CNAME for gps.DOMAIN.de at 2a01:4f8:c0c:289d::2
Dec 01 14:59:41 box:dns/waitfordns isChangeSynced: NS ns3.DOMAIN.de (2a01:4f8:c0c:289d::2) not resolving gps.DOMAIN.de (A): Error: queryCname ETIMEOUT gps.DOMAIN.de. Ignoring
Dec 01 14:59:41 box:dns/waitfordns waitForDns: gps.DOMAIN.de at ns ns3.DOMAIN.de: done
Dec 01 14:59:41 box:dns/waitfordns waitForDns: gps.DOMAIN.de has propagated
Dec 01 14:59:41 box:tasks updating task 3509 with: {"message":"Waiting for propagation of gps.osmand.DOMAIN.de"}
Dec 01 14:59:41 box:dns/waitfordns waitForDns: nameservers are ["ns1.DOMAIN.de","ns2.DOMAIN.de","ns3.DOMAIN.de"]
Dec 01 14:59:41 box:dns/waitfordns waitForDns: waiting for gps.osmand.DOMAIN.de to be 123.123.123.123 in zone DOMAIN.de
Dec 01 14:59:41 box:dns/waitfordns resolveIp: Checking A for gps.osmand.DOMAIN.de at 456.456.456.465
Dec 01 14:59:41 box:dns/waitfordns isChangeSynced: gps.osmand.DOMAIN.de (A) was resolved to 123.123.123.123 at NS ns1.DOMAIN.de (456.456.456.465). Expecting 123.123.123.123. Match true
Dec 01 14:59:41 box:dns/waitfordns resolveIp: Checking A for gps.osmand.DOMAIN.de at 2001:1680:101:1::2
Dec 01 14:59:46 box:dns/waitfordns resolveIp: No A. Checking CNAME for gps.osmand.DOMAIN.de at 2001:1680:101:1::2
Dec 01 14:59:51 box:dns/waitfordns isChangeSynced: NS ns1.DOMAIN.de (2001:1680:101:1::2) not resolving gps.osmand.DOMAIN.de (A): Error: queryCname ETIMEOUT gps.osmand.DOMAIN.de. Ignoring
Dec 01 14:59:51 box:dns/waitfordns waitForDns: gps.osmand.DOMAIN.de at ns ns1.DOMAIN.de: done
Dec 01 14:59:51 box:dns/waitfordns resolveIp: Checking A for gps.osmand.DOMAIN.de at 5.79.97.178
Dec 01 14:59:51 box:dns/waitfordns isChangeSynced: gps.osmand.DOMAIN.de (A) was resolved to 123.123.123.123 at NS ns2.DOMAIN.de (5.79.97.178). Expecting 123.123.123.123. Match true
Dec 01 14:59:51 box:dns/waitfordns resolveIp: Checking A for gps.osmand.DOMAIN.de at 2001:1af8:4700:a120:4::2
Dec 01 14:59:56 box:dns/waitfordns resolveIp: No A. Checking CNAME for gps.osmand.DOMAIN.de at 2001:1af8:4700:a120:4::2
Dec 01 15:00:01 box:dns/waitfordns isChangeSynced: NS ns2.DOMAIN.de (2001:1af8:4700:a120:4::2) not resolving gps.osmand.DOMAIN.de (A): Error: queryCname ETIMEOUT gps.osmand.DOMAIN.de. Ignoring
Dec 01 15:00:01 box:dns/waitfordns waitForDns: gps.osmand.DOMAIN.de at ns ns2.DOMAIN.de: done
Dec 01 15:00:01 box:dns/waitfordns resolveIp: Checking A for gps.osmand.DOMAIN.de at 94.130.74.45
Dec 01 15:00:01 box:dns/waitfordns isChangeSynced: gps.osmand.DOMAIN.de (A) was resolved to 123.123.123.123 at NS ns3.DOMAIN.de (94.130.74.45). Expecting 123.123.123.123. Match true
Dec 01 15:00:01 box:dns/waitfordns resolveIp: Checking A for gps.osmand.DOMAIN.de at 2a01:4f8:c0c:289d::2
Dec 01 15:00:06 box:dns/waitfordns resolveIp: No A. Checking CNAME for gps.osmand.DOMAIN.de at 2a01:4f8:c0c:289d::2
Dec 01 15:00:11 box:dns/waitfordns isChangeSynced: NS ns3.DOMAIN.de (2a01:4f8:c0c:289d::2) not resolving gps.osmand.DOMAIN.de (A): Error: queryCname ETIMEOUT gps.osmand.DOMAIN.de. Ignoring
Dec 01 15:00:11 box:dns/waitfordns waitForDns: gps.osmand.DOMAIN.de at ns ns3.DOMAIN.de: done
Dec 01 15:00:11 box:dns/waitfordns waitForDns: gps.osmand.DOMAIN.de has propagated
Dec 01 15:00:11 box:tasks updating task 3509 with: {"percent":95,"message":"Configuring reverse proxy"}
Dec 01 15:00:11 box:shell reverseproxy: openssl x509 -noout -subject -issuer
Dec 01 15:00:11 box:reverseproxy providerMatches: subject=CN = gps.DOMAIN.de domain=gps.DOMAIN.de issuer=C = US, O = Let's Encrypt, CN = E7 wildcard=false/false prod=true/true issuerMismatch=false wildcardMismatch=false match=true
Dec 01 15:00:11 box:shell reverseproxy: openssl x509 -startdate -enddate -subject -noout
Dec 01 15:00:11 box:reverseproxy ensureCertificate: gps.DOMAIN.de acme cert exists and is up to date
Dec 01 15:00:11 box:reverseproxy expiryDate: subject=CN = gps.DOMAIN.de notBefore=Nov 11 13:11:57 2025 GMT notAfter=Feb 9 13:11:56 2026 GMT daysLeft=69.96648200231482
Dec 01 15:00:11 box:reverseproxy needsRenewal: false. force: false
Dec 01 15:00:11 box:shell reverseproxy: openssl x509 -noout -subject -issuer
Dec 01 15:00:11 box:reverseproxy providerMatches: subject=CN = gps.osmand.DOMAIN.de domain=gps.osmand.DOMAIN.de issuer=C = US, O = Let's Encrypt, CN = E7 wildcard=false/false prod=true/true issuerMismatch=false wildcardMismatch=false match=true
Dec 01 15:00:11 box:shell reverseproxy: openssl x509 -startdate -enddate -subject -noout
Dec 01 15:00:12 box:reverseproxy ensureCertificate: gps.osmand.DOMAIN.de acme cert exists and is up to date
Dec 01 15:00:12 box:reverseproxy expiryDate: subject=CN = gps.osmand.DOMAIN.de notBefore=Nov 11 13:12:29 2025 GMT notAfter=Feb 9 13:12:28 2026 GMT daysLeft=69.9668517824074
Dec 01 15:00:12 box:reverseproxy needsRenewal: false. force: false
Dec 01 15:00:12 box:reverseproxy writeAppLocationNginxConfig: writing config for "gps.DOMAIN.de" to /home/yellowtent/platformdata/nginx/applications/c9964b52-**************-2d94664aa2ef/gps.DOMAIN.de.conf with options {"sourceDir":"/home/yellowtent/box","vhost":"gps.DOMAIN.de","hasIPv6":true,"ip":"172.18.17.203","port":8082,"endpoint":"app","redirectTo":null,"certFilePath":"/home/yellowtent/platformdata/nginx/cert/gps.DOMAIN.de.cert","keyFilePath":"/home/yellowtent/platformdata/nginx/cert/gps.DOMAIN.de.key","robotsTxtQuoted":"\"# Disable search engine indexing\\n\\nUser-agent: *\\nDisallow: /\"","cspQuoted":null,"hideHeaders":[],"proxyAuth":{"enabled":false,"id":"c9964b52-**************-2d94664aa2ef","location":"/"},"upstreamUri":"","hstsPreload":false}
Dec 01 15:00:12 box:reverseproxy writeAppLocationNginxConfig: writing config for "gps.osmand.DOMAIN.de" to /home/yellowtent/platformdata/nginx/applications/c9964b52-**************-2d94664aa2ef/gps.osmand.DOMAIN.de.conf with options {"sourceDir":"/home/yellowtent/box","vhost":"gps.osmand.DOMAIN.de","hasIPv6":true,"ip":"172.18.17.203","port":5055,"endpoint":"app","redirectTo":null,"certFilePath":"/home/yellowtent/platformdata/nginx/cert/gps.osmand.DOMAIN.de.cert","keyFilePath":"/home/yellowtent/platformdata/nginx/cert/gps.osmand.DOMAIN.de.key","robotsTxtQuoted":"\"# Disable search engine indexing\\n\\nUser-agent: *\\nDisallow: /\"","cspQuoted":null,"hideHeaders":[],"proxyAuth":{"enabled":false},"upstreamUri":"","hstsPreload":false}
Dec 01 15:00:12 box:shell reverseproxy: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/restartservice.sh nginx
Dec 01 15:00:12 box:tasks updating task 3509 with: {"percent":100,"message":"Done"}
Dec 01 15:00:12 box:tasks setCompleted - 3509: {"result":null,"error":null,"percent":100}
Dec 01 15:00:12 box:tasks updating task 3509 with: {"completed":true,"result":null,"error":null,"percent":100}
Dec 01 15:00:12 Exiting with code 0
Dec 01 15:00:12 box:taskworker Task took 521.525 seconds
That's not Traccar logs.
I can't find the traccar_logs! Where are they located in the Cloudron container? Do you happen to know?
I also installed it on a freshly installed server with Ubuntu / Cloudron / Traccar, and as I said, nothing worked there either. I'm kind of stuck.
No idea what the Cloudron is.
Cloudron is a Docker program (www.cloudron.io).
Is it possible that I haven't enabled any logs in my configuration?
<entry key="logger.console">true</entry>
<entry key="logger.queries">false</entry>
<entry key="logger.level">config</entry>
<entry key="logger.fullStackTraces">true</entry>
If you're using the official docker image, logs should be in /opt/traccar/logs.
Hello,
No, I checked the terminal logs, and there are no logs. That's really confusing me.
Like I said, I don't understand why it's no longer working on two different data centers.
I set up a new instance for testing. I couldn't even activate it with a single device. And everything has always worked perfectly on the production instance. It's been running flawlessly for over a year.
Hello,
After the latest update, none of my devices are working with the Traccar Server app using Cloudron.io.
I'm using Cloudron.io to run Traccar Server.
All my devices are currently offline. There should always be at least 2-3 devices online. I have absolutely no idea what's causing this. As far as I can tell, the client isn't displaying any error messages. I've attached some screenshots.
If you need any further assistance, please let me know!
I'm using Ubuntu with Cloudron.io. Traccar Server is the latest version.
The Traccar Client is also up to date.
As a test, I installed Cloudron.io with Traccar on a fresh system, but the client/device remains offline there as well.
Has anyone else experienced this?
Best regards, Cliff