| 1 | # Install Netdata on GCP |
| 2 | |
| 3 | Netdata is fully compatible with the Google Cloud Platform (GCP). |
| 4 | You can install Netdata on cloud instances to monitor the apps/services running there, or use |
| 5 | multiple instances in a [parent-child streaming](/src/streaming/README.md) configuration. |
| 6 | |
| 7 | ## Recommended installation method |
| 8 | |
| 9 | The best installation method depends on the instance's operating system, distribution, and version. For Linux instances, |
| 10 | we recommend the [`kickstart.sh` automatic installation script](/packaging/installer/methods/kickstart.md). |
| 11 | |
| 12 | If you have issues with Netdata after installation, look to the sections below to find the issue you're experiencing, |
| 13 | followed by the solution for your provider. |
| 14 | |
| 15 | ## Post-installation configuration |
| 16 | |
| 17 | ### Add a firewall rule to access Netdata's dashboard |
| 18 | |
| 19 | If you cannot access Netdata's dashboard on your cloud instance via `http://HOST:19999`, and instead get an error page |
| 20 | from your browser that says, "This site can't be reached" (Chrome) or "Unable to connect" (Firefox), you may need to |
| 21 | configure your cloud provider's firewall. |
| 22 | |
| 23 | Cloud providers often create network-level firewalls that run separately from the instance itself. Both AWS and Google |
| 24 | Cloud Platform calls them Virtual Private Cloud (VPC) networks. These firewalls can apply even if you've disabled |
| 25 | firewalls on the instance itself. Because you can modify these firewalls only via the cloud provider's web interface, |
| 26 | it's easy to overlook them when trying to configure and access Netdata's dashboard. |
| 27 | |
| 28 | You can often confirm a firewall issue by querying the dashboard while connected to the instance via SSH: `curl |
| 29 | http://localhost:19999/api/v1/info`. If you see JSON output, Netdata is running properly. If you try the same `curl` |
| 30 | command from a remote system, and it fails, it's likely that a firewall is blocking your requests. |
| 31 | |
| 32 | Another option is to put Netdata behind web server, which will proxy requests through standard HTTP/HTTPS ports |
| 33 | (80/443), which are likely already open on your instance. We have a number of guides available: |
| 34 | |
| 35 | - [Apache](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md) |
| 36 | - [Nginx](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md) |
| 37 | - [Caddy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md) |
| 38 | - [HAProxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md) |
| 39 | - [lighttpd](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md) |
| 40 | |
| 41 | To add a firewall rule, go to the [Firewall rules page](https://console.cloud.google.com/networking/firewalls/list) and |
| 42 | click **Create firewall rule**. |
| 43 | |
| 44 | The following configuration has previously worked for Netdata running on GCP instances |
| 45 | ([see #7786](https://github.com/netdata/netdata/issues/7786)): |
| 46 | |
| 47 | ```text |
| 48 | Name: <name> |
| 49 | Type: Ingress |
| 50 | Targets: <name-tag> |
| 51 | Filters: 0.0.0.0/0 |
| 52 | Protocols/ports: 19999 |
| 53 | Action: allow |
| 54 | Priority: 1000 |
| 55 | ``` |
| 56 | |
| 57 | Read GCP's [firewall documentation](https://cloud.google.com/vpc/docs/using-firewalls) for specific instructions on how |
| 58 | to create a new firewall rule. |