---
title: "Change the Device Connectivity Port from TCP 995"
slug: "how-to-8"
updated: 2026-09-08T11:17:14Z
published: 2026-09-08T11:17:14Z
canonical: "kb.ctera.com/how-to-8"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.ctera.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Change the Device Connectivity Port from TCP 995

By default, a CTERA Edge Filer and CTERA Drive Share/Protect (Agent) establish a connection and perform cloud backup and synchronization with CTERA Portal over port TCP 995. These devices can be configured to connect to the CTERA Portal over a different port by changing this default port in the portal configuration.

## Step-by-step guide

**To change the default port used by devices to connect to the portal:**

1. Access the DNS Manager and for the portal server click **Forward Lookup Zones**.
2. Open the domain for the DNS Suffix of the portal, and create a new subdomain under it with the name of the team portal you want to join the edge filer to.
3. Right-click on the subdomain and select Other **New Records…**.
4. Select **Service Location (SRV)** from the resource record type list, and click **Create Record**.
5. Enter the following details:  

**Service** –  _ctera  

**Protocol** – _tcp  

**Priority** – 10  

**Weight** – 5  

**Port Number** – The port number you want to use instead of 995.
6. Click **OK**.
7. Using SSH, log in as root to a portal application server.
8. Run the following commands:

```
firewall-cmd --add-port=<newPort>/tcp --permanent
firewall-cmd --reload
```

where newPort is the TCP port to use for connectivity.
9. Optionally verify that the new port is open on the server by running the following command `firewall-cmd --list-ports` to display the list of ports including the new port.
10. Repeat steps 7 to 9 for every portal application server in the cluster.
11. Access the telnet interface by entering `#telnet 0`
12. At the telnet prompt, input the login command Login <portal-name> admin <globaladminname><br>
Where portal-name is the portal name, such as myportal and GlobalAdminName is the global administrator username.</globaladminname></portal-name>
13. At the prompt, enter the password for the global administrator.
14. Run the following commands:

```
set-list /settings/portSettings/ newPort
set /settings/defaultPort newPort
```

**Note**

If you change the port to TCP 443 for secure access over HTTPS, you must also change the administration portal’s HTTPS access port so that both HTTPS and CTTP traffic do not go over the same port.
15. Run `portal-manage.sh restart` on each server.

**To change the administration portal HTTPS access port when the device connectivity port is set to 443:**

1. In the global administration view, select **Settings > Control Panel** in the navigation pane.
2. Select **Global Settings**.  

The **Global Settings** page is displayed.
3. In the **Administration Console** area, specify the new HTTPS port number in the **HTTPS Port** field.  

Use a port in the range 1024 to 65535.
4. Click **Save**.
5. Restart all the portal servers, by running `portal-manage.sh restart` on each server.  

Restart the servers in the following order:
  - Main database server.
  - Replication database server, if available.
  - All application and preview servers.

The change is implemented after the restart.

Configure the firewalls on the CTERA Portal servers to enable TCP traffic between the servers on the changed HTTPS port.

To connect to the administration portal after changing the administration access port, append the port number to the FQDN of your portal. For example, to connect to Example’s administration portal using HTTPS port 2222, use the following address: `https://example.ctera.me:2222/admin`

## Related articles

[Connect an Edge Filer to a Portal over TCP 443](/v1/docs/how-to-9) [Connect a CTERA Drive Share/Protect (Agent) to a CTERA Portal over TCP 443](/v1/docs/how-to-15)