ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Troubleshooting Issues with Nessus Plugin Updates that Traverse a ProxySG
Article ID: 169138
ProxySG Software - SGOS
Unable to update Nessus Vulnerability Assessment Tool via ProxySG in Explicit Connection.
Nessus Plugin Feed server IP: 184.108.40.206
E.g. # nessuscli update --all ----- Fetching the newest updates from 220.127.116.11 ----- [error] Could not connect to 18.104.22.168 through proxy <ProxySG IP: 8080 [error] Nessus Plugins: Failed to send HTTP request to 22.214.171.124 Nessus Plugins: Failed
[error] Could not connect to 126.96.36.199 through proxy <ProxySG IP: 8080 [error] Nessus Core Components: Failed to send HTTP request to 188.8.131.52 Nessus Core Components: Failed
* Failed to update Nessus Plugins * Failed to update Nessus Core Components
Packet capture shows request with user-agent string Nessus/* and 406 Response. Reason is because the http CONNECT request header syntax is not acceptable. It is not accepted and 406 Response will be sent by ProxySG immediately without applying policy rules.