Our Development and QA environments are running as on-prem SNO instances of MAS 9.1. These are upgraded environments from MAS 8.6. Prior to the upgrade, each of the instances were made publicly available using an Nginx reverse proxy. I previously posted here in TechXChange the steps necessary to make a SNO instance public facing.

It seems something has changed within the configuration of MAS 9.1. Since upgrading to MAS 9.1, the Nginx configuration no longer functions and the applications are not viewable as public facing applications. I have tried various reconfigurations of the Nginx "conf" file to no avail. Each iteration of the configuration file introduces new challenges and/or errors.

Has anyone been successful in making a MAS 9.1 SNO environment public facing?

Hi Craig

Are you running SNO on the public cloud or is it on-premise?

Our Development and QA environments are running as on-prem SNO instances of MAS 9.1. These are upgraded environments from MAS 8.6. Prior to the upgrade, each of the instances were made publicly available using an Nginx reverse proxy. I previously posted here in TechXChange the steps necessary to make a SNO instance public facing.

It seems something has changed within the configuration of MAS 9.1. Since upgrading to MAS 9.1, the Nginx configuration no longer functions and the applications are not viewable as public facing applications. I have tried various reconfigurations of the Nginx "conf" file to no avail. Each iteration of the configuration file introduces new challenges and/or errors.

Has anyone been successful in making a MAS 9.1 SNO environment public facing?

Our Development and QA environments are running as on-prem SNO instances of MAS 9.1. These are upgraded environments from MAS 8.6. Prior to the upgrade, each of the instances were made publicly available using an Nginx reverse proxy. I previously posted here in TechXChange the steps necessary to make a SNO instance public facing.

It seems something has changed within the configuration of MAS 9.1. Since upgrading to MAS 9.1, the Nginx configuration no longer functions and the applications are not viewable as public facing applications. I have tried various reconfigurations of the Nginx "conf" file to no avail. Each iteration of the configuration file introduces new challenges and/or errors.

Has anyone been successful in making a MAS 9.1 SNO environment public facing?

Craig,

Have you tried following https://www.ibm.com/support/pages/node/6966684 which I think was available in 8.9 and higher. The benefit to this is that it updated all the appropriate resources in OpenShift, Routes, Pods so that you can properly expose it to the internet and don't need NGINX or reverse proxies. 

Mike

Our Development and QA environments are running as on-prem SNO instances of MAS 9.1. These are upgraded environments from MAS 8.6. Prior to the upgrade, each of the instances were made publicly available using an Nginx reverse proxy. I previously posted here in TechXChange the steps necessary to make a SNO instance public facing.

It seems something has changed within the configuration of MAS 9.1. Since upgrading to MAS 9.1, the Nginx configuration no longer functions and the applications are not viewable as public facing applications. I have tried various reconfigurations of the Nginx "conf" file to no avail. Each iteration of the configuration file introduces new challenges and/or errors.

Has anyone been successful in making a MAS 9.1 SNO environment public facing?