Oracle Cloud instance - no tracking data in web UI

I've been a long term user of Traccar (personal use, only two devices) in a free GCP instance for a few years now.
GCP resources are somewhat basic when compared to the Oracle cloud free tier and I recently fell foul of the storage limitations, so I thought I'd try set up an instance there based on there Ampere ARM resources (I've allocated it 2 cores and 4G mem).

Does anyone else deploy Traccar on Oracle?
When I switch the DNS to point to the Oracle instance, I never get any connection from either device showing in the WebUI. I do see some data coming in via the logs - I've attached a copy of when one of the cars was in use yesterday below. The ports are open (both devices are tk103, so 5001) - and if I switch DNS back to the GCP instance they show up immediately, ruling out a problem with the devices surely?

The difference between the two instances is GCP is Debian 11, Mysql and Traccar 5.7. Oracle is Debian 12, MariaDB and Traccar 5.8.
I was thinking it was an issue with using MariaDB and maybe me setting it up wrong or to wait for 5.9 - but I get the same behaviour when using the default H2 method.

Does anyone have any thoughts or ideas? Using the hex decoded/encoder I just get the "Binary cannot be converted" error and I've not had a look further into that yet - it's next on the list but just seeking some community advice too now.

I do also see "out of bounds" messages in the log as follows - which is why I wonder if it's a MariaDB issue and 5.9 may help with the new driver. Why it's showing GPS103 decoder in the error message I'm not sure on though.

2023-07-04 23:32:07  INFO: [Tc71fe2cd] error - begin 21, end 24, length 19 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)
2023-07-04 23:32:07  INFO: [Tc71fe2cd] error - begin 21, end 24, length 9 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)
2023-07-04 23:32:07  INFO: [Tc71fe2cd] error - begin 21, end 24, length 2 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)
2023-07-04 23:32:07  INFO: [Tc71fe2cd] error - begin 21, end 24, length 2 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)
2023-07-04 23:32:07  INFO: [Tc71fe2cd] error - begin 21, end 24, length 23 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)
2023-07-04 23:32:07  INFO: [Tc71fe2cd] error - begin 21, end 24, length 2 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)
2023-07-04 23:32:07  INFO: [Tc71fe2cd] disconnected

