I installed GitStack server on my Windows server 2008 machine, created a repository, created a user, and I can browse to the repository from my local machine.
The problem is that when I go to my Mac, I can browse through the web fine, but when I open the XCode and try to connect to the repository, it prompts me for the name and password and just keeps prompting, but cannot log me in. Is this GitStack related, or something with my XCode? I use XCode 4.6.2.
I used this:
https://testname#192.168.1.10/reponame
https://testname#192.168.1.10/reponame
https://testname:testpassword#192.168.1.10/reponame
Nothing works, it always prompts me for the name and password and cannot log in. This user is created as local user in GitStack, and had been given the access to the repository.
Thank you.
Try to initialize the git repository through Terminal.
It must be something about security and in Terminal you'll have a prompt.
Related
How do I install jenkins on Windows 10 Home?
I am going through this link to install jenkins on local system.
https://www.jenkins.io/doc/book/installing/windows/
anytime I try to login after installation, I get following error:
From the Jenkins website I get following solution:
Logon to the computer with administrative privileges.
Open the Administrative Tools and open the Local Security Policy
Expand Local Policy and click on User Rights Assignment
In the right pane, right-click Log on as a service and select properties.
Click on the Add User or Group… button to add the new user.
In the Select Users or Groups dialogue, find the user you wish to enter and click OK
Click OK in the Log on as a service Properties to save changes.
But this is not helpful as I am trying to do this on Win 10 Home hence local security policy is not available.
I tried to check system requirements also from https://www.jenkins.io/doc/administration/requirements/windows/ but could not get definitive answer.
Are there any workarounds or solution for this?
I ran into the same problem and could not find a solution. I ended up installing docker desktop on my Win10 Home and now run the precompiled image. Works perfectly.
I've been making some changes to my MVC project which earlier today was running fine. However, I installed some new software including PostGreSql and npgsql for Visual Studio and now when I run my project it seems IIS can no longer find localhost. The actual message is 'Cannot reach this page. Make sure the web address http://localhost:4068 is correct'.
I've checked that my IIS is running and I've tried deleting my IISExpress folder, deleting the config file in .vs/config but so far nothing seems to work and I don't even know what it was that caused it. If anyone has had this issue, please let me know how you resolved it.
The most likely scenario is that your project's properties have changed.
Have you checked the web settings? (right click on project -> properties)
You need to put an entry in your c:\Windows\System32\Drivers\etc\hosts File like
127.0.0.1 localhost
Or simply try http://127.0.0.1:4068 as url
Editing the file needs administrative rights so you might run your editor as administrator.
My question is - to copy files to remote machines from the Drop folder, do I need that remote machine registered as an agent?
My remote machine is in the same network but still, I'm getting an ERROR to copy files.
No, it is not required to have a TFS Agent on the target server in order to copy files over to it, but you do need to have permission to write to it. See the screenshot of what I did. Notice that I am storing the credentials as variables in the build definition. The password is "locked" so no one can see the clear text password. I have the Build Agent running under the same service account that has Admin privileges on the target server, but leaving them off did not help. To test this out, try to log into the build server via RDP and then try to open file explorer and connect to the Target Server using the network path (\SomeServer\C$\SomePath\dir) and using the credentails (domain\login or just login) and see if it works, along with the password.
GitKraken has successfully cloned a repository hosted on Team Foundation Server, but on subsequent fetch and push it asks for login information. Even when provided it will ask again, offering no error or explanation. "Remember me" is checked.
Everything works perfectly fine using the cmd.
Note that the issue occurs on a virtual machine. I have tested interacting with the repository on my physical machine using GitKraken - no problem there. However, I have previously experienced the same type of problem with other projects on my physical machine. Seems GitKraken sometimes has problems with TFS, but not sure.
I have tried reinstalling GitKraken, but it didn't resolve the issue. Any ideas on how to fix this?
Edit 2018-01-24 as per #Cece Dongs comment
I am using GitKraken 3.3.3 - recently upgraded, but issue still occurs.
TFS is version 15.117.26714.0 and using the web portal does not give me problems. I login once like normally.
When cloning a GitHub repo everything is working properly. However, when attempting to clone a TFS repo from Visual Studio I get an unauthorized error. (TF30063). I assume it could be related to the Active Directory settings not set up properly because of the Hyper-V setup I am using. Will investigate further and provide more details here.
After using \domain\username instead of just username as login credentials to TFS everything is working.
Using only the username will work on my physical machine as that machine is recognized on the domain, but as the virtual machine is not, the domain is required.
I am trying to get some automatic deployments up and running using TFS 15 (on-premise). I have a powershell script on the deployment target to call.
The deployments starts fine by downloading the artifact. But when the agent runs the script it wants to create a folder C:\Windows\DtlDownloads (thats not part of my script but part of preparing things for TFS I guess). That fails:
##[debug]System.AggregateException: Failed to install 'VisualStudioRemoteDeployer20597940-38b2-4ba8-9a4d-fcc894308730' from service executable path VisualStudioRemoteDeployer.exe . Consult the logs below:
Access to the path 'DtlDownloads' is denied.
CategoryInfo :PermissionDenied: (C:\Windows\DtlDownloads:String) [New-Item], UnauthorizedAccessException
FullyQualifiedErrorId :CreateDirectoryUnauthorizedAccessError,Microsoft.PowerShell.Commands.NewItemCommand
The user used to logon is a server-local user named deploy who is also a local administrator on that machine. I also checked the effective access for that user on the windows folder and it should be able to create directories.
Something similar happens with the copy step. Robocopy signals two errors:
2017/03/16 08:57:21 ERROR 5 (0x00000005) Getting File System Type of Destination \\server.domain.com\c$\abc\def\
Access is denied.
and
2017/03/16 08:57:21 ERROR 5 (0x00000005) Creating Destination Directory \\server.domain.com\c$\abc\def\
Access is denied.
The second is a bit unexpected as the folder def already exists but I guess it is a follow up because getting the type failed beforehand.
The user itself must have been recognized because I get different errors when using invalid credentials. I have enabled WinRM using Enable-PSRemoting and ConfigureWinRM.ps1 from WinRM-Http-Https-Without-Makecert.
What could still restrict the permissions?
Update: Using a domain user instead of a local one of that server solves the issue. But I do not understand why. Can someone explain or even provide information how to make it work with a local user?
The username of either a domain or a local administrative account on
the target host(s).
Formats such as username, domain\username, machine-name\username, and .\username are supported.
UPN formats such as username#domain.com and built-in system accounts such as NT Authority\System are not supported.
Source Link
Both the domain account and local admin should be work. Please double check your format and give a try with another format.
One problem could be if that you have the agent as a service, that service has not the proper privileges, like being on Network Account. Try to change that to the user account which has administrative privileges.
Running "winrm quickconfig" fixed this problem for me
winrm quickconfig
https://learn.microsoft.com/en-us/windows/win32/winrm/installation-and-configuration-for-windows-remote-management