Hello Ben, sorry it took a moment to be able to get back to you in this matter.
Re. "I have to explicitly visit the fineract server endpoint and select to proceed to site before the page loads.", yes, that's documented e.g. on https://github.com/openMF/community-app/#connecting-to-a-mifosx-platform-running-on-a-different-host. To make local development easier, your browser has an option to permanently accept Fineract's development self signed certificate. Re. a real world production deployment, and how I handled the Cert issue on https://www.fineract.dev, I'm contributing https://github.com/apache/fineract/pull/1503/files with proposed documentation about this, and hope that it helps to clarify this for you, and others in the future. Best, M. _______________________ Michael Vorburger http://www.vorburger.ch On Mon, Nov 2, 2020 at 8:42 PM Ben Njoka <[email protected]> wrote: > > Hi Michael, > > > I deployed Fineract as an executable jar on a Google Cloud VM. > > java -jar fineract-provider.jar > End Point: https://IP:8443/ > > I also have an angular frontend served by a nginx web server listening on > port 80 on the same VM - http://IP > My frontend points to the Fineract API server at *https://IP > <https://IP>: 8443/fineract-provider/api * defined in environment.prod.ts > > I can access my frontend at http://IP > However, the page does not load due to Cert err. I have to explicitly visit > the > fineract server endpoint and select to proceed to site before the page loads. > > Question: > How did you handle the cert issue in your GCP deployment? > I expect the browser to at least give me the option to > proceed with warning with the self-signed cert > > Thanks, > Ben. > > <[email protected]> >
