You can restart a Looker (Google Cloud core) instance.

## Required role


To get the permissions that
you need to restart a Looker (Google Cloud core) instance,

ask your administrator to grant you the
[Looker Admin](https://docs.cloud.google.com/iam/docs/roles-permissions/looker#looker.admin) (`roles/looker.admin`) IAM role on the project in which the instance was created.


For more information about granting roles, see [Manage access to projects, folders, and organizations](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access).


You might also be able to get
the required permissions through [custom
roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles) or other [predefined
roles](https://docs.cloud.google.com/iam/docs/roles-overview#predefined).

## Restart a Looker (Google Cloud core) instance

Restarting a Looker (Google Cloud core) instance stops any in-process Looker processes on the instance --- including running queries, schedules, and alerts --- and then restarts the instance. Once the restart has been completed, the instance will automatically resume its normal operations. Any queries that were running at the time of restart won't be completed unless you reinitiate them. Schedules and alerts will run on their specified cadence, but any jobs that were scheduled or that were being executed during the restart won't be completed.

If the instance is being modified, wait for it to complete its updates before you attempt a restart.

To restart a Looker (Google Cloud core) instance, select one of the following options:

### console

1. On the **Instances** page, click the name of the instance to view its configuration settings.
2. Click **RESTART** in the instance configuration page icon bar.

### gcloud

```
gcloud looker instances restart INSTANCE_NAME --region=REGION --async
```

Replace the following:

- <var translate="no">INSTANCE_NAME</var>: the [name](https://docs.cloud.google.com/looker/docs/looker-core-view-console#the_instances_page) of the Looker (Google Cloud core) instance
- <var translate="no">REGION</var>: the [region](https://docs.cloud.google.com/looker/docs/looker-core-view-console#the_instances_page) that the instance was created in

> [!NOTE]
> **Note:** If your `gcp.restrictTLSCipherSuites` organization policy constraint doesn't include any cipher suites that are in the [MODERN SSL policy profile](https://docs.cloud.google.com/load-balancing/docs/ssl-policies-concepts#defining_an_ssl_policy), Looker will return an error, and the instance restart will fail. Update the policy to resolve the error and restart the instance. See the [Restrict TLS cipher suites](https://docs.cloud.google.com/looker/docs/looker-core-tls-cipher-suites#policy_violations) documentation page for more information.

## What's next

- [Administer a Looker (Google Cloud core) instance from the Google Cloud console](https://docs.cloud.google.com/looker/docs/looker-core-admin-console)
- [Back up and restore a Looker (Google Cloud core) instance](https://docs.cloud.google.com/looker/docs/looker-core-backup-restore)
- [Looker (Google Cloud core) admin settings](https://docs.cloud.google.com/looker/docs/looker-core-admin-looker)