Search results

In order to simplify the FWCloud installation procedure we have created packages for DEB and RPM based Linux distributions. These packages are created automatically every time we publish a new release of FWCloud. DEB and RPM are package management systems used in different Linux distributions...

We have added the next line to the Unit section of the fwcloud-api.service systemd file: It would be available in the next FWCloud-API release. Thank you very much for the feedback.

Hi, May you copy here the logs lines of FWCloud-API (/opt/fwcloud/api/logs/app.log file) that arise when you try to login into de FWCloud-UI web user interface? Best regards.

We have just made public the FWCloud-Agent source code available in its corresponding GitHub repository. FWCloud is an OpenSource project under the GNU Affero General Public License v3. You can install it in your own servers or, alternatively, you can contact us to use our cloud service...

We are very proud to announce the availability of new releases for the main modules that make up FWCloud. These are the new versions for each module: - FWCloud-API 1.8.2 - FWCloud-UI 1.7.0 - FWCloud-Websrv 1.1.2 - FWCloud-Updater 1.1.0 - FWCloud-Agent 1.3.1 There are many new features and...

Thank you very much for your comments. I deduce for them that you have now FWCloud operative, great! :-) The FWCloud Installer script must be executed by root or a sudo user, for this reason it is not necessary to indicate the database password for create the FWCloud required database. If you...

Remove the `/opt/fwcloud` folder and then launch de install script again. Let me know if all goes fine now.

You have to check first that the MariaDB engine is working fine. Can you log into your MariaDB engine and create a new database?

We have been able to install FWCloud by means of FWCloud-Installer in a fresh installed and updated Ubuntu 22.04.2 LTS Server. That is something that we usually verify every time a new release is published, but we checked it again just in case. Are you installing FWCloud in a new server or are...

Hi, We are trying to reproduce the error in a fresh and updated Ubuntu 22.04 LTS. I'll inform you with the results of the tests once we finish them. Thank you for the feedback.

Hi, We have been testing it in our laboratory environment and its going fine. Please, may you give us more details about the problem? Can you include some screenshots about it? Thanks.

Hi, At this moment, the Keepalived plugin will install Keepalived software packages in all cluster's nodes and will create a suggested configuration that you can customize by yourself. In the roadmap for this year we have the addition of a new FWCloud section that will allow Keepalived setup by...

What communications do you want to allow for the Docker containers?

Great!, thank you very much for the answer.

Hi Jeremy, We have already solved the problem with the target x86_64-unknown-linux-musl in the RPM package process generation. Thanks to this it is now possible to install FWCloud-Agent in RHEL7, RHEL8 and many other RPM Linux based distributions. Please, install the new FWCloud-Agent release...

We have just released FWCloud-Agent 1.2.2. This is a patch releases in which we have improved some issues: - IPTables package dependency for both `deb` and `rpm` packages. - GitHub actions `rpm` package generation task for use `--target=x86_64-unknown-linux-musl`. This way the FWCloud-Agent...

We have just released FWCloud-API 1.7.2 and FWCloud-UI 1.6.1. These are patch releases in which we have solved some bugs: - Solved problems with the display of the checking for updates dialog. - Bug in `iptables-save` import procedure when `-p tcp` and `-m tcp` are used at the same time in...

Hi, Yes, in fact we have a GitHub repository with a docker compose file for FWCloud: https://github.com/soltecsis/fwcloud-docker

As you can see in the log, the received packet is a TCP RST (https://www.pico.net/kb/what-is-a-tcp-reset-rst/). Have you checked the communication from this host? Goes it fine?

Who is the owner of the source IP (172.16.1.109) ? Is the FortiGate ? If you try the communication from any other host connected to the same network, goes it fine ?