Search results

Hi, Yes, you can configure site 2 site VPN, VPN servers, etc. Any configuration parameter that you can use with OpenVPN can be used in FWCloud when you create your VPN servers or clients.

Can you try it a a new incognito windows ? I think that the problem is in the websocket created between your browser and FWCloud-API.

Hi, Thank you! :-D Answering your questions: 1) Yes, you can change it modifying the LISTEN_PORT environment variable in /opt/fwcloud/websrv/.env 2) Yes, it is possible too, but for this you already have the FWCloud-Websrv process. Regards.

Hi, This is due to the CORS_WHITELIST configuration in the FWCloud-API. Edit the /opt/fwcloud/api/.env file, add the new URL to the CORS_WHITELIST variable and restart FWCloud-API. Please, let me know if this solves your problem.

Ok, then the problem is in the name resolution. Maybe you have to enable access to the DNS service in the INPUT chain of your host and coming from the Docker interface. Can you test it ?

May you test first: ping 8.8.8.8

Great! What about the communication from your Docker container to Internet? Is it going fine now?

Look at the line 230 of your firewall policy load script: $IPTABLES -A INPUT -i ens18 (LAN) -d 192.168.1.22 -m conntrack --ctstate NEW -j ACCEPT You have called your network interface as ens18 (LAN), but this is a mistake, you should call it as it is really named in your firewall, that it is...

Is your FWCloud installation updated to the latest one ? Which versión do you have (you can see it in the About button) ? Can you paste here the fwcloud.sh script for analyze it ? You can get it using the option for see it in the right menu button menu over your firewall.

I think that you have an error in the SNAT rule. If you look at our FWCloud & Docker integration documentation you will see that in the `Translated source` field of the SNAT rule you have to put the IP address of your LAN interface (in your case 192.168.1.22). But in your SNAT rule such field is...

Ok, then the only problem you have is with the communication from the Docker container to Internet, is it correct ?

Ok, the configuration option for IPv4 forwarding is enabled. It is necessary for the containers to Internet communication. Yes, I'm talking about the service provided by the container. For example, if your container is a MySQL its service is supplied by the TCP port 3306 (if you have not mapped...

Ok, let's go first with the service supplied by the Docker container. How are you accessing this service? I need to see to the Options tab of your firewall config.

Ok, great. Now I need to know what do you want to do. Do you want allow Internet access to your Docker container? Do you need to allow access to the service supplied by the Docker container? May you send me screenshots about the policy rules created? I need to see to the options tab of your...

Have you checked that the next option is present in your `/etc/docker/daemon.json` Docker config file? { "iptables": false }

May you send the output of the next command? ip a

It would help us if you explain more about your Docker installation: - Linux Distribution. - Docker versión. - Docker containers. - Etc.

We have released FWCloud-API version 1.7.1. This a patch release with which we have solved a bug in the OpenVPN status history worker process whose role is the harvest of OpenVPN status data form all the OpenVPN servers managed by means of FWCloud-Agent. You can see here more details about the...

We have just published new releases of FWCloud-API 1.7.0, FWCloud-UI 1.6.0 and FWCloud-Agent 1.2.1 whose main goal is the addition of new plugins for add NGFW (Next Generation FireWall) features to the firewalls managed by means of FWCloud. If the communication mechanism that you use for manage...

One of our main objectives for this year was the launch of the MyFWCloud service, a SaaS (Software as a Service) FWCloud version that allows you to have your own and dedicated FWCloud instance in the cloud. And ... yes, we have accomplished it! We have just launched MyFWCloud service, it is...