[REGRESSION] Controller Hostname/IP can no longer be configured with Omada SDN Controller 4.1.5
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I'm running the Omada Software SDN Controller inside a docker container (in bridged mode with exposed ports).
When setting up the mail configuration I can no longer configure the public IP of the omada controller. Instead it will pick up the private IP. This is not good, as e.g. password reminder emails will point to the wrong IP.
Please bring back this feature from 3.2.x
Hi,
I've written it down and forwarded this to the engineer for consideration. Thank you for the valued feedback.
ASCII wrote
I'm running the Omada Software SDN Controller inside a docker container (in bridged mode with exposed ports).
When setting up the mail configuration I can no longer configure the public IP of the omada controller. Instead it will pick up the private IP. This is not good, as e.g. password reminder emails will point to the wrong IP.
Please bring back this feature from 3.2.x