I'm setting NuGet for deploy my projects in Nexus, when I execute the command 'nuget install ' i got this message:
Name User:INFO: An error occurred while loading packages from 'MyRepository' Could Not Ask for an entry in Interactive Mode NO. Provide the credentials for 'MyRepository'
How should I configure proxy, userLogin and password network, to make it work?
Related
I trying to make SVN work on a Windows 2016 Server. I am using SVN over commandline. SVN is always using the user which is logged in. Let's say the logged in user is USER. The user needed for SVN is called SVNUSER. We are using a VisualSVN Server. Both Servers are inside a company network and they use the same AD for authentication.
I tried following stuff:
svn checkout --username SVNUSER http://svn01.de/svn/Application/trunk/FSW
or
svn checkout --username e102365 --password pass http://svn01.w3.de/svn/Application/trunk/FSW
didn't work. I get following error:
svn: E175013: Unable to connect to a repository at URL 'http://svn01.de/svn/Application/trunk/FSW'
svn: E175013: Access to '/svn/Application/trunk/FSW' forbidden
The serverlog says i tried to connect with USER.
The only way I was able to make the checkout work is using run as with the SVNUSER but I need it for automation and run as is interactive so it does not help.
The folder C:\Users\USER\AppData\Roaming\Subversion\auth is empty. When using tortoise SVN it says there is no saved authentication.
I assume that your VisualSVN Server installation is configured for Integrated Windows Authentication (Active Directory Single Sign-On) (see KB182 for details).
Since it's Single Sign-On, you have to run your scripts as the user account that has permissions to access the repository. Specifying credentials in the command-line won't work - it will always authenticate as the user account who started the svn.exe client. You can try running your script from Windows Task Scheduler, custom Windows Service, etc.
Or you can enable Basic Windows authentication on the server in addition to Integrated Windows Authentication. And force your svn client to always prefer Basic auth (i.e., disable Integrated Windows Authentication on the client side). You can append the following option to your svn.exe commands:
--config-option servers:global:http-auth-types=basic
Or modify the %APPDATA%\Subversion\servers file. Add the http-auth-types=basic string under [Global].
I'm using Windows 10 behind a corporate proxy and az --version outputs the following:
azure-cli 2.5.1
command-modules-nspkg 2.0.3
core 2.5.1
nspkg 3.0.4
telemetry 1.0.4
...
Unable to check if your CLI is up-to-date. Check your internet connection.
Furthermore, az extension list-available throws:
Unable to get extension index.
Please ensure you have network connection. Error detail: HTTPSConnectionPool(host='aka.ms', port=443): Max retries exceeded with url: /azure-cli-extension-index-v1 (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden',)))
How to configure azure-cli for the corporate proxy?
Download local proxy configuration from http://wpad/wpad.dat
At the beginning of the wpad.dat file there is a line similar to CWSProxy="PROXY proxy.corporation.com:8082";
Enter the proxy server to environment variable HTTPS_PROXY, e.g. in bash: export HTTPS_PROXY="proxy.corporation.com:8082"
Now az extension list-available connects. However, for some reason, az --version is still giving Unable to check if your CLI is up-to-date. Check your internet connection. You can now anyway install extensions such as az extension add --name azure-devops.
From https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?view=azure-cli-latest&tabs=azure-cli#proxy-blocks-connection
For Windows 10, you could check the proxy settings in the Settings > Network & Internet > Proxy pane. Contact your system administrator for the required settings, or for situations where your machine may be configuration-managed or require advanced setup.
I am automating a build process. The process requires deployment of application to a server, after deployment a few scripts have to be executed to share and provide permissions on the server. The scripts run when I login via domain user through powershell.I am using Jenkins for the CI/CD process. I want to include my domain credentials to run the scripts on the server. I have also used the active directory plugin, and can login with my domain credentials but still I am not able to establish a remote connection with the server.
My script is
Enter-PSSession -ComputerName ATKT-WS-20
Invoke-Expression -Command .\FolderSharingScript.ps1
Enter-PSSession : Connecting to remote server ATKT-WS-20 failed with the following error message : WinRM cannot
process the request. The following error with errorcode 0x8009030e occurred while using Kerberos authentication: A
specified logon session does not exist. It may already have been terminated.
Possible causes are:
-The user name or password specified are invalid.
-Kerberos is used when no authentication method and no user name are specified.
-Kerberos accepts domain user names, but not local user names.
-The Service Principal Name (SPN) for the remote computer name and port does not exist.
-The client and remote computers are in different domains and there is no trust between the two domains.
After checking for the above issues, try the following:
-Check the Event Viewer for events related to authentication.
-Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or
use HTTPS transport.
Note that computers in the TrustedHosts list might not be authenticated.<
I have also added the machine name in the trustedhosts. How can I include the domain credential in Jenkins jobs?
The solution turned out to be not to use PowerShell's remoting at all, but instead rely on the remoting built into Jenkins:
Connect the remote machine as a Jenkins agent to the Jenkins server, running the agent executable as the desired domain user.
On the Jenkins server, ensure that your job is configured to run on the remote machine, using a label expression.
Assuming the PowerShell plugin is installed, you can then send PowerShell code as-is to the remote machine - no need for PowerShell sessions, credentials, ...
I have two windows machines, one running Nexus OSS 3 and the other running ProGet.
Now I would like to create a nuget proxy repository in Nexus that points to one of the feeds/repositories I have in ProGet. I have followed this guide: nuget proxy repository where I basically copied the nuget.org-proxy proxy configuration that comes by default when you install Nexus OSS 3.
But I keep getting this error from command line
GET http://mynexus:8082/repository/tools-proxy/Packages(Id='x',Version='1.1.1')
GET http://mynexus:8082/repository/tools-proxy/Packages(Id='x',Version='1.1.1.0')
System.InvalidOperationException: Unable to find version '1.1.1' of package 'x'.
at NuGet.PackageHelper.ResolvePackage(IPackageRepository repository, String packageId, SemanticVersion version)
And the Nexus web log:
2016-05-25 20:13:28,252+0200 INFO [qtp1305498137-264] admin org.sonatype.nexus.rapture.internal.security.SessionServlet - Deleting session for user: admin
2016-05-25 20:13:32,971+0200 ERROR [qtp1305498137-282] *UNKNOWN org.sonatype.nexus.extdirect.internal.ExtDirectServlet - Failed to invoke action method: coreui_Repository.coreui_Repository_readStatus, java-method: org.sonatype.nexus.coreui.RepositoryComponent.readStatus
org.apache.shiro.authz.UnauthenticatedException: The current Subject is not authenticated. Access denied.
at org.apache.shiro.authz.aop.AuthenticatedAnnotationHandler.assertAuthorized(AuthenticatedAnnotationHandler.java:53) [na:na]
at org.a
When I run nuget install on a package X specifying the proxy repository URL as source:
nuget install x -Version 1.1.1 -Source http://mynexus:8082/repository/tools-proxy -Pre -NoCache -Verbosity detailed
That package indeed exists in the original ProGet feed and if I specify the direct/non-proxy feed instead the install works fine:
nuget install x -Version 1.1.1 -Source http://myproget:8181/repository/tools -Pre -NoCache -Verbosity detailed
GET http://myproget:8181/nuget/Tools/Packages(Id='x',Version='1.1.1')
GET http://myproget:8181/nuget/Tools/package/x/1.1.1
Installing 'x 1.1.1'.
Successfully installed 'x 1.1.1'.
I have tried with nuget version 2.8 and 3.4.
My ProGet server is configured with Built-In authentication:
Anonymous have download access:
Why do I get this access error when Anonymous have download access on my ProGet server?
I have now built up a gitlab server on my Ubuntu computer as your installation guide on www.gitlab.org official website tells.
Then I signed in the gitlab server homepage through IE browser in the client computer.
Subsequently I modified the "My Profile" and uploaded my SSH public key.
Logged out and reboot server, then login again.
Create my first git project : gitlab_testing.git
At that time when I did 'git clone' to download the gitlab_testing.git repository from server, or when I push the first commit upon to server, it always showed the below error message, please kindly see the below snapshots :
As mentioned here:
"Name or service not known" is a socket-level error which usually points to either an invalid IP address/DNS hostname, or an unregistered port name.
Check if this is a proxy issue (as in this question).
Either you need to configure a proxy, or make sure that you don't use a proxy when accessing a local gitlab server (using the no_proxy environment variable)