FSPBX replication - files/folders

In a previous post you outlined the batch file to sync the database for a HA setup.

Would you consider sharing a definitive list of folders you recomment sync with Syncthing as well, including the dehydrated folder in /etc and /etc/nginx as well as the various /var folders for fspbx, fusionpbx, and freeswitch?

pbxgeek said:

Here are the most essential folders to sync. You can add any other folders you may find useful, too.

Code:

/usr/share/freeswitch/sounds/music

/var/cache/fusionpbx

/var/lib/freeswitch/recordings

/var/lib/freeswitch/storage

/var/www/fspbx/public/resources/templates/provision/

Click to expand...

Ok thank you for that list, I'll try these out.

Now how did you deal with the certs in both fusionpbx folder and dehydrated?

I ended up synching /etc/dehydrated and /etc/nginx in order for the certs to be present in both servers and for the .env file to use my FQDN

However it took a while to figure out i had to create move both /etc/dehydrated and /etc/nginx folders and create symlinks in order to sync those because permissions would not allow syncing.

After some 5 days of experimenting and not taking notes I think i have certs working. I think this chat would benefit from a full description to run HA database and files via synch.

alright...synching these system folders like /etc/dehydrated or even /usr/share/freeswitch/sounds/music is proving complicated.
I'm getting errors that write privilidge is not available, something like
Notice
2025-10-27 15:14:23: Failed to create folder root directory: mkdir /var/www/html/syncthing_test: permission denied
2025-10-27 15:14:23: Error on folder "/var/www/html/syncthing_test" (fcttg-ia4dg): folder path missing

I tried to change folder permissions, user permission / groups, chmoding, then i escalated to trying ACLs, then finally went nuclear by disabling hardening in systemd via:

• sudo nano /lib/systemd/system/syncthing@.service, the commingting out the hardeing and reloading
• sudo systemctl daemon-reload

Only removing hardening worked, but i didnt like the idea of removing this protection.
Eventualy found a bit of a compromise by moving these folders, given the new folders access to Syncthing and creating a symlink back to the original folder.

Its pretty messy. @pbxgeek how are you handling syncthing permissions of folders?