Cloudron Forum

No no, I‘ve the actual version running! It‘s just that it stopped working on 29th of November and when I looked into the events i noticed that on this day 1.21 was installed!

@James Thanks! I used 5050 since nearly a year and it worked. I don't know why it stopped working. And now with 5027 is working again. Very strange. Seems there was a change in that traccar version that broke the 5050.

Hi,

since I updated the traccar package on the 29th November, the app doesn't get any more GPS updates. The router still sends them but the packages don't get through to position processing. With 1.22 of the package, the error still persists.

I see these logs:

Jan 22 12:00:37 2026-01-22 10:00:37 INFO: [Tcb5ee177: gotop < MYROUTERIP] 000f383630333032303531343131373137
Jan 22 12:00:37 2026-01-22 10:00:37 WARN: [Tcb5ee177] error -
Jan 22 12:00:37 io.netty.handler.codec.TooLongFrameException: frame length exceeds 1024: 1037 - discarded
Jan 22 12:00:37 at io.netty.handler.codec.DelimiterBasedFrameDecoder.fail(DelimiterBasedFrameDecoder.java:299)
Jan 22 12:00:37 at io.netty.handler.codec.DelimiterBasedFrameDecoder.decode(DelimiterBasedFrameDecoder.java:285)
Jan 22 12:00:37 at io.netty.handler.codec.DelimiterBasedFrameDecoder.decode(DelimiterBasedFrameDecoder.java:215)
Jan 22 12:00:37 at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:530)
Jan 22 12:00:37 at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:469)
Jan 22 12:00:37 at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:290)
Jan 22 12:00:37 at org.traccar.WrapperInboundHandler.channelRead(WrapperInboundHandler.java:56)
Jan 22 12:00:37 at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:356)
Jan 22 12:00:37 at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:93)
Jan 22 12:00:37 at org.traccar.handler.network.StandardLoggingHandler.channelRead(StandardLoggingHandler.java:62)
Jan 22 12:00:37 at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:354)
Jan 22 12:00:37 at org.traccar.handler.network.NetworkMessageHandler.channelRead(NetworkMessageHandler.java:36)
Jan 22 12:00:37 at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:354)
Jan 22 12:00:37 at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1429)
Jan 22 12:00:37 at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:918)
Jan 22 12:00:37 at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:168)
Jan 22 12:00:37 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.handle(AbstractNioChannel.java:445)
Jan 22 12:00:37 at io.netty.channel.nio.NioIoHandler$DefaultNioRegistration.handle(NioIoHandler.java:388)
Jan 22 12:00:37 at io.netty.channel.nio.NioIoHandler.processSelectedKey(NioIoHandler.java:596)
Jan 22 12:00:37 at io.netty.channel.nio.NioIoHandler.processSelectedKeysOptimized(NioIoHandler.java:571)
Jan 22 12:00:37 at io.netty.channel.nio.NioIoHandler.processSelectedKeys(NioIoHandler.java:512)
Jan 22 12:00:37 at io.netty.channel.nio.NioIoHandler.run(NioIoHandler.java:484)
Jan 22 12:00:37 at io.netty.channel.SingleThreadIoEventLoop.runIo(SingleThreadIoEventLoop.java:225)
Jan 22 12:00:37 at io.netty.channel.SingleThreadIoEventLoop.run(SingleThreadIoEventLoop.java:196)
Jan 22 12:00:37 at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:1193)
Jan 22 12:00:37 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
Jan 22 12:00:37 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
Jan 22 12:00:37 at java.base/java.lang.Thread.run(Thread.java:1583)
Jan 22 12:00:37 2026-01-22T10:00:37Z
Jan 22 12:00:37 2026-01-22 10:00:37 INFO: [Tcb5ee177] disconnected

The root cause in the log is that Traccar discards incoming packets due to "TooLongFrameException" – this means that the GPS data is not passed on to position processing and you cannot see any current points in the interface.

On the router side (Teltonika RutX50) wasn't anything changed.

Anyone has an idea?

Greets
Hendrik

I second that question. I could really need Open Cloud, because it seems the first solution on Cloudron to exchange files with a user- and permission management, besides the shitty Nextcloud.

Just stumbled across Silex and definitively want to run it on my cloudron server!

Would love to see it soon in the Cloudron App Store!

Okay, after all it was a browser issue. I deleted all website data in Safari and the error was gone. Sorry I bothered you.

@nebulon

I don't see anything related in the logs when I try to access the documents.

Jan 23 17:00:00 13:M 23 Jan 2025 16:00:00.155 * 10 changes in 300 seconds. Saving...
Jan 23 17:00:00 13:M 23 Jan 2025 16:00:00.155 * Background saving started by pid 250
Jan 23 17:00:00 13:M 23 Jan 2025 16:00:00.257 * Background saving terminated with success
Jan 23 17:00:00 250:C 23 Jan 2025 16:00:00.159 * DB saved on disk
Jan 23 17:00:00 250:C 23 Jan 2025 16:00:00.160 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
Jan 23 17:00:00 [2025-01-23 16:00:00,066] [INFO] [celery.beat] Scheduler: Sending due task Check all e-mail accounts (paperless_mail.tasks.process_mail_accounts)
Jan 23 17:00:00 [2025-01-23 16:00:00,069] [INFO] [celery.worker.strategy] Task paperless_mail.tasks.process_mail_accounts[b10dff4d-3c1e-4f39-8f3e-d55cd16e8e1d] received
Jan 23 17:00:00 [2025-01-23 16:00:00,128] [INFO] [celery.app.trace] Task paperless_mail.tasks.process_mail_accounts[b10dff4d-3c1e-4f39-8f3e-d55cd16e8e1d] succeeded in 0.057467245002044365s: 'No new documents were added.'
Jan 23 17:00:47 Running movescans
Jan 23 17:00:47 mv: cannot stat '/media/Storagebox Scanner/*': No such file or directory
Jan 23 17:05:00 [2025-01-23 16:05:00,054] [INFO] [celery.beat] Scheduler: Sending due task Train the classifier (documents.tasks.train_classifier)
Jan 23 17:05:00 [2025-01-23 16:05:00,057] [INFO] [celery.beat] Scheduler: Sending due task Check and run scheduled workflows (documents.tasks.check_scheduled_workflows)
Jan 23 17:05:00 [2025-01-23 16:05:00,057] [INFO] [celery.worker.strategy] Task documents.tasks.train_classifier[a584d8f6-2fe8-4e6a-969a-59073b8aacc6] received
Jan 23 17:05:00 [2025-01-23 16:05:00,061] [INFO] [celery.worker.strategy] Task documents.tasks.check_scheduled_workflows[71079fb2-98ab-4433-86c0-93d6cd66e0ca] received
Jan 23 17:05:01 13:M 23 Jan 2025 16:05:01.001 * 10 changes in 300 seconds. Saving...
Jan 23 17:05:01 13:M 23 Jan 2025 16:05:01.002 * Background saving started by pid 251
Jan 23 17:05:01 251:C 23 Jan 2025 16:05:01.005 * DB saved on disk
Jan 23 17:05:01 251:C 23 Jan 2025 16:05:01.006 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
Jan 23 17:05:01 13:M 23 Jan 2025 16:05:01.103 * Background saving terminated with success
Jan 23 17:05:01 [2025-01-23 16:05:01,373] [INFO] [paperless.classifier] No updates since last training
Jan 23 17:05:01 [2025-01-23 16:05:01,386] [INFO] [celery.app.trace] Task documents.tasks.train_classifier[a584d8f6-2fe8-4e6a-969a-59073b8aacc6] succeeded in 1.3244988239894155s: None
Jan 23 17:05:01 [2025-01-23 16:05:01,774] [INFO] [celery.app.trace] Task documents.tasks.check_scheduled_workflows[71079fb2-98ab-4433-86c0-93d6cd66e0ca] succeeded in 0.0695804700080771s: None

The movescans error is from a script that moves new scans from my scanner to the import directory. I wonder why the nginx errors are not in there. Also nothing in the box logs:

Jan 23 17:00:00 box:eventlog cleanup: pruning events. creationTime: Fri Oct 25 2024 16:00:00 GMT+0000 (Coordinated Universal Time)
Jan 23 17:00:00 box:janitor Cleaning up expired tokens
Jan 23 17:00:00 box:janitor Cleaned up 0 expired tokens
Jan 23 17:00:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:00:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:00:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:00:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:00:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:00:50 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:01:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:01:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:01:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:01:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:01:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:01:50 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:02:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:02:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:02:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:02:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:02:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:02:50 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:03:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:03:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:03:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:03:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:03:31 box:shell system: swapon --noheadings --raw --bytes --show=type,size,used,name
Jan 23 17:03:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:03:50 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:04:00 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:04:10 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:04:20 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:04:30 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:04:40 box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Jan 23 17:04:41 box:shell logs /usr/bin/sudo -S /home/yellowtent/box/src/scripts/logtail.sh --lines=100 --follow /home/yellowtent/platformdata/logs/8e3f77b8-0c99-49b8-b90c-decbb36c618e/apptask.log /home/yellowtent/platformdata/logs/8e3f77b8-0c99-49b8-b90c-decbb36c618e/app.log /home/yellowtent/platformdata/logs/redis-8e3f77b8-0c99-49b8-b90c-decbb36c618e/app.log
Jan 23 17:04:41 box:shell tail: warning: --retry only effective for the initial open

Hi,

I don't know exactly when it started, but I noticed it yesterday when the package 1.31.3 was the actual version and the package 1.31.4 didn't fix the error. When I click on Documents I get the following error:

Fehler beim Laden der Dokumente: <html>
<head><title>400 Bad Request</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx</center>
</body>
</html>

However accessing the documents with PaperParrot on my iPhone works.

I tried restarting the container as well as the whole host. Any ideas? What happens when I use the repair option in Cloudron? Are all my settings and contents gone?

Regards
Hendrik

• Title: Web-Check on Cloudron

• Main Page: https://web-check.xyz/
• Git: https://github.com/Lissy93/web-check
• Licence: MIT
• Docker: Yes
• Demo: https://web-check.xyz/

• Summary: We give you X-Ray
• Vision for your Website
• In just 20 seconds, you can see what attackers already know

• Notes: Nice tool to check if your websites are correctly and secure configured.