Run SSH terminal
Use an SSH terminal to run commands on a remote computer from GoLand. For example, you can build or test a Go application using the Go installation on that computer. To transfer project files, configure a deployment server.
Set up the SSH terminal
Make sure the remote computer has an SSH server and that you have an account with access to it.
Create an SSH configuration with the host, port, username, and authentication method required by the server. Test the connection.
Select the remote environment and configure the SSH terminal:
In the Settings dialog (Ctrl+Alt+S) , go to .
In the Connection settings area, select the remote environment:
Current Vagrant: select this option to have the commands in the SSH Terminal executed on the currently running Vagrant virtual machine.
SSH configuration: select this option to have the commands in the SSH Terminal executed on the local or remote Web server accessible through one of the SSH configurations.
Select SSH configuration on every run: if this option is selected, you will have to choose the desired configuration from the popup, every time you choose from the main menu.
If the desired SSH configuration does not appear in the list, click the Set up configurations link, and define one in the SSH Configurations page.
To use the same SSH connection each time, select an SSH configuration. To choose a connection whenever you start a session, select Select SSH configuration on every run.
From the Default encoding list, select the encoding to use in the SSH terminal.
Launch the SSH terminal
Go to . If prompted, select the SSH configuration for the remote computer.
Run commands in the terminal tab that opens. To end the session, enter
exit.
View SSH logs
To troubleshoot an SSH connection, check the IDE logs. For authentication errors, also check the SSH server logs or ask the server administrator. Their location depends on the server operating system and configuration.
For example, on a Fedora server, run sudo journalctl -u sshd.service to view the SSH server logs. These logs can help identify authentication failures and rejected connections.