2 answers

Must admit I have not tried integrating Secure Gateway service with a container in the cloud. I did at some point try setting up a container on my local PC and configure a Secure Gateway client there... connecting to the Secure Gateway service I had in the cloud, but that's a different use case compared to yours. That said... from your screen shots, it seems to me that you have indeed figured out how to connect the client on your PC to the Secure Gateway service on the cloud... I think I need to understand a bit more about how you set up the destination to your local machine once the connection was established... You have probably set up your local web service as something like localhost:port or how is it inteded to be called from the outside? What I have tried has mainly been enabling connections from the internet (public) to a local web application for instance by using Secure Gateway to set up a secure connection from Bluemix cloud (which provides a public endpoint) to the local web application on a server or my local PC... Not quite sure how you are trying to connect from your container, so maybe you can explain your set up in a bit more detail...?

I must admit I have not tried creating a container in Bluemix and then trying to connect to a local machine via Secure Gateway service... But maybe that's not your real problem or at least based on what you write, I can't say for sure where the problem is. I'm not sure how you were planning on connecting from the container to the local web service. I have tried connecting to a web application both on a server behind a firewall and to a local PC using Secure Gateway service in Bluemix. But this was only a question of setting up the destination in Secure Gateway service to get a public endpoint which basically "published" those applications to the internet... I am still struggling with securing such a connection... not that you need to in all cases, but I would also like to figure that out... especially if I'm opening up a connection to for instance an on premise database...

Anyway, back to your issue... I think I need to understand how your local web service is exposed... is it supposed to be callable via a given port on localhost? or what is your plan? Because from the Secure Gateway connection I can see you set up and got connected, you have to set up a destination from the Secure Gateway service to whatever endpoint your local web service uses, right? So maybe you can explain how the destination was set up.... You say you tried with ip address and port, but which ip and port and does that match your web service ? And then perhaps let me know a bit more about what's running in your container and how you were thinking it could call the local web service