Script to install BcContainerHelper fails

[eclipses]

The script in the file "Install-BcContainerHelper.ps1" is failing with the following error:

Exception calling "DownloadString" with "1" argument(s): "The remote name could not be resolved:
'bccontainerhelper.azureedge.net'"

Please do I need to change anything in this script or it is something you can fix from your side?

[RadoArvay]

Yes, I wanted to ask the same question. I use the "Hello World" pipeline script to install BCH for few years.
Is there any other path to download BCH directly or we need to use a general way to update PWS module?

[shashihubgit]

+1

[ralf-escher]

Same problem here.
All our pipelines show this error.

[BennoVendrig]

We also have this issue. All pipelines shows this error.

[freddydk]

Please replace the URL with bccontainerhelper.blob.core.windows.net instead of bccontainerhelper.azureedge.net

[ralf-escher]

Thanks. Is this a temporary solution?

[freddydk]

This is a permanent solution.
bccontainerhelper.azureedge.net is no more.

[freddydk]

sorry for the inconvenience - I totally forgot that one version of that script used this hostname,

[BennoVendrig]

I've changed the path and the pipeline is running again but still in progress. Thanks for the quick response and solution.

[eclipses]

I confirm that changing the url from bccontainerhelper.azureedge.net to bccontainerhelper.blob.core.windows.net fixed the issue.

[MUR-SDP]

Thanks very much and apologies for the duplicate.

[freddydk]

No problem @MUR-SDP - just saves me the time of writing the same again.
I am very happy that people are creating issues here instead of posting on twitter, linkedin, my blog, facebook or other places - this is the right place:-)

And sorry for not thinking of this problem beforehand - I think I did consider most other usages of azureedge.net - but this one was forgotten...
Not sure I could have done anything to reach people with this information beforehand - but the solution is fortunately easy

[RadoArvay]

And sorry for not thinking of this problem beforehand - I think I did consider most other usages of azureedge.net - but this one was forgotten... Not sure I could have done anything to reach people with this information beforehand - but the solution is fortunately easy

To be honest, I did not think that so many of us use the script from "demo" pipelines.