Responses to user support requests. Weekly overview. Part 16.
Q: i’m using version 25.8.22 Pro and i use on one camera a Planer + FTP-Server Upload Node. The Planer is placed behind universal camera and is set to 7:00 start and 19:00 end on all days.
Behind planer node i placed FTP-Upload node. I set IP/Port/Name/Password/Directory with Filename and Type to JPEG with 2 hour interval.
This configuration is running since july 2024 and has nicely uploaded pictures to my NAS, but since january this year it stoped working.
If i now press the button to test connection i got success and a actual picture appears on my NAS, but not automated.
since i set this upload up i only updated xeoma Server and Clients sometimes nothing else is changed NAS / camera…
I can see a message above the setting connection timeout it disappears if i hit test: “TYPE command not accepted”
i checked the logs but only this message appears sometimes: “Aug 29 08:09:17 BRH-NAS-MAIN proftpd[2146776]: 127.0.0.1 (192.168.2.205[192.168.2.205]) – FTP no transfer timeout, disconnected”
the transfer timeout is set by default to 300 seconds in NAS.
A: This seems like a network issue, e.g. a firewall on the FTP server or FTP client side is blocking Xeoma’s attempts to send the JPG file. You may want to carefully check the network setup both on Xeoma’s server and on the NAS.
Q: I am struggling to get TLS working between the in the following setup.
I have my own CA running locally that assigns HTTPS certs.
I wan to use that cert for the TLS handshake between Xeoma client and Server. I get the error “Server certificate is not trusted”
The root CA is trusted on my client device as I can successfully connect to other devices.
Client: ubuntu (installed and auto runs)
Server: ubuntu (headless)
Please advise where i am going wrong, assume the root ca is in the wrong place maybe ?
A: If by CA you mean “Certificate Authority” (the thing that signs certificates) – no, this generally does not matter for Xeoma, only the certificates themselves. Please make sure that:
1) the certificates are either .der or .pem
2) the server has both the PublicCertificate and the PrivateKey files in …/Xeoma/Security/Certificate/Server (where to look for that directory)
3) the client has the same PublicCertificate file in …/Xeoma/Security/Certificate/Client (same directory as above)
See more on this subject here: https://felenasoft.com/xeoma/en/articles/new-feature-secure-tls-connection/#in-Xeoma
Q: I have noticed another thing having to do with recording playback. For instance, I set the calendar to Sept 1, 3:00pm on Camera 1 and start playback. If I click the arrow on the right or left to go to another next camera, version 25.3.5 will switch to that Camera as close a possible to the time where Camera 1 was. However, version 25.8.22 does not. It switches to whatever the last time was that looked at on that camera or sometimes it seems some random position.
A: You can now choose what Xeoma will show you when you switch between archives by going Archive menu -> Start position
If you want the previous behavior, pick “Same time/date position as in a previous archive” from that list.
September 5, 2025