To allow replication between the primary and secondary servers, traffic must get through the Windows Firewall (or any other third-party firewalls). When you installed the Hyper-V role on the servers by default exceptions for HTTP (80) and HTTPS (443) are created. If you're using these standard ports, you'll just need to enable the rules:
To enable the rules on a standalone host server:
Open Windows Firewall with Advance Security and click Inbound Rules.
To enable HTTP (Kerberos) authentication, right-click Hyper-V Replica HTTP Listener (TCP-In) > Enable Rule.
*-> To enable HTTPS certificate-based authentication, right-click Hyper-V Replica HTTPS Listener (TCP-In) > Enable Rule.
For Hyper-V Replica with certificate-based authentication, both the primary and replica Hyper-V servers need X.509 v3 certificates with Server and Client Authentication extended key usage (EKU), exported private keys, and the host's FQDN in the subject name, installed in the local computer's Personal store. You also need network connectivity, enabled firewall rules for HTTPS, and the root certificate must be trusted on both the primary and replica servers.
Reference:
https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/set-up-hyper-v-replica