issue in ngrock container

[dolly1997]

Hi @jleach @reflectivedevelopment @swcurran

We have been using aries python mediator since 1 year. As due to some security policy we cant use ngrock service so what i did i made some changes in start.sh file and build the images and ran the containers. ngrock container was not in running state.but still invitation url we were getting from mediator-service container and everything was working fine. we were able to communicate between mobile and mediator.

Now after some months I deleted the containers as well as images and build fresh new images and containers .it is throwing error "ngrock container is unhealthy" due to which mediator-service container is also not running as it has some dependencies.

Attaching scrrenshoot of my start.sh file which i have been using since 1 year .

Kindly look into it .whether we can use mediator without ngrock.

[WadeBarnes]

You can absolutely use the mediator without ngrock, you just need to securely expose the Caddy proxy. ngrock support is only included to allow for local use during development. You can find an example OpenShift configuration here; https://github.com/bcgov/openshift-aries-mediator-service

[dolly1997]

Thankyou for the response @WadeBarnes
So I am using ubuntu so i have to add caddy port in my respective security group right.so that it should be exposed right?

I would like to inform you ngrock anyway I am not using. i have commented the ngrock service from docker-compose file also.can u plz confirm on the shell file that i have shared is correctly configured or not..

Because if I put the invitation url of mediator in my aries bifold application it is throwing error of message unpack failed.

[WadeBarnes]

Yes, the Caddy proxy will need to be exposed publicly.