I’m probably being dense, but how do you switch to https?
I will do some more digging but, as a workaround, how about using another git client (like gitkraken) to connect to gitlab.pavlovia.org? Or VS Code’s built-in git client? I think they support oauth2 authorisation which is what psychopy is doing (successfully) with the updated server
If you go to your repo you can clone your repo using http (see screenshot). You can also change the remote if you already have a git repo pulled.
BTW - joining the crowd, this issue is currently breaking experimental automation.
Hi there,
I don’t know the answer yet to the change in SSH but Gitlab provides the links to show you how to clone a repository using HTTPS instead of SSH on the top-right of each project page:
I just tried this for a repo that I own and clone/push/pull worked perfectly fine using HTTPS.
For repositories you haven’t yet cloned simply use the HTTPS url when you perform clone.
For repositories you previously cloned you’ll need to open the (hidden) file .git/config within the project and replace-all [email protected]: with https://gitlab.pavlovia.org/ (or fetch the url from the gitlab site and do it one-by-one).
hope that helps but I’ll also post here if I find out why SSH authentication has changed
best wishes
Jon
Thanks Jon, confirming that this works for me (as mentioned above). Thanks for the .git/config tip, too, that is very helpful!!
Thanks Jon - this works! What a relief! Much appreciated 
Thanks Jon, changing from ssh to https in the config file finally solved this issue for me.
A shame that ssh doesn’t work any more, but https seems like a good solution for now.
This is a little while ago but I am getting this problem again today. I’ve tinkered with making things in the Builder and pushing/pulling to Pavlovia but I’m now trying to clone an experiment I’ve forked from someone else and I’m getting this error.
I can’t seem to find the instructions for cloning using html but I’m still looking…
This message is just to report to the developing team that this is still an issue, even though it has been marked as solved.
When pushing local changes to an existing gitlab.pavlovia remote repo using ssh, I am asked the password for my account. Permission is denied even if the password is correct (signing in on the website works fine with the same password). A collaborator also tried cloning the same repo via ssh and got the same problem.
As suggested in the solution, using https instead of ssh is an effective workaround. I am still reporting this as a feedback to the developers, in case they wanted to restore the ssh connection.
This continues to be an issue. I’ve lost hundreds of dollars of data because of these issues – I am running a longitudinal study and this error unfortunately cropped up midway through data collection. The https route is ALSO not a viable workaround for me – I am STILL being asked for a password. The issue is specific to GitLab.Pavlovia (not GitLab). Please help, I feel incredibly exasperated!
This thread is about jsPsych, not PsychoPy. Which are you using?
PsychoPy, but the issue seems to be similar? That is, a Pavlovia server-side issue (making the use of jsPsych vs. PsychoPy irrelevant?). But I could be fundamentally misunderstanding the problem – apologies for the confusion if so!
Just bumping this thread… ssh authentication from terminal still seems broken. HTTPS is fine, but I would not call this “solved” while the standard secure ssh method does not work. Since I use ssh access with most other services (it tends to be recommended as the most secure option, and it is the first of the two options in the GitLab drop down), I wasted hours trying to get this to work. It would have saved me a lot of effort if it had been made clear in the documentation that only HTTPS works, especially if there is no plan to fix ssh authentication.