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

24 replies
5681 views
Translate

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.

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

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.

Translate

Thanks, Priyank Shrivastava

T

thumbo

Participating Frequently

This redirection issue, can it cause issues with ColdFusion not starting up?

I've been seeing a weird issue in my dev environment that seems to have started early today,

where it simply won't start because it's timing out, with an error like "https://www.adobe.com:443: The target server failed to respond". I.e. it seems to be timing out trying to reach some adobe services (I'm guessing).

Translate

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.

Translate

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.

Translate

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

Translate