Skip to main content

ESET PROTECT repository is not working (8.x – 9.x) - Kennisbank / ESET PROTECT On-prem - ESET Tech Center

ESET PROTECT repository is not working (8.x – 9.x)

Authors list

Issue

Solution


I. Test your connection to the ESET PROTECT repository


Open the link below in your web browser:

If you are given the option to download the metadata file, you are connected to the repository. If you cannot access the repository, contact your system administrator to resolve firewall issues.

Make sure you have HTTP 1.1 enabled when accessing the repository or ESET update servers via third-party proxy. This applies to all products that have access to the ESET repository.

Do not use an IP address to access the ESET repository.


II. Change the repository URL for ESET PROTECT Server(optional - set the repository that uses only ESET servers)

  1.  Open the ESET PROTECT Web Console in your web browser and log in.

  2. Click MoreServer Settings and expand Advanced Settings. In the Repository section, type the ESET PROTECT repository link (http://repositorynocdn.eset.com/v1) into the Server field and click Save to apply the changes.


                                                                                                                  Figure 1-1 

III. Change repository for ESET Management Agent(optional - set the repository that uses only ESET servers)


1. Open the ESET PROTECT Web Console in your web browser and log in.


2. Click Policies.

3. Select the policy, click the agent policy name you need to change, and then select Edit.

                                                                                                                           Figure 2-1 

 

4. Expand Settings Advanced settings. In the Repository section, type the ESET PROTECT repository link (http://repositorynocdn.eset.com/v1) into the Server field. Click Finish.

                                                                                                                            Figure 2-2 

5. Check your connection to the repository again. If your connection continues to fail, proceed to Part IV.

IV. Troubleshooting "Key not valid for use in specified state" in the server trace log


1. In Windows Explorer, navigate to one of the following folders, depending on your operating system:

  • Windows XP/2003: C:\Documents and Settings\Application Data\Microsoft
  • Windows Vista/2008 or later: C:\Users\[Windows User Account Name]\AppData\Roaming\Microsoft

2. In the path above, find and rename the Crypto folder to "Crypto old." If you cannot rename the folder, right-click it, select Copy from the context menu, right-click in the present folder and then select Paste from the context menu (this copy will serve as a backup).

3. After making a backup, delete the original Crypto folder.

4. Restart the ESET PROTECT Server service.

5. The Crypto folder will be re-created automatically, and the connection to the repository should now be functional. Test your connection to the ESET PROTECT repository as described in Part I.


If you are still unable to resolve your issue, contact ESET Technical Support.

Add a comment

Please log in or register to submit a comment.

Need a password reminder?