- SAP Managed Tags:
So you're happily coding your awesome Business Technology Platform(BTP) solution using SAP's Business Application Studio(BAS) and you're really liking the(what I call) piecemeal deploy little rocket icon. It makes your development sooo much faster than having to do a full build/deploy/test cycle.
Then your security manager emails you with a mandate to lock down your HANA Cloud(or Hana As A Service) instance so that it's not open to the whole world, just the corporate servers.
So you dutifully bring up the HANA settings and flip from "Allow all IP addresses" to "Allow only specific IP...". Makes sense so you enter the network range of the corp servers. You save and wait a little for the HANA instance to do it's thing.
You return to BAS to get some more accomplished before lunch and now you're getting this error upon hitting your favorite rocket icon.
Connecting to the container "F0CF3EC39E304DD49F4758D75E1E25AD"...
Deployment to container F0CF3EC39E304DD49F4758D75E1E25AD failed - error: Connection failed (RTE:[89008] Socket closed by peer (ffa845c4-c70e-4774-ba37-c0a6fdf16850.hana.prod-us21.hanacloud.ondemand.com:443)) [Deployment ID: none].
Error: Connection failed (RTE:[89008] Socket closed by peer (ffa845c4-c70e-4774-ba37-c0a6fdf16850.hana.prod-us21.hanacloud.ondemand.com:443))
Well seems wherever BAS is running in your situation is currently not being considered part of the BTP(internal network routing). This should be fixed soon and make this blog post irrelevant, but if you're running into this issue or something similar, don't feel stuck. Here's a work-around to try.
Figure out the IP address where BAS's DevSpaces are connecting from by using the built in curl command from a new terminal window.
Cut the IP address returned and add it to your HANA configuration(this one is for US10 but yours may be different.
Now after letting HANA settle down, you should be able to deploy like a rocket again!
Let me know if you have and questions or issues by leaving me a question below or better yet, asking it on the SAP community.
-Andrew
Then your security manager emails you with a mandate to lock down your HANA Cloud(or Hana As A Service) instance so that it's not open to the whole world, just the corporate servers.
So you dutifully bring up the HANA settings and flip from "Allow all IP addresses" to "Allow only specific IP...". Makes sense so you enter the network range of the corp servers. You save and wait a little for the HANA instance to do it's thing.
You return to BAS to get some more accomplished before lunch and now you're getting this error upon hitting your favorite rocket icon.
Connecting to the container "F0CF3EC39E304DD49F4758D75E1E25AD"...
Deployment to container F0CF3EC39E304DD49F4758D75E1E25AD failed - error: Connection failed (RTE:[89008] Socket closed by peer (ffa845c4-c70e-4774-ba37-c0a6fdf16850.hana.prod-us21.hanacloud.ondemand.com:443)) [Deployment ID: none].
Error: Connection failed (RTE:[89008] Socket closed by peer (ffa845c4-c70e-4774-ba37-c0a6fdf16850.hana.prod-us21.hanacloud.ondemand.com:443))
What gives?
Well seems wherever BAS is running in your situation is currently not being considered part of the BTP(internal network routing). This should be fixed soon and make this blog post irrelevant, but if you're running into this issue or something similar, don't feel stuck. Here's a work-around to try.
Figure out the IP address where BAS's DevSpaces are connecting from by using the built in curl command from a new terminal window.
curl ifconfig.meCut the IP address returned and add it to your HANA configuration(this one is for US10 but yours may be different.
Now after letting HANA settle down, you should be able to deploy like a rocket again!
Let me know if you have and questions or issues by leaving me a question below or better yet, asking it on the SAP community.
-Andrew
| Partners: If you have a question, click here to ask it in the SAP Community . Be sure to tag it with Partnership and leave your company name in the question so that we can better assist you. |
1 Comment
