02-21-2023, 11:52 PM
Rudy,
You are correct. Self-signed certificates can be only used for development, i.e. testing of your application while you can still use the HTTPS protocol to see how it behaves. But it can't be used in production.
As Joe mentioned above, you need to point your domain (one that you probably have registered as www.yourcompany.com) and point it to the server IP address (the one where the IP application is running on).
Then, whenever you type www.yourcompany.com the Internet DNS servers will resolve that to your server IP (although the request doesn't contain any IP address, only the name of the server). Then the certificate will be correctly accepted by the browser).
You are correct. Self-signed certificates can be only used for development, i.e. testing of your application while you can still use the HTTPS protocol to see how it behaves. But it can't be used in production.
As Joe mentioned above, you need to point your domain (one that you probably have registered as www.yourcompany.com) and point it to the server IP address (the one where the IP application is running on).
Then, whenever you type www.yourcompany.com the Internet DNS servers will resolve that to your server IP (although the request doesn't contain any IP address, only the name of the server). Then the certificate will be correctly accepted by the browser).

