But I understand that the only problem you have is with the deletion of on cluster node, that all the other actions like modify firewall policy, install, etc. go fine, is it correct?
In the screenshot supplied, can you show us the information in the API request just below the one that you show?
Hello,
The forbidden error is normal, it is due to a confirmation token required in several API calls.
¿Can you show us the content of the second API call that shows errors to?
¿What errors can you see the error logs in the FWCloud-API?
Sorry us, we forgot to add the filter to this function.
A new patch release (2.0.16) is cooking now in our CI, it will be available in a few minutes.
Please, let me know if with it the problem is solved.
We have published a new patch release that solves this problems.
Please, update your FWCloud installation and let me know if this patch release solves your problema.
¿Te estaba funcionando antes del cambio de versión?
Hemos actualizado el paquete OpenGPG de la versión 5.11.2 a la 6.0.1, puede que si antes te funcionaba este sea el motivo.
Hi,
It is a bug in the policy compilation process.
I'm going to generate a issue related with this and we will generate a patch release in order to solve it.
Let us a couple of days for solve it and thank you very much for the report!
Thanks to you.
Please, report any other issue that you detect and we will solve as soon as possible.
Help from community is very appreciated and helps us create great software tools as FWCloud.
I think that it is a problem with de `localhost` resolution.
We have solved in the new versions, but you can not update for it.
Can you print here the content of your /etc/hosts file ?
That error is normal because the `fwcloud` database already exists.
Let's try the next ...
As the `fwcloud` user, execute the next commands:
Then access again the FWCloud user interface and update the other FWCloud modules.
As an alternative solution until we release the patch release (on Monday) you can create one script rule with the code you need.
That is, temporarily disable the current rule and create up or below a new script rule with the code:
Hi,
It seems that is a bug introduced in the last update.
Please, let us some time to review it and generate a new patch version that solves it.
I'll inform you as soon as it is solved, in a few days.
Greetings.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.