From 3adb91d9bb0c134f6f787ad0e54616e3d126da5c Mon Sep 17 00:00:00 2001 From: Avinash Ganesh Date: Mon, 12 Sep 2022 12:57:30 +0530 Subject: [PATCH] Updating mq-container docs (#318) --- docs/developer-config.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer-config.md b/docs/developer-config.md index cce7de8..87777f4 100644 --- a/docs/developer-config.md +++ b/docs/developer-config.md @@ -34,7 +34,7 @@ Two channels are created, one for administration, the other for normal messaging ## Web Console -By default the MQ Advanced for Developers image will start the IBM MQ Web Console that allows you to administer your Queue Manager running on your container. When the web console has been started, you can access it by opening a web browser and navigating to https://:9443/ibmmq/console. Where is replaced by the IP address of your running container. +By default the MQ Advanced for Developers image will start the IBM MQ Web Console that allows you to administer your Queue Manager running on your container. When the web console has been started, you can access it by opening a web browser and navigating to `https://:9443/ibmmq/console`. Where `` is replaced by the IP address of your running container. When you navigate to this page you may be presented with a security exception warning. This happens because, by default, the web console creates a self-signed certificate to use for the HTTPS operations. This certificate is not trusted by your browser and has an incorrect distinguished name.