Networking service configuration cannot be performed concurrently with an active systemd-networkd service. To enable FreePBX for managing your networking configuration, you’ll need to disable systemd-networkd.
FreePBX17, Debian 12 - Installed on Azure - Does anyone know how to fix this?
I have the same issue when using the Debian Local Cloud image.
What cloud provider are you using?
Does anyone fixed this issue?
Using AWS getting the same error.
Not yet Renato - If you figure it out, please let us know.
This problem is on Azure, AWS and GCP. Has anyone installed this on a non-cloud system?
All, this is where the answer will come from:
Very unlikely, as it doesn’t relate to Asterisk.
@abuislam - is this okay to run if our server hosted in cloud like in AZURE or AWS?
Don’t we get disconnected from SSH?
I don’t know if this will help but you should only manage networking with one set of tools, if this helps
discusses how networkd and networkmanager (which I tend to use) can co-exist without stepping on rhe others foot (basicly run only one at a time). I am not familiar with how sysadmin handles networks but if it is a complete manager as is networkmaner, then stop/disable/mask networkd, or disable sysadmin’s management of the network interfaces.and use networkd.
( Azure, AWS and GCP all use netplan/networkd I believe but depending on how cloudy they are, perhaps don’t have to 
)
Yes, I am seeing this error on System Admin > Network Settings but everything is working fine as expected. I will just leave it and maybe on the next update it will automatically be fixed. Let you know if I encounter any issue.
You will probably also want to disable systemd-networkd-wait-online.service if that is enabled, otherwise it will fail and time out, adding an additional 2 minutes to your boot time. If disabling that causes other problems with some other service, then you will need to do something else, such as leaving it enabled but reducing the timeout to something more reasonable. Maybe 30 seconds.
Won’t start unless systemd-networkd did
I’m running mine on-premise.
@cryptopunk Any updates on this using on premise?
Is there any update on how to solve this problem when hosting on a provider like AWS? I tried installing NetworkManager and then disabling systemd-networkd, but it keeps getting reenabled, and when I masked it and then disabled it, I completely lost access to the instance. It was just a test instance, but some guidance on the steps to swap out systemd-networkd would be appreciated.
don’t disable it, ‘purge’ it