---
title: "Allow all traffic on a node temporarily"
description: "Open all traffic to and from a node temporarily while you sort out a conflict between the operating system firewall and the security group rules."
content_type: "how-to"
product: "security-group"
platform: "MyAccount"
url: "/myaccount/security-group/how-to/allow-all-traffic-on-a-node/"
topic: ["attach"]
relationships: {"requires":["/myaccount/security-group/how-to/attach-a-security-group-to-a-node/"]}
---

# Allow all traffic on a node temporarily

When a service on a node cannot be reached, something is blocking it: the security group rules,
or a firewall inside the node such as ufw or Windows Firewall. **Allow All Traffic** helps you
tell which. It attaches one more security group to the node, and that group
lets all traffic in and out. If the service answers with it attached, the security group rules
were the problem; if it still does not, look inside the node.

## Before you begin

- A node that is not answering on a port you expect to be open.

## Open all traffic

1. Open **Compute > Nodes**, select the node, and open its **Security Group** tab.
2. Click **Allow All Traffic**.

The group is attached straight away. It appears in the node's list with a name that starts
with **allow_all_traffic** and the region. Now test your
service again.

## Detach the allow-all group when you are done

The allow-all group stays attached until you take it off, and while it is there every port on
the node is open to the internet. As soon as the test is over:

1. On the node's **Security Group** tab, click **Detach** next to the allow-all group.
2. Click **Confirm**.

If the test showed the rules were the cause, fix them in
[Add or edit rules](/myaccount/security-group/how-to/add-or-edit-rules/). If the service still
did not answer with all traffic allowed, check the firewall inside the node and that the
service is running.

The node is back on its own rules, and you know where the traffic was being stopped. For other causes, see [Troubleshooting Security Group](/myaccount/security-group/troubleshooting/security-group/).