Hi @stevedennis,
Thanks for the reply. It turns out my default nginx server was intercepting all http traffic and not allowing requests to get to the Proget server.
I solved the issue by disabling the default server (removing it from sites-enabled) and making some config changes to the Proget nginx config file to stop the server from redirecting http traffic to https.
I have created a Proget instance with a NuGet feed and am trying to access the packages hosted there. However, when I try to access the API endpoint URL provided in the feed, the server returns a 404 error. I'm having difficulty troubleshooting the issue as I'm not sure why the web interface would be accessible, but the API end point would not be. Any help would be much appreciated.
Thanks
Response when attempting to send a GET request to the API endpoint URL:
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.18.0 (Ubuntu)</center>
</body>
</html>
Hi @atripp,
Thanks for the response!
It turns out I was overlooking the fact that the docker container cannot access the files of the host. So the directory was non-existent from the perspective of the ProGet instance. I ended up solving the issue by copying my bulk import directory into the docker container itself, which allowed the bulk import service to detect the directory.
I am attempting to import packages from a feed on a depreciated version of ProGet. I am following the steps outlined in this documentation: https://docs.inedo.com/v1/docs/proget-bulk-import-with-droppath
I have moved the packages from the old feed into a dedicated directory as the documentation states, but I get the error "Directory does not exist on the server, or is otherwise not accessible by the server." when I try to set it as my target directory for import (See image below). The directory exists on the disk and I am able to access it.
I am running ProGet on Linux so there is quite a lack of documentation.
I moved a package directly into the /var/proget/packages folder (as the importer does seem to recognize that directory) to test if the functionality worked and the bulk package importer did not recognize that the package was present.
Looking for guidance on what I am doing wrong here, thanks.