Manage cookies that are used for advertising, such as ad personalization, remarketing, and ad effectiveness analysis.
2.11.1.3. Connect via SSH
Important points:
- root-access to the hosting servers is not provided. Apps and components requiring such access cannot be installed on the hosting.
- Tunneling and proxying via SSH is not supported on the hosting.
WebSSH
Notes:
- The web client works directly in the browser. You do not need to enter a password or run any additional software to use it.
- When connecting via "SSH access" you will get to the hosting account root directory, when connecting via "My sites" — directly to the root directory of the corresponding site.
Open the "SSH access" section and in the "WebSSH" row, click "Connect":
Or open the "My sites" section and in the site menu, click "SSH":
Console
- Execute the standard connect command (Instead of
exampleandexample.ftp.tools, use your SSH login and host):ssh example@example.ftp.tools - When the connection is established, enter the SSH password. ⚠️ For security reasons on Linux systems, characters are not displayed on the screen when you enter a password or paste it from the clipboard.
PuTTY
PuTTY — free client for SSH, telnet and other protocols.
- Download and run PuTTY.
- Specify the connection settings and click "Open":

- "Host Name (or IP address)" — SSH host.
- "Port" —
22. - "Connection type" — "SSH".
- If the warning is displayed, it means that the server key is not in the PuTTY cache (this is normal for the first connection) or has changed. To connect, click "Accept" or "Connect Once":

- "Accept" — connect and store the current server key in the PuTTY cache (future connections will not display the warning until the PuTTY cache is cleared or the server key is changed).
- "Connect Once" — connect without storing the key in the PuTTY cache (the warning will be displayed again on future connection).
- "Cancel" — do not connect and do not store the key in the cache.
- Once connected, enter SSH login and password. You can either enter the password manually or copy and paste it with the right mouse button. ⚠️ For security reasons on Linux systems, characters are not displayed on the screen when you enter a password or paste it from the clipboard.
(11)
Comments
[16:17:37.750] Failed to set up socket for dynamic port forward to remote port 14821: Socket closed. TCP port forwarding may be disabled, or the remote server may have crashed. See the VS Code Server log above for details.
[16:17:37.799] > channel 3: open failed: administratively prohibited: open failed
> channel 4: open failed: administratively prohibited: open failed
>
[16:17:37.801] ERROR: TCP port forwarding appears to be disabled on the remote host. Ensure that the sshd_config has `AllowTcpForwarding yes`. Contact your system administrator if needed.
Однак для синхронізації файлів ви можете скористатися FTP або SFTP плагінами, наприклад за інструкцією https://www.ukraine.com.ua/wiki/hosting/files/ftp/ide/vscode/ , або функціоналом GitHub Actions, що більш детально описано в інструкції https://www.ukraine.com.ua/wiki/hosting/other/github-actions/ .
У випадку виникнення додаткових запитань, зверніться до технічної підтримки, що можна зробити натиснувши на кнопку повідомлення у правому нижньому куті сторінки.
[10:43:44.164] stderr> channel 4: open failed: administratively prohibited: open failed
[10:43:44.165] Failed to set up socket for dynamic port forward to remote port 14385: Socket closed. TCP port forwarding may be disabled, or the remote server may have crashed. See the VS Code Server log above for details.
[10:43:44.165] Failed to set up socket for dynamic port forward to remote port 14385: Socket closed. TCP port forwarding may be disabled, or the remote server may have crashed. See the VS Code Server log above for details.