A service address can include an explicit port after the hostname. Removing it can send the player to a different listener and produce a connection or login error. Use the supplied address exactly, including the scheme and port, unless support provides an updated endpoint.
Read the colon in context
The colon after http or https introduces the scheme delimiter. A later colon after the hostname can introduce a port number. These are not interchangeable pieces of punctuation. An app may reject an address if either is missing or pasted into the wrong field.
Do not guess common ports
Changing a supplied port to a familiar number does not make the service more secure or more compatible. The server must actually provide the expected protocol at that location. A working web homepage is also not proof that the streaming endpoint uses the same port.
Document endpoint changes privately
If support changes the service address, keep the previous value in a private note long enough to identify which profiles need updating. Do not publish a list of account endpoints with credentials attached.
A practical sequence
- Retain the original scheme, hostname and explicit port.
- Paste the address into the field for the chosen login method.
- Use only endpoint changes supplied through verified support.
An example
https://example.invalid:8443 and https://example.invalid identify different connection targets unless the server is configured to make them equivalent.
Questions about this topic
Can I remove a port to shorten the address?
Not safely when it was explicitly supplied.
Does a port number prove encryption?
No. The URL scheme and actual server configuration determine transport security.
