• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

GIT extension 2.5.2 does not save token

Duarte N

New Pleskian
Username:

TITLE

GIT extension 2.5.2 does not save token

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.60_build20240329.08 os_Windows 2012/2016/2019/2022

PROBLEM DESCRIPTION

When configuring a GIT repository with the PAT (personal access token) specified in the URL, the token is not stored in the config file (for example: D:\vhosts\domain.com\git\test.domain.com)

STEPS TO REPRODUCE

1. Open GIT extension
2. Click Add Repository from Azure Devops
3. Configure Repository URL with the token (ex: https://<TOKEN>@dev.azure.com/something-com/something/_git/somethingsomething)
4. Connection fails with following error:
Deploying files to test.domain.com
gitmng failed: Cloning into bare repository 'D:\vhosts\domain.com\git\test.domain.com'...
fatal: Verification code expired before contacting the server
bash: line 1: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://dev.azure.com/something-com/something/_git/somethingsomething': No such file or directory (Error code 128)

ACTUAL RESULT

The connection is not successfully established because it is done without the token, the repository is not created and the GIT folder configuration is deleted.

EXPECTED RESULT

Connection established, repository created, GIT folder with configuration created and maintained.

ANY ADDITIONAL INFORMATION

This anomaly does not happen with GIT extension 2.5.1

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
I apologize for the delayed response on your bug report. I tried to replicate your issue, but I ran into some questions. Can you help me clarify some steps?

  • In your 2nd step you mention "Add Repository from Azure Devops". However there is no option to specifically add a repository from Azure Devops. Can you clarify what you did here?
  • When adding an URL to a repository with a PAT in the format https://<PAT>@dev.azure.com/something-com/something/_git/somethingsomething the PAT gets striped from the URL when adding it to Plesk. Isn't that the case for you?
 
Last edited:
Back
Top