2023-07-05 07:20:02  INFO: [Tc083b4b7: tk103 < 87.236.176.51] 474554202f20485454502f312e310d0a486f73743a203133322e3134352e32332e3230353a353030320d0a557365722d4167656e743a204d6f7a696c6c612f352e302028636f6d70617469626c653b20496e7465726e65744d6561737572656d656e742f312e303b202b68747470733a2f2f696e7465726e65742d6d6561737572656d656e742e636f6d2f290d0a436f6e6e656374696f6e3a20636c6f73650d0a4163636570743a202a2f2a0d0a4163636570742d456e636f64696e673a20677a69700d0a0d0a
2023-07-05 07:20:22  INFO: [Tc083b4b7] disconnected
2023-07-05 07:20:34  INFO: [Tf860aef6] connected
2023-07-05 07:20:37  INFO: [Tf860aef6: tk103 < 87.236.176.64] 0000001f000000000000000c476574436c6173734e616d650000000204000000000100
2023-07-05 07:20:40  INFO: [Tf860aef6] disconnected
2023-07-05 07:20:52  INFO: [T25cea99c] connected
2023-07-05 07:20:55  INFO: [T25cea99c: tk103 < 87.236.176.51] 10c00b004c494f523c020000ffffffff00000200d1587355509195954997b6e611ea26c60789cd434c39118f44459078909ea0fc4ecade1d100300005a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a
2023-07-05 07:20:58  INFO: [T25cea99c] disconnected
2023-07-05 07:21:10  INFO: [T66e3fe96] connected
2023-07-05 07:21:13  INFO: [T66e3fe96: tk103 < 87.236.176.39] 05000b03100000004800000001000000b810b8100000000001000000000001000883afe11f5dc91191a408002b14a0fa03000000045d888aeb1cc9119fe808002b10486002000000
2023-07-05 07:21:16  INFO: [T66e3fe96] disconnected
2023-07-05 07:21:28  INFO: [Te098fcd5] connected
2023-07-05 07:21:31  INFO: [Te098fcd5: tk103 < 87.236.176.54] 1201001a0000000000000b00060100110001ff08000155000001
2023-07-05 07:21:34  INFO: [Te098fcd5] disconnected
2023-07-05 07:21:46  INFO: [Te6318c10] connected
2023-07-05 07:21:49  INFO: [Te6318c10: tk103 < 87.236.176.57] 8000002899e4daa40000000000000002000186a3000000030000000000000000000000000000000000000000
2023-07-05 07:21:52  INFO: [Te6318c10] disconnected
2023-07-05 07:22:04  INFO: [T92e467a2] connected
2023-07-05 07:22:07  INFO: [T92e467a2: tk103 < 87.236.176.73] 000000090003000000
2023-07-05 07:22:10  INFO: [T92e467a2] disconnected
2023-07-05 07:22:22  INFO: [T3b5aa191] connected
2023-07-05 07:22:25  INFO: [T3b5aa191: tk103 < 87.236.176.46] 0300002c27e00000000000436f6f6b69653a206d737473686173683d656c746f6e730d0a0100080003000000
2023-07-05 07:22:28  INFO: [T3b5aa191] disconnected
2023-07-05 07:22:40  INFO: [Tc7f614d2] connected
2023-07-05 07:22:43  INFO: [Tc7f614d2: tk103 < 87.236.176.66] 2a310d0a24340d0a696e666f0d0a
2023-07-05 07:22:46  INFO: [Tc7f614d2] disconnected
2023-07-05 07:22:58  INFO: [T3c18364f] connected
2023-07-05 07:23:01  INFO: [T3c18364f: tk103 < 87.236.176.38] 00000031ff534d4272000000000000000000000000000000000000000000000000000100000e00024e54204c4d20302e3132000200
2023-07-05 07:23:04  INFO: [T3c18364f] disconnected
2023-07-05 07:23:04  INFO: [T73f93fd6] connected
2023-07-05 07:23:04  INFO: [T73f93fd6: tk103 < 87.236.176.38] 0000006efe534d4240000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024000400010000000000000000000000000000000000000000000000000000000000000002021002000302031103
2023-07-05 07:23:07  INFO: [T73f93fd6] disconnected
2023-07-05 07:23:19  INFO: [Tf755741c] connected
2023-07-05 07:23:22  INFO: [Tf755741c: tk103 < 87.236.176.45] 16030100fa010000f60303f711d4b8a3f082810f078d1b9595ee1abeb4fe8ae474e631cd44b3cfdcb2e5b620c1b9ab8a8ba00d356f808f9a6a8ac3cf6dc1eb9d9bec5153f302b54d726387a40032c02bc02fc02cc030cca9cca8c009c013c00ac014009c009d002f0035c012000ac023c027003cc007c01100051301130213030100007b000500050100000000000a000a0008001d001700180019000b00020100000d001a0018080404030807080508060401050106010503060302010203ff0100010000120000002b0009080304030303020301003300260024001d00205495efec879cae8799277079338fd751d8c353f1290935b8d0e2b18a5da83071
2023-07-05 07:23:28  INFO: [Tf755741c] disconnected

I tired. But I also only put the traccar server there. No db. Db I kept at home and connected via tailscale

I found it was ok. But the 2nd drive of a day it seemed to kill the vm. I tired turning off the web ui (using another instance at home connected the to same db). That seemed better.

In the end I wrote a python tcp forwarder that would listen to 5002 and send it to a traccar instance at home via tailscale.

Much lower footprint

The data you had in logs is not in the right format for the port 5002, so I suspect that it's not from your device.

Both devices are TK103, so port 5001. I'm not expecting anything from 5002, so that's why I found the GPS103 protocol errors strange.

Nonetheless, I spun up a 2nd instance in Google Cloud, pointed the DNS and it worked straight away.
It's definitely something strange on the Oracle side...

Just as a follow up, I managed to find a work-around...

I'm not entirely happy doing it this way, but I found the only way it would work reliably was by allowing all ingress traffic via the security lists function in OCI and getting familiar with the OS firewall.
Without this, I'd see the device popping up online, but no actual data to map out. Just odd.