11. Bind certificate to port

Only the IIS binding connects the certificate to the real address. This is where it is decided whether the browser reaches exactly the right application under exactly the right name.

Why this station counts

A binding combination of IP, port and hostname must be unique. SNI allows multiple HTTPS websites on the same IP but requires consistent client and infrastructure support.

The resilient process

1. Open the bindings of the intended X-ERP website.
2. Add HTTPS with scheduled port and hostname and select the verified certificate.
3. Check SNI and conflicts with other websites.
4. Restart the website or IIS in a controlled manner.
5. Test DNS, TLS, login and redirects locally and from a real client.

Functional test - only then continue

• Only the intended website responds.
• Certificate name, chain and validity are error-free in the client.
• HTTP is deliberately blocked or redirected to HTTPS.
• Firewall and reverse proxy use the same target definition.

If the result is not correct

• Wrong website receives the certificate.
• Duplicate port/host combinations produce unpredictable hits.
• Only a test on the server will miss DNS or proxy errors.

This is what you take with you

The public address leads to the correct X-ERP application in an encrypted, clear and reproducible manner.

Video

▶Bind certificate to port

Further information / source

Related topics

1. For system administrators – set up servers and create company databases › 10. Set up certificate
2. For system administrators – set up servers and create company databases › 12. Pass access data to the company database manager
3. For system administrators – setting up servers and creating company databases › 13. Backup, monitoring and recovery

Frequently asked questions