Protect: My Jetpack Card is Misleading on Pressable

[bobmatyas]

Impacted plugin

Protect

Quick summary

On Pressable and WordPress.com, the Jetpack Protect card in "My Jetpack" says that Auto-firewall is disabled and implies that it is user configurable. However, users can't turn on the feature on the hosts

Steps to reproduce

1. Add a Jetpack Scan plan to a site hosted on Pressable
2. View the My Jetpack Protect card and see that the auto-firewall is grayed out

A clear and concise description of what you expected to happen.

I think that ideally we should communicate that the firewall is turned off / unnecessary on this particular host. I think it should be mentioned on both the card and in the plugin setting so that it isn't confusing if users can't find the setting.

What actually happened

My Jetpack:

Tooltip on My Jetpack implies it is user configurable:

Firewall settings:

Impact

All

Available workarounds?

No but the platform is still usable

If the above answer is "Yes...", outline the workaround.

No response

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

[CodeyGuyDylan]

I opened a PR for this, I just added a new Tooltip for the Protect card in My Jetpack that explains WAF is unsupported for their site and why. I think this solves all the issues brought up here but let me know if I am wrong