Socket connection error while downloading the content database.

search cancel

Socket connection error while downloading the content database.

book

Article ID: 166920

calendar_today

Updated On:

Products

ProxySG Software - SGOS

Issue/Introduction

The following socket connection error displays when you attempt to download your content filtering database:

Websense download error

Download log:

Websense database download at: 2011/10/25 18:41:43 +0000

Downloading from download.websense.com

Fetching Websense download file

Warning: Socket receive error

Attempting full Websense database download

Downloading from download.websense.com

Fetching Websense download file

ERROR: Socket receive error

Download failed

BCWF download error

Download log:

Blue Coat download at: 2011/10/19 17:11:01 -0500

Downloading from https:https://list.bluecoat.com/bcwf/activity/download/bcwf.db

Requesting initial database

Fetching:

https://list.bluecoat.com/bcwf/activity/download/bcwf.db?installed_version=0

ERROR: Socket connect error

Requesting full database

Fetching:

https://list.bluecoat.com/bcwf/activity/download/bcwf.db

ERROR: Socket connect error

Download failed

Resolution

Please refer to 000013574 (/articles/Solution/Socketconnecterrorwhendownloadingacontentfilterdatabase) to fix this problem. If the problem still persists, please check for the following causes:

1. The socket error occurs when the ProxySG is unable to connect with the content filter download server. Check the routing/network access settings on your ProxySG -- Verify that the gateway is configured correctly in the proxy and also make sure that the configured gateway is the right one to go out to Internet. If the gateway is a firewall, make sure that firewall is not dropping the packet during the content filter download and firewall has the correct rule to allow this traffic. Also, make sure that proxy is routing table especially the static routes are still intact. If the proxy configuration is installed from the backed up configuration, make sure that all the static routes are in place along with the gateway.

2. The same error occurs, if the database download link is incorrect. Verify that you have the accurate link for downloading the content filter database.