Overview

In the AppManager UI, you may encounter a situation when you create new KerioControl Traffic Rules and these are not getting saved. This happens when new traffic rules would break the Kerio Control Administration. 

Solution

This behavior is caused by incorrect added rules. They are initially saved but KerioControl later rejects them because they would break connectivity. If you have the KerioControl UI open at the same time, you will observe this notification:

In such cases, adjust the rules accordingly to ensure that they won't break the connection.

Summary

In the AppManager UI, users may find that they cannot save new KerioControl Traffic Rules due to the system rejecting rules that could disrupt the Kerio Control Administration's connectivity. This happens when the rules added are incorrect and threaten to break connectivity. Users will see a notification about this in the KerioControl UI and should adjust their rules to ensure they do not disrupt the connection.

FAQ

1. Why can't I save new KerioControl Traffic Rules in AppManager UI?
   New traffic rules are not saved if they are incorrectly set and pose a risk to disrupting the Kerio Control Administration's connectivity.
2. What happens if I try to save a traffic rule that could break connectivity?
   If a rule that could break connectivity is added, it is initially saved but later rejected by KerioControl. A notification will appear in the UI indicating this issue.
3. How can I successfully save new traffic rules in KerioControl?
   To successfully save new traffic rules, ensure that the rules do not disrupt connectivity by adjusting them as needed before saving.