• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Forwarded to devs Cannot connect to remote Git repository using custom ssh port

David Alonso

New Pleskian
TITLE:
Cannot connect to remote Git repository using custom ssh port
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx, 17.8.11 #7, CentOS 6.9, x64
PROBLEM DESCRIPTION:
Connecting to remote Git repository which uses a custom ssh port, allways tries use the ssh default port (22).

upload_2018-7-5_16-31-44.png
STEPS TO REPRODUCE:
1. Go to a domain
2. Select Git
3. Fill git repository address in ssh format especifiying the port used by the remote git repository (not 22).
4. Click Ok.
5. After some seconds the following message apears: ssh: connect to host x port 22: Connection timed out​
ACTUAL RESULT:
Cannot use Git repository connection​
EXPECTED RESULT:
Be able to connect to remote git repository using any ssh port​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Help with sorting out
 
Have you tried to specify protocol like ssh://<remote_ip>:2221/repository.git ?
 
Back
Top