tencent cloud

Bastion Host

Product Introduction
Overview
Strengths
Scenarios
Differences between SaaS BH Standard Edition and Pro Edition
Purchase Guide
Billing Overview
Purchase Method
Upgrade Subscription Plan
Upgrade Bandwidth
Upgrade Extension Pack
Renewal
Payment Overdue
Refund
Getting Started
First Login of Admin
Admin Manual
First Login of Ops Engineer
Ops Engineer Manual
Operation Guide
Admin Guide
Operations Guide
Practical Tutorial
Blocking High-risk Commands
File Transfer Control
Tracing Security Incidents
Cross-VPC Asset Management
Access Bastion Host O&M Page Via Intranet Domain
Troubleshooting
Windows Resource Login Connection Timeout
Windows Resource Login Prompting Wait Active
Linux Resource Login via Mac Prompting No Matching Host Key Type Found
Windows Resource is Inaccessible for Mac Users
iTerm Client Displaying Unrecognizable Characters to Mac Users During Ops
Unable to Invoke Local XShell or SecureCRT
Ops Members Cannot Receive SMS Verification Code
Ops Members Cannot Load the Account When Logging in to Resources
Linux Resource Login Prompting Host Unreachable
Linux Resource Login Failure Prompting Password Error
FAQs
Usage
Consultation
BH Policy
Privacy Policy
Data Processing And Security Agreement
DocumentationBastion HostTroubleshootingiTerm Client Displaying Unrecognizable Characters to Mac Users During Ops

iTerm Client Displaying Unrecognizable Characters to Mac Users During Ops

PDF
Focus Mode
Font Size
Last updated: 2025-04-18 11:17:41

Phenomenon Description

When a Mac system uses the iTerm client to access a Linux server, Chinese characters appear garbled, as shown below:


Possible Causes

An issue with the SSH configuration file on the Mac system.

Solutions

Modify the ssh_config file on the Mac system.

Directions

1. Open the terminal on the Mac system and enter the command: vi /etc/ssh/ssh_config.
2. Modify the configuration at SendEnv LANG to SendEnv LANG LC_* .

3. Close the iTerm client, use the BH to access the target device again, and check whether the garbled text issue has been resolved.
Previous Topic: Windows Resource is Inaccessible for Mac UsersNext Topic: Unable to Invoke Local XShell or SecureCRT

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback