> For the complete documentation index, see [llms.txt](https://docs.acecloud.ai/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecloud.ai/knowledge-base/network/troubleshoot-connecting-to-your-ace-compute-instance.md).
# Troubleshoot Connecting to your Ace Compute Instance
Learn about troubleshooting options for the AceCloud instance.
**a. Verify that your instance's security group allows access to port 22 (Linux) or port 3389 (Windows).**
**Step 1:** [Login](https://customer.acecloudhosting.com/index.php?m=ace_product_register_addon\&action=login) to your AceCloud Portal.\
\
**Step 2:** Navigate to **Networks** and then **Security Groups** from the left panel.
**Step 3:** Click on the security group to view its port settings.
**Step 4:** Click on **Inbound Rules.**
**Step 5:** Verify that the port range is set to 22 for Linux instances or 3389 for Windows instances. If not, proceed to Step 6 to modify the settings.
**Step 6:** Click on the **Ellipsis menu** and choose **Edit Rule.**
***Note:** Alternatively, you can create a new security group rule that includes the necessary port configuration.*
**Step 7:** Update the port number as needed, scroll down, and click **Update** to save the changes.
*Note: Opening port **22 (for Linux)** or **3389 (for Windows)** to the public internet can expose your instance to potential unauthorized access or brute-force attacks.*\
*It is strongly recommended to restrict access using security group rules (e.g., limit to specific IP addresses).*
**b. Verify that the rule direction is correctly set to Inbound or Outbound, depending on the intended traffic flow.**
**c. Verify the network address configured for each subnet within your networks**.
Check whether the network address is correctly configured. If it is incorrect, you can update the network address or modify the associated subnet as needed.
