|
|
|
|
Servers without Parallels Virtual Automation
The table below lists the ports for servers that do not participate in Parallels Cloud Storage clusters and do not use the Parallels Virtual Automation application. "I" in the Description column signals that the port should be opened for incoming traffic and "O" — for outgoing traffic.
|
Port |
Description |
|
22 |
(IO) Used for secure logins via SSH. |
|
80 |
(IO) Used for HTTP connections, e.g., to download Parallels Cloud Server updates and EZ templates from remote repositories. |
|
21 |
(O) Used to connect to the Debian repository to cache Debian EZ templates. |
|
443 |
(O) Used to send problem reports to the Parallels support team. |
|
5224 |
(O) Used to connect to the Parallels Key Administrator server to update Parallels Cloud Server lease licenses. |
|
64000 |
(IO) Used for remote connections to the Parallels dispatcher via Parallels Automation for Cloud Infrastructure. |
|
1621, 1622 |
(O) Used to migrate Containers to virtual machines on servers that run Parallels hypervisor-based solutions. |
|
67 |
Used to support Host-Only adapters in virtual machines. Parallels Cloud Server does not use port 67 for any external connections. |
|
|
Used by various RPC services (e.g., to support NFS shares). Port numbers may differ from system to system. To learn what RPC services are registered on your server and what ports they are using, run this command: # rpcinfo -p localhost |
|
647, 847 |
Reserved by the Linux
|
You may also need to additionally open ports used to connect to remote
yum
repositories. Though most of the repositories can be accessed via HTTP, some may require access via HTTPS or FTP. To check what repositories are currently configured for your system and what protocols are used to connect to them, run the following commands and examine their output:
# yum repolist -v | egrep -e 'baseurl|mirrors'
# curl http://repo.cloudlinux.com/psbm/mirrorlists/psbm6-os.mirrorlist
Top of page
|
Feedback
|