Webserver Protection does not accept licence

Can you share a screenshot of the Licensing page? 

Hello LuCar,

here is the screenshot. The Firewall is part of an HA-Cluster. I also opened a Support Case for this issue but the Support said I should reimage the Firewall. This is no solution for me.

Thanks,

Ben

Does anybody has an idea to get the license accepted by firewall?

Hi Ben,

you could try reset factory defaults, apply the licence then do a restore, might work?
ian

It seems to be a known issue and only a cosmetic issue. So the Webadmin actually is pointing out, the license is not there, but the feature should be 100% functional. 

Can you confirm this? 

Hello LuCar, Hello Ian,

In my case it is not a cosmetic issue, it is a real issue. I build a rule that listen on port 443 with a public certificate. Behind the firewall is a webserver with a self-signed certificate. If I try to access the webserver I see in my browser the self-signed certificate except the public certificate.

To restore the firewall to factory defaults is not really possible because the firewall is far away from my site.

Is there any possibility to start the license sync from the scratch without a factory reset?

Thanks,

Ben

Do you see any kind of reverseproxy.log entries? Is the service loaded? 

Please raise a case and ping the ID to FloSupport

This was a good hint. It seems that the reverseproxy hangs. I restarted the service with "service WAF:restart -ds nosync" and now the reverseproxy is accepting the requests. 

Now the issue is only a cosmetic thing (the rule shows still the licensing warning). 

Many thanks for your help

Ben

Hi Ben, looping in emmosophos who will follow up with you on this as our team wanted to investigate further.

Hi Ben, looping in emmosophos who will follow up with you on this as our team wanted to investigate further.

Hello,

The following Case ID has been created by Ben related to this 04128411. If an ID is created after this issue or a fix is found, I will be updating the thread accordingly.

Regards,

Hello,

This issue was investigated under NC-71443 and is targeted to be resolved on 18.5.1 MR1

Regards,