| | 316 | |
| | 317 | To enable a UFW application profile, run ufw allow followed by the name of the application profile you want to enable, which you can obtain with a sudo ufw app list command. In the following example, we’re enabling the OpenSSH profile, which will allow all incoming SSH connections on the default SSH port. |
| | 318 | {{{ |
| | 319 | sudo ufw allow “OpenSSH” |
| | 320 | }}} |
| | 321 | {{{ |
| | 322 | Output |
| | 323 | Rule added |
| | 324 | Rule added (v6) |
| | 325 | }}} |
| | 326 | Remember to quote profile names that consist of multiple words, such as '''''Nginx HTTPS.''''' |
| | 327 | |
| | 328 | '''Disable Application Profile''' |
| | 329 | |
| | 330 | To disable an application profile that you had previously set up within UFW, you’ll need to remove its corresponding rule. For example, consider the following output from '''sudo ufw status:''' |
| | 331 | {{{ |
| | 332 | sudo ufw status |
| | 333 | }}} |
| | 334 | |
| | 335 | {{{ |
| | 336 | Output |
| | 337 | Status: active |
| | 338 | |
| | 339 | To Action From |
| | 340 | -- ------ ---- |
| | 341 | OpenSSH ALLOW Anywhere |
| | 342 | Nginx Full ALLOW Anywhere |
| | 343 | OpenSSH (v6) ALLOW Anywhere (v6) |
| | 344 | Nginx Full (v6) ALLOW Anywhere (v6) |
| | 345 | }}} |