There are two FreePBX Notices on our FreePBX System Status page that just will not go away or give us the ability to delete / clear. One is a “1 extension/trunk has weak secret” message, although the extension being referred to is no longer in existence. Another one is a “Failed to send online update email” message, despite us adding a valid email address and despite us being able to receive emails. There is no red x or red - next to either of these messages. Both messages are about 4 days old. We have rebooted our server several times since then and have made many changes since these two messages.
Check the weakpassword detection module of FreePBX. It should indicate which extension has the weak password. You may have to add the extension with a strong password then delete it to sync everything.
Under General Settings is the email account for FreePBX updates. Check if it is correct.
Yes, we have tried recreating the extension in question with strong password and deleting it. In fact, we have done it multiple times with no success. The Weak Password Detection module does not detect any extension with weak passwords yet the notice will not go away.
As far as update goes, yes, we have checked the email address and yes, we are receiving update emails yet the notice will not go away either.
There is no red x or red - next to either of these messages. Both messages are about 4 days old. We have rebooted our server several times since then and have made many changes since these two messages.
Is there a back door for these notices where we can go and clear them out from some config file maybe?
Yes, we have tried clearing cache, tried different browsers and even tried different computers – all with no success.
There is no red x or red - next to either of these messages. Both messages are about 5 days old now. We have rebooted our server several times since then and have made many changes since these two messages. Other notices and messages have come and gone away too, but these two won’t!
Is there a back door for these notices where we can go and clear them out from some config file maybe?
what you report is odd, especially if you have recreated the extension (not that you should have to do that).
Those warnings should be going away, that is not normal behavior.
You can always resort to going into the notification table in the database and deleting the corresponding rows. It will be obvious which ones they are.