Posts made by michael.day_7391

@rhessinger Windows server 2019. I took a screenshot at the end of the installation as proof it was giving the wrong command, and yes, that is the machine account in the image.

Thanks, re-adding the acl with the user set to NETWORKSERVICE worked.

Maybe it's just me, but if the web UI knows the server is running as NETWORKSERVICE, shouldn't the command it gives you in the web UI at the end of the setup process use the NETWORKSERVICE, and not give you the incorrect command using the computer account name?

I did assume that the instructions it gave me were valid, and that assumption turned out to be false.

I have followed the directions here: https://docs.inedo.com/docs/installation/windows/web/https-support

When adding the https cert in ProGet web UI, it only gave me one command to run on the command line:

netsh http add urlacl url=https://*:443/ user="MYDOMAIN\PROGET-SERVER$"

I thought this was strange because the docs say to use NetworkService, not the machine account name for the netsh binding.

Then when I clicked OK, suddently I get ERR_CONNECTION_CLOSED in the web browser even after opening with the url https://PROGET-SERVER-URL

Windows event viewer shows event id 1000
Category: Microsoft.AspNetCore.Server.Kestrel EventId: 0 Overriding address(es) 'http://*:8624, https://*:443'. Binding to endpoints defined via IConfiguration and/or UseKestrel() instead.

I tried following the docs further and adding this command, but the server still does not start

netsh http add sslcert hostnameport=proget-hostname.mydomain.com:443 certhash=VALID_HASH certstorename=My appid="{VALID_GUID}"

When I attemp to keep following the documentation and bind NetworkService, it fails because the machine account bound through the command the web UI had me run has already bound:

netsh http add urlacl url=https://*:443/ user="NETWORK SERVICE"

Url reservation add failed, Error: 183
Cannot create a file when that file already exists.

Here is the relevant data that was added to proget.config

<WebServer Enabled="true" Urls="http://*:8624;https://*:443" Subject="proget-url.mydomain.com" Store="My" Location="LocalMachine" AllowInvalid="True" UseHttpsRedirection="True" />

Thanks. I've installed certificates on our domain controllers, and now I can connect properly with LDAPS and login via my domain account.

So attempting imports from Artifactory here are the results:

1. Docker import : succeeded (using administrator username and password). It downloaded all the images into ProGet. Strangely enough, when I look at the Artifactory logs, it appears ProGet did not download as administrator, it downloaded as anonymous!
   "2026-02-03T17:16:39.409Z|42aa2e4a419b3fedad8559b05a1a241d|10.2.2.2|anonymous|GET|/api/docker/docker-local/v2/redis/blobs/sha256%3A95e910c2a21348907d21bb294dc886ab3160fd44dedfbc8aa872641185e6285e|200|-1|1002978|7|ProGet/25.0.19.14 (Microsoft Windows NT 10.0.17763.0)"

2. RPM Import: failed (using administrator username and password). Artifactory returns 403. Looking at artifactory log, it appears that ProGet is sending 'anonymous' instead of the credentials I gave it as evidenced by this artifactory log:
   "2026-02-03T17:24:55.659Z|e671ac4eeb05b7cb3a8b87684e1e2e15|10.2.2.2|anonymous|GET|/api/storage/node-exporter|403|-1|55|4|ProGet/25.0.19.14 (Microsoft Windows NT 10.0.17763.0)"

3. Helm Import: failed (using administrator username and password). The import screen did not show the helm repo in Artifactory. The list was empty, so import could not even be attempted.

I have solved the SSL issue by allowing firewall access to CRLs, however, now the import is failing because it can't find the artifactory local repository.

In artifactory, I have a local repo called "cozy-proxy" of type HelmOCI.

In Proget I have created a new feed of type Helm. I am connecting with the "Import packages from Artifactory" option, and using my full administrator credentials with username/password authentication.

When I get to the dropdown list that asks which artifactory local repository to import, the dropdown list is blank, and if I type "cozy-proxy" it doesn't find it.

@atripp said in Error importing from Artifactory: The SSL connection could not be established, see inner exception.:

Invoke-WebRequest

I was able to determine that the cause of the problem is that Windows, in an offline environment is unable to check certificate revocation, even when the root cert is added to the trusted root certification authorities store via GPO. Windows doesn't include LetsEncrypt certs in their trust by default.

Apparently, Chrome, RPM, docker, and Linux all automatically include LetsEncrypt certs, which is why the native docker clients, rpm clients, and chrome browser all connect without cert errors.

I have tried your suggestion, but It's not working. I've added a standard connector to the artifactory server, but I do not get any helpful errors in the log.

Unfortunately, the docker connector does not allow image browsing, so you have to type the image in the search path. It's not obvious what path I should check.

Connector: https://docker.artifactory.mydomain.com/

Artifactory lists file URL as https://docker.artifactory.mydomain.com/artifactory/docker-local/beats/filebeat/9.2.4/

I have tried the following searches which all fail:
artifactory/docker-local/beats/filebeat/9.2.4/
artifactory/docker-local/beats/filebeat:9.2.4
docker-local/beats/filebeat/9.2.4/
docker-local/beats/filebeat:9.2.4/
beats/filebeat/9.2.4/
beats/filebeat:9.2.4
filebeat/9.2.4/
filebeat:9.2.4

None of these searches log an errors in ProGet, so I still cannot tell why the SSL is failing...

Connector Note: Unfortunately, one or more connectors do not support third-party searching of their container registry, so you won't see any results from it, as you may expect. However, if you enter the exact repository name as the search term, it will display in the results.

No Images were found that matched "beats/filebeat:9.2.4".

Thanks, that worked!

We've had problems with this repo before as directory browsing isn't allowed due to the fact it's hosted on S3, so it breaks some software if you just put in the folder path. I guess ProGet is properly just appending the usual location of the repodata file instead of requiring the ability to browse the root folder.

I have setup a docker feed, and am attempting to use the import images option. When I choose artifactory, and enter the url and credentials, and click "Select Feed" I get the following error:

The SSL connection could not be established, see inner exception.

I'm not sure what inner exception I'm supposed to be seeing.
I cannot find any logs in the Administration section under the diagnostic center or the additional logs and events sections related to this error. It does not get logged at all, other than in the popup window, and the stack trace that I've seen in other posts on this forum about the error is missing.

The certificate on the artifactory server is valid, and issued by LetsEncrypt, and is trusted by the operating system. I can open the artifactory url I'm using in the web browser on the Proget Windows Server 2019 server and I do not see any certificate errors.

We actually don't have LDAPS enabled on our servers, so that would not work either. I'll go get some certs installed and enable LDAPS though, since ProGet doesn't seem to support the strong authentication (StarTLS) for regular LDAP.

Proget 2025.19 on Windows Server 2019

I have configured a feed for RPMs, and added the following connector: https://prod-cdn.packages.k8s.io/repositories/isv:/kubernetes:/core:/stable:/v1.31/rpm/repodata/repomd.xml

I have also tried the url https://prod-cdn.packages.k8s.io/repositories/isv%3A/kubernetes%3A/core%3A/stable%3A/v1.31/rpm/repodata/repomd.xml just in case the url parser was getting confused by the colons in the path, and although this also works in a web browser, it still produces the 403 forbidden error.

I can connect to and mirror this repo with our existing Artifactory system with no issues. I can also open that URL in a web browser (on the ProGet server) and retrieve a valid repomd.xml file. so I know that there is no connectivity issue.

I left authentication as anonymous.

However, ProGet returns a 403 forbidden error when I try.

Local index file update failure: The remote server returned an error: (403) Forbidden.

System.Net.WebException: The remote server returned an error: (403) Forbidden.
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location ---
   at System.Net.WebRequest.GetResponseAsync()
   at Inedo.ProGet.GlobalExtensions.GetResponseAsync(HttpWebRequest request, CancellationToken cancellationToken)
   at Inedo.ProGet.Feeds.Connector.GetDirectResponseAsync(String url, CancellationToken cancellationToken)
   at Inedo.ProGet.Feeds.Connector.GetCachedResponseAsync(String url, CancellationToken cancellationToken)
   at Inedo.ProGet.Feeds.Connector.GetCachedTextReaderAsync(String url, Boolean bufferEntireResponse, CancellationToken cancellationToken)
   at Inedo.ProGet.Feeds.Rpm.RpmConnector.UpdateIndexAsync(RpmConnectorIndex localIndex)
   at Inedo.ProGet.Feeds.Rpm.RpmConnector.GetAndUpdateIndexAsync()
   at Inedo.ProGet.Feeds.Rpm.RpmConnector.Inedo.ProGet.Feeds.ILocalIndexFileConnector.UpdateIndexAsync(CancellationToken cancellationToken)
   at Inedo.ProGet.Feeds.CachedIndexFileMan.UpdateConnectorIndexAsync(Int32 connectorId, CancellationToken cancellationToken)

::Connector Error on 2026-01-27 9:54:34 AM::

I have downloaded ProGet 2025.0.19 and was able to successfully change the location for that last setting. Thanks.

It appears the issue is that we are running regular LDAP with strong authentication enforced via group policy as part of the server hardening, and ProGet does not seems to support that. Without StarTLS or other method, it won't allow the connection.

bindResponse(201) strongAuthRequired (00002028: LdapErr: DSID-0C090346, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection

@atripp

Yes, that is exactly what we are doing, proxying public Rocky Linux repositories to an internal network that has no internet connectivity.

Our setup is very standard for a product like this. Program is installed on c:, all artifacts go on a different drive to avoid filling up c: and accidentally crashing the server.

To be honest, I was a little surprised that the installer just automatically put the artifact locations on the OS/program drive. This is not standard at all. Most products will give you an option for the data storage location being separate from the program executables during installation.

@atripp said in An error occurred in the web application: Property set method not found.:

Hi @michael-day_7391 ,

It looks like this was an oversight, and this value cannot be configured. However, we will fix that via PG-3203 in the upcoming maintenance release on Friday.

Thanks,
Alana

If I use the server now with that setting pointing to the wrong drive, and we start caching files in that location, can I move them after the fix is implemented?

Eg:
-Change location in UI
-Shut down service
-Move files to new location
-Start up service

ProGet 2025.18 running on Windows Server 2019

https://docs.inedo.com/docs/installation/security-ldap-active-directory/various-ldap-ldap-active-directory

I have followed those docs. When I get to step 3, and try to search for any group in my AD domain, the search never completes, and only the built in "Administrators" group shows up.

I have also tried creating a new AD domain connection using a service account credentials. I can add permissions for users, and the groups shows up properly, but when I test the login using the login test to try to get my user account to login, it fails with no error message. I also cannot login properly using that same AD account if I logout of the built-in Admin account and try to login with the AD account.

I get the following error in the ProGet web UI when attempting to change the Storage.LocalStoragePath property from C:\ProgramData\ProGet\LocalStorage to D:\ProgramData\ProGet\LocalStorage

Proget Version is Version 2025.18 (Build 12) I used the Windows offline installer to install and am running on Windows Server 2019.

An error occurred in the web application: Property set method not found.

URL: http://localhost:8624/0x44/proget/Inedo.ProGet.WebApplication.Pages.Administration.AdvancedSettingsPage/ChangeSetting
Referrer: http://localhost:8624/administration/advanced-settings
User: (unknown)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36
IP Address: ::1
Stack trace:    at System.Reflection.RuntimePropertyInfo.SetValue(Object obj, Object value, BindingFlags invokeAttr, Binder binder, Object[] index, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.SetValue(Object obj, Object value, Object[] index)
   at Inedo.ProGet.WebApplication.Pages.Administration.AdvancedSettingsPage.ConfigSetting.set_Value(Object value)
   at Inedo.ProGet.WebApplication.Pages.Administration.AdvancedSettingsPage.ChangeSetting(String name, Object newValue)
   at InvokeStub_AdvancedSettingsPage.ChangeSetting(Object, Span`1)
   at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

::Web Error on 2026-01-22 10:54:59 AM::