Syncovery Support Forum

I also had an issue when I was using Fedora. I had to disable SELinux to get Syncovery to work. After disabling SELinux there were no issues with running Syncovery.

I still haven't really understood what SELinux exactly does and how it can be easily configured (i.e. without several days of ...

tobias wrote: Fri Jun 19, 2026 7:21 pm Yes, realtime is not supported on Linux.

I hope to add it in Syncovery 12.

Ah, ok. Thanks!

I just noticed that, even when it's running (started with sudo or not), realtime sync doesn't work. No changes are detected, except in manual or scheduled runs.
It can't be a system limitation of Fedora 44 KDE, because RealTimeSync (from FreeFileSync) automatically detects changes and synchronizes ...

Sure. No problem.
Syncovery was running fine on Kubuntu and still is running without issues on Windows 11 and on my UGreen NAS. I really like it.

sudo ausearch -m avc -ts recent (right after reboot)
returns nothing.
Also, I had already tried the setenforce and that didn't help either.
I'm wondering if it's really SELinux that's causing the issue. After login, I can even start SyncoveryCL without sudo and it works (my account has access to ...

Thank you!
Meanwhile, if you already have the syntax to create the exception, I'd love to see it.
Otherwise, I'll see if I can somehow start the service on login. It doesn't need to be running when I'm not logged in.

To me, it looks like the starts but then immediately exits. It doesn't seem to fail:

sudo systemctl status syncoverycl
● syncoverycl.service - Syncovery Scheduler Service
Loaded: loaded (/etc/systemd/system/syncoverycl.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service ...

This is all that's in the WebGUI.log file:
17.06.2026 20:33:53.697: No port defined for SSL
17.06.2026 20:33:53.697: Starting Web Server
17.06.2026 20:33:53.697: Added binding with IP=localhost and Port=8999
17.06.2026 20:33:53.697: Plain HTTP Port is 8999
17.06.2026 20:33:53.697: Web server IP ...

Ok, I found this in the list of services:

Thank you for the tips, Tobias.
I looked at the SELinux Troubleshooter and there was nothing about Syncovery there.
And I can't find the Syncovery log file (tried searching, but that involves searching through hundreds of thousands of files and folders on my NAS because the shares are mounted under ...