I have setup NuGet.Server 3.3+ on Windows 10 IIS
[Working][1]
I can browse already inited packages on the server
When I try and push a known working package to my server
nuget push webgrease.1.6.0.nupkg -Source http://localhost/NuGetSrv/nuget
I get
I get 404
In fiddler the package is sent it looks to be a security issue on the server when it goes to write the file
I have use not network service / classic app pool and also tried admin account for the app pool
Also tried local c:\somedir and a \server\share
I had the same problem :/
If you can get packages but not add
Make sure you have the application pool set to Integrated and not Classic and your network share will work for pushing packages
If you're working on Azure, #HoopSnake's answer still apply, but its worderd differently.
In the App Service => Application Settings => Managed Pipeline Version set this to Integrated.
Atleast, that's what fixed it for me
Related
I'm running a CI pipeline on Azure DevOps. Part of the release pipeline is deploying a website to our web server (running IIS).
We changed hardware recently and did a fresh install of Windows. Of course I also installed the WebDeploy handlers and everything. But since then, the deployment runs without error, but it doesn't actually update any files. If I publish the website from VS2019, everything is fine.
How would I troubleshoot this?
I forgot to include the new server into the deployment group. Only noticed it when we finally turned off the old server and got the error message that the target was offline.
I have a web app, and I've setup VSTS to create a package in build, and then deploy it using release management.
It puts all of the result in the wwwroot of the site if I look at it in ftp so I get:
/site/wwwroot/
/wwroot
/
This doesn't run and I get a 404 error.
If I use the URL and go say /wwwroot/images/ it returns it just fine.
The app is set to use .net core and I'm doing a self-contained package.
How do I get VSTS release to put the files in the right place and what is the right place ? I can't find any documentation on this anywhere. Everything is to do with Windows.
Also, what linux target should the dotnet application be set to for self-contained? I have it using ubuntu but I'm sure that's wrong and it's something else.
Please use Azure App Service Deploy task with 4.* (preview) version instead, and deploy again:
I had a similar issue and I responded here. Essentially you need to have a startup command pointing to your DLL because Dev Ops deploys the package in a different way than VS.
Deploying .Net Core to Linux WebApps on Azure with DevOps
I try to setup teamcity nuget feed. But when i try download package form nuget server i get next error in VS output window:
when i try get definition of nuget feed i see next:
in Administration / Global settings / Server URL i have valid dmin name of my server. How can i change xml:base attribute in feed definition?
I don't think there is an issue with TeamCity. From what I can see you are hosting TeamCity locally on your development machine and you are successfully downloading your own packages (1st picture). The error that you are seeing in chrome is absolutely fine.
However the issue that it appears you are having is that you have not configured either VisualStudio or your solution in VisualStudio to download from more than one place. The package that is failing is NancyFx which presumably you are not hosting from TeamCity so therefore you need to go and get it from the public NuGet Server. In order to achieve this you either have to configure VisualStudio or your solution file to search multiple package sources.
https://docs.nuget.org/ndocs/tools/package-manager-ui#package-sources
From TeamCity support "Change base URL in FeedService":
It looks like you have a reverse proxy and it is not properly
configured. Please refer to TeamCity HowTo documentation about this:
https://confluence.jetbrains.com/pages/viewpage.action?pageId=74845225#HowTo...-SetUpTeamCitybehindaProxyServer
It seems HTTP proxy does not pass Host header correctly. When browser
makes a request it sets Host to hostname from browser address bar. If
proxy changes Host to something else, or removes it, then feed will
have URLs pointing to localhost, because TeamCity server does not know
that there is an HTTP proxy somewhere.
Please check that HTTP proxy preserves original Host header.
I'm trying Windows Azure now.
I have been following instruction from
https://www.windowsazure.com/en-us/develop/java/java-home/download-the-windows-azure-sdk-for-java/
I'm running on eclipse helios, but when i try to install new software and enter url repository :http://dl.windowsazure.com/eclipse
Eclipse always timeout,
message on message box like bellow :
Unable to connect to repository http://dl.windowsazure.com/eclipse/content.xml
Unable to connect to repository http://dl.windowsazure.com/eclipse/content.xml
Connection timed out: connect
How to solve this, i very need it to deploy my first app on Windows Azure platform
Help me to solve this, please
Now i try to runnning azure project on Cloud Azure, but why when i try to upload cspkg file and cscfg file, the process always timeout, whereas connection is running normally when i look on ping -t
this is message when i try upload on azure hosting service :
Uploading the selected package has failed, please verify your network connection and try again.
How to solve this issue ?
it's very strange error. >-<
I think there is some problem with your network connection as I have just tested the same download location and it does work perfectly fine as below:
As you can see below I am using http://dl.windowsazure.com/eclipse URL to download the Java specific Azure components:
After that once I select "Next", the following two components are listed to be installed in my machine:
Microsoft JDBC Drive 3.0 for SQL Server (This will work with SQL Azure)
Windows Azure Plugin for Eclipse with Java
I am sure that the problem is specific to your network connection so please have it corrected.
Yes, it's foolish of me, i forget to shutting down my proxy server on My compute.After i disable it,everything gonna be alright :D
Thanks
surely I haven't meet this situation before , but just for your additional information..
Have you follow this step on installing azure #eclipse? like .net version must be >= 3.5
here are some source link for your help http://www.windowsazure4e.org/download/
I haven’t worked with Windows Azure Java SDK. But the error message is complaining the file C:\Users\workspace\AzureFirst\emulatorTools\ResetEmulator.cmd cannot be found. It would be better if you can check whether the file exists. In addition, the call stack points out you’re using Windows Azure SDK 1.4. Please try to upgrade it to 1.6 to see whether it works fine. You can find SDK 1.6 on http://www.microsoft.com/en-us/download/details.aspx?id=28045. Please install WindowsAzureEmulator and WindowsAzureSDK. The WindowsAzureLibsForNet is not needed if you don’t want to use .NET.
Best Regards,
Ming Xu.
I'm trying to host nuget on my Amazon EC2 VPS, and I'm having issues.
I've followed the instructions here ( Hosting your own NuGet Feeds )
I've read this thread ( NuGet: remote server returned an Error(403) Forbidden ) along the same lines.
I'm not running TFS
It "could" be a proxy issue, but I'm not entirely sure how to check.
My NuGet feed is located at http://nuget.infinitas.ws. You'll notice that both http://nuget.infinitas.ws/nuget/Packages and http://nuget.infinitas.ws/Packages are throwing errors.
Any help with this will be greatly appreciated.
You are probably running the NuGet.Server in a Web Site-project. Try to run it via an ASP.NET Web Application instead (in Visual Studio you can create one via File -> New -> Project -> ASP.NET Web Application)
Have you tried the latest version (1.5)?
The release notes include some changes related to proxy authentication:
Support for Proxies that require authentication
When using NuGet behind a proxy that requires authentication, NuGet will now prompt for proxy credentials. Entering credentials allows NuGet to connect to the remote repository.
I realize I'm a little late to the party but I've just spent a frustrating couple of hours with the same problem.
I found that switching the Application Pool from "Classic" to "Integrated" fixed the problem