Nevermind, we solved it. We had to also change the identity of the AppPool in IIS to point to our domain user. After changing it, it was working.

Thanks! I think the restart of IIS App Pool might have helped. I don't see that failure anymore.

Sorry, I meant for "To test, you can try loading that tpage on all nodes and you should not see "Encryption key decryption failure" when refreshing the nodes."

How do you do this?

"I would also make sure to restart the service/web as well. To test, you can try loading that tpage on all nodes and you should not see "Encryption key decryption failure" when refreshing the nodes."

Hi, thank you for your response. How do you do the above?

Hello,

We currently use Windows servers for our ProGet cluster. We tried to add another node to our cluster by installing ProGet on it and copying the same configurations as the other nodes (i.e. DB connection string, encryption key, etc). However, when we did that we noticed that the new node had the following error:

This resulted in instability for our ProGet app (many 403 errors and clicking buttons would result in the login page). We have disabled the node for now. What could the issue be? We have checked everything including the ProGet.config files and they are the same across all nodes. We also checked the permissions for those files and they are also consistent.

@dean-houston Oh okay. Weird. Is there also a path to access the status of each server in the cluster (similar to the one showed /administration/cluster/configure) ?

Hi @dean-houston, as you can see in the screenshot below, I am unable to access that page even from non-localhost endpoint. It just loads indefintely (no error or anything). Is it the port 33237 issue? Or could there be something else? It was working before (like 2-3 days ago).

How would I go about disabling the cluster in this case (since we have just done this on a test environment for now)?

@dean-houston @atripp , for some reason we are not able to load the ProGet Cluster Configuration page after clicking on "More Info":

The page tries to load indefintely as seen in the image.
However, you can see it still displays the status of the cluster. Does that mean there is something wrong with the load balancer?

Nevermind, we solved it. We had to also change the identity of the AppPool in IIS to point to our domain user. After changing it, it was working.

Hi @dean-houston, thank you for the reply. This is happening for every package consistently. After migrating to a shared storage space for all the package files, we are not able to access any of the files from ProGet. Here is the context of that error in more detail (if that helps):

How do you normally define UNC path (for network share) within ProGet settings?

Also, is there a difference between the user running the ProGet Web Service and IIS App pool? By default, the ProGet runs via a Network service, we changed the user to a domain user to run the service. That domain user is able to access the files via network share path on the ProGet machine: