Agent connects to cluster on 443

[henk_stobbe]

Hello,

This is not documented, but why can a agent also communtate on port 443. And why shoult does not be done?

KR Henk

[Julius_Loman · Accepted solution]

For Dynatrace SaaS tenants this is correct, agents communicate on 443/tcp in SaaS environment.

In Dynatrace Managed tenants agents communicate on 8443/tcp.

If there is security gateway in the environment, agent communicate to security gateway on 9999/tcp.

[rswarnka]

Hi Julius, My corporate network team has detected that the port 8443 is not being used for a SaaS deployment, only 443 is being used... However documentation says:

Ports 443 and 8443 must remain open to allow incoming traffic from your data center.

Can you pl. explain why 8443 is required to be kept open between the monitored server till SaaS cluster on firewall? Shouldn't this un-used port be closed?

Pl. help.

[Julius_Loman]

You really don't need 8443/tcp in SaaS. I think this is a typo in the documentation.

[rswarnka]

Thanks Julius! I think I mistakenly referred to managed documentation:

https://www.dynatrace.com/support/help/deploy-dynatrace/managed/configuration/which-network-ports-does-dynatrace-server-use/

[henk_stobbe]

Hi Julius,

The issue is that we have a Managed environment, and still 443 works,

KR Henk

[JamesKitson]

How are you telling it to communicate on 443? The reason this shouldn't be done is that the UI and REST API calls come in through 443 in managed:

https://www.dynatrace.com/support/help/installatio...

James