[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-25。"],[],[],null,["# Admin settings - Connections\n\nTo access the **Connections** page, open the **Admin** menu and, under **Database** , choose **Connections**.\n| **Note:** If you have a permission that provides access to only select pages in the Admin panel, such as [`manage_schedules`](/looker/docs/admin-panel-users-roles#manage_schedules), [`manage_themes`](/looker/docs/admin-panel-users-roles#manage_themes), or [`see_admin`](/looker/docs/admin-panel-users-roles#see_admin), but you don't have the [Admin role](/looker/docs/admin-panel-users-roles#default_roles), the page or pages that are described here may not be visible to you in the Admin panel.\n\nViewing connections\n-------------------\n\nOn the **Connections** page, you can view your database connections and the IP addresses that are needed to allow network traffic. If the ability to create a new database has been enabled for your instance, you can also add a new connection.\n\n\n### Databases tab\n\nThe **Databases** tab shows basic information about the database connections that you've defined. It also shows any Looker-managed connections that you've created, if the ability to create a new database has been enabled for your instance. You can also test the status of and edit the configuration of those connections from the **Databases** tab.\n\nYou can click **Public IP Addresses** to view the list of IP addresses that are needed to allow network traffic from your Looker instance. All network traffic from Looker will come from one of the listed IP addresses, based on the region where your Looker instance is hosted. Prohibiting traffic to your database, except from these and other trusted IP addresses, is a way to limit data access.\n| **Note:** The **Public IP Addresses** button is not available for [Looker (Google Cloud core)](/looker/docs/looker-core-overview) instances. If you are using a Looker (Google Cloud core) instance that is set up for public IP or for both public IP and private IP, use the IP address listed in the **Egress Public IP** field on the [**Details** tab](/looker/docs/looker-core-view-console#details_tab) of the **Instances** page in the Google Cloud console.\n\nThe following table describes the elements on the **Databases** tab:\n\n### SSH Servers tab\n\n\u003e The **SSH Servers** tab isn't available for [Looker (Google Cloud core)](/looker/docs/looker-core-overview) instances.\n\u003e\n\u003e The **SSH Server** option is available if a Looker (original) instance is deployed on Kubernetes infrastructure, and only if the ability to add SSH server configuration information to your Looker instance has been enabled. If this option is not enabled on your Looker instance and you would like to enable it, [contact a Google Cloud sales specialist](https://cloud.google.com/contact) or [open a support request](http://console.cloud.google.com/support/cases).\n\u003e\n\u003e Looker automatically chooses the localhost port for you when creating SSH tunnels; you cannot specify the localhost port.\n\u003e\n\u003e SSH connections to PrestoDB or Trino databases may require additional database configuration. When SSL is enabled, the PrestoDB or Trino database defaults to listening on port 443. To establish the SSH tunnel, Looker must set the localhost port to 443, which is already in use by Looker. This will cause the SSH tunnel setup to fail. To correct the issue, configure your PrestoDB or Trino database to listen on a port other than port 443 when SSL is enabled.\n\nThe **SSH Servers** tab lists the SSH server configurations that you have added, indicates the status of connections to the SSH servers, and lists the [database connections](/looker/docs/connecting-to-your-db#adding-connections) using each SSH server. From the **SSH Servers** tab, you can also [test a connection to an SSH server](#testing_the_connections_to_an_ssh_server), and [add or edit SSH server configurations](#adding_or_editing_an_ssh_server_configuration).\n\nThe following table describes the elements on the **SSH Servers** tab:\n\n#### Adding or editing an SSH server configuration\n\nTo add a new SSH server configuration:\n\n1. In the **SSH Server** tab, click **Add Server**\n2. In the **Unnamed Server** field in the top right corner, enter a name for the SSH server configuration.\n3. Click **Download Key** to download the public key to a text file. Be sure to save this file for later use.\n4. In the **Server Username** field, enter the username that Looker will use to connect to the SSH server.\n5. In the **Server IP Address or Hostname** field, enter the SSH server IP address or hostname.\n6. In the **Server Port** field, enter the port number used to connect to the SSH server.\n7. Add the downloaded public key to the authorized key file on your SSH server. See the [Using an SSH server](/looker/docs/using-an-ssh-tunnel#step_4:_prepare_the_tunnel_host) documentation page for more information and an example.\n8. Ensure that the appropriate [Looker IP addresses are added to the allowlist](/looker/docs/using-an-ssh-tunnel#step_2:_create_ip_allowlist) on your SSH server so that Looker can connect to the SSH server.\n9. Click **Test \\& Request Fingerprint** to verify your connection to the SSH server.\n10. View the new SSH configuration. On this screen, you can also download or view the public key and view the unique fingerprint of the SSH server configuration.\n\nTo edit an existing SSH server configuration, click the three-dot **Options** menu in the row of the selected SSH server, and choose **Server Details**.\n\n#### Testing the connections to an SSH server\n\nTo test all database connections to an SSH server:\n\n1. Click the three-dot **Options** menu in the row of the chosen SSH server.\n2. Choose **Test Connections**.\n\nLooker will test all database connections using that SSH server and display a green checkmark next to the server name and all connections where the connection test passes. A red exclamation point icon indicates that the connection failed the test.\n| **Note:** If you make changes to your SSH server's `sshd_config` file, before testing the connection you'll need to restart the sshd daemon on your SSH server for the changes to take effect.\n\n#### Adding a database connection to an SSH server\n\nTo add a new database connection using an SSH server:\n\n1. Click the three-dot **Options** menu in the row of the chosen SSH server.\n2. Choose **Add Connection**.\n\nLooker displays the [**Connection Settings**](/looker/docs/connecting-to-your-db) page, with the SSH server listed in the **SSH Server** field.\n\n#### Deleting an SSH server configuration\n\nTo delete an SSH server configuration:\n\n1. Click the three-dot **Options** menu in the row of the SSH server to delete.\n2. Choose **Delete Server**.\n\nTesting connections\n-------------------\n\nLooker lets you test your existing connections to make sure they are functioning properly. You can also test connections as you add them, as described on the [Connecting Looker to your database](/looker/docs/connecting-to-your-db) documentation page.\n\nEach connection test includes a list of status checks to tell you whether Looker can successfully use the database connection.\n\nPotential issues are shown in yellow; errors are shown in red. If a connection \"passes\", it appears in green.\n\u003e Database connections that use OAuth, such as [Snowflake](/looker/docs/db-config-snowflake#oauth) and [Google BigQuery](/looker/docs/db-config-google-bigquery#oauth_for_bigquery_connections), require a user login. If you are not logged in to your OAuth user account when you test one of these connections, Looker will show a warning with a **Log In** link. Click the link to enter your OAuth credentials or to allow Looker access to your OAuth account information.\n\nYou can check the status of:\n\n- A single connection by clicking **Test** to the far right of that connection\n- All connections by clicking the **Test All Connections** button at the top of the page\n\nTwo checks are common cause for confusion:\n\n- Can find temp schema\n- Can use persistent derived tables\n\nThese checks don't need to pass for Looker to function. However, you do need them to pass to use [persistent derived tables](/looker/docs/derived-tables#persistent-derived-tables), which are a very valuable modeling feature.\n\nAdding connections\n------------------\n\nTo add a new database connection, follow the steps described on the [Connecting Looker to your database](/looker/docs/connecting-to-your-db) documentation page.\n\nEditing connections\n-------------------\n\nTo edit an existing connection, open the **Connections** page by selecting the **Admin** menu, and then, under **Database** , choose **Connections** . Click the **Edit** button for the connection. The same page that you use to create a connection will appear (described on the [Connecting Looker to your database](/looker/docs/connecting-to-your-db#adding-connections) documentation page), but with the relevant information already filled out. Make any needed changes, and then click **Update Connection**.\n\n\nActions available for all connections\n-------------------------------------\n\nAll connections offer these options from the gear drop-down menu to the far right of each connection:\n\n\nActions available for some connections\n--------------------------------------\n\nDepending on the connection dialect, the gear drop-down menu to the right of the connection may offer the following additional options:"]]