The packages repository https://www.adobe.com/go/coldfusion-packages is not accessible

Forum|Forum|1 year ago
December 6, 2024
3 replies
5421 views

Hi, since yesterday I'm getting the following error when trying to install packages on Coldfusion 2021

cfpm_audit.log

The packages repository https://www.adobe.com/go/coldfusion-packages is not accessible. You can only load the packages that are available locally in the /usr/local/lib/CommandBox/server/serverHome/adobe-2021.0.04.330004/WEB-INF/bundles directory.

https://www.adobe.com:443: Connection Reset on the imagem attached

I tried to install on my personal computer at home and at company computer.

Correct answer Priyank Shrivastava.

Hi All,

We are aware of it and we are working on it. There is a redirection issue with the URL.

If you want to install the packages, here is the workaround.

Copy this URL - https://cfmodules.adobe.com/cf2023/bundlesdependency.json in Packages Settings and Submit.

It will directly hit the URL and install the packages.

Priyank Shrivastava.Correct answer

Inspiring

Hi All,

We are aware of it and we are working on it. There is a redirection issue with the URL.

If you want to install the packages, here is the workaround.

Copy this URL - https://cfmodules.adobe.com/cf2023/bundlesdependency.json in Packages Settings and Submit.

It will directly hit the URL and install the packages.

Thanks, Priyank Shrivastava

R

Rafael MartinesAuthor

Participating Frequently

Sorry for the delay about this, but everything is back to normal here in the company since the fix on the redirecting issue, I just want to know if possible, in case of this happens again, is there an option to startup a server with the url of packages already configured? Like an env variable? I tried to find on docs and got nothing.

Charlie Arehart

Community Expert

I agree with Rafael: any mechanism to automate setting this would be very much appreciated (setting the package update url, by other than the admin or editing the xml file holding it). There are a couple of possible means.

First, an env var would certainly benefit both those familiar with adding such to the jvm.config (via the -D arg), as well as those running the cf docker/container image.

Even more valuable could be the ability to control it via the cfsetup tool (added in cf2021). This could help both those audiences, as well being another means to promote use of the cli cfsetup tool. For those not aware, it lets you change virtually any cf admin setting, removing the need to use the cf admin or edit xml files. It can also export or import settings via json (similar to Commandbox cfconfig, a still more powerful tool that long preceded cfsetup). It also lets you easily import that json into the startup of a container. Either way, it could have really helped here, but I found it had no support for this package url setting.

Adobe folks, do you need us to add an ER for this, or are you perhaps already working on it given this repeated update problem?

/Charlie (troubleshooter, carehart. org)

D

Dave Watts

Community Expert

I just noticed you specified "connection reset" as the error, too. That typically means the client (CF) isn't able to validate the certificate, usually because it or one of the certificates in the validation chain has expired. I'm not sure if CF does anything in that case to fix the problem, but if it can't get there and you can (from the console using wget or curl and a non-root user), that's what I'd look for.

Dave Watts, Eidolon LLC

D

Dave Watts

Community Expert

Normally, this indicates a network error of some sort rather than a CF-specific problem. Can you use wget or curl while logged into the shell (not as root) to go to the packages repository? If not, you or your network administrator may have blocked direct access. Can you see if there's a proxy server being used? CF won't know about that in some cases. In the short term, you can download the packages manually, then point CF to the internal location instead of the default one.

If this just happened immediately after a CF update, look for update-specific issues or bugs. You might be able to do that at the official Adobe bug tracker (https://tracker.adobe.com/). You should tell us if that's the case, too.

Dave Watts, Eidolon LLC

R

Rafael MartinesAuthor

Participating Frequently

Hi, thanks for the answer this didn't happened after an update I was just deploying some new code on homologation server and this happened on the images attached