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

Forum|Forum|1 year ago
December 6, 2024
3 replies
5373 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

Community Manager

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

cindyt72591385

Participating Frequently

We are having the same issues on CF 2021 as well. We also cannot get the CF server to start up after installing this on Azure App Service. We've not had issues with previous versions of CF2021, just with CF2021 update 16 and 17. Once it is installed and we use Kudu to install the packages, we start the app service. Confirm that the app service is running and then look at any packages not installed. When we try to "install all" again, it gives us the notice that the ColdFusion service is not running and the packages will be installed once the server is up and running again.

billr33588170

Participant

We had multiple CF2021 servers failing to startup today as well. coldfusion-out.log indicated it could not reach www.adobe.com.

[date time] Information [main] - Package spreadsheet started...
[date time] INFO [main] - I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {tls}->https://www.adobe.com:443: The target server failed to respond
[date time] AM Information [main] - I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {tls}->https://www.adobe.com:443: The target server failed to respond

We contacted Adobe support and worked with Ravi. The fix for us was to edit this file:

{cf_root} \cfusion\lib\neo_updates.xml and change the packagesurl to use {cf_root} \bundles\bundlesdependency.json instead of the online file www.adobe.com/go/coldfusion-packages

<packagesurl>C:\ColdFusion2021\bundles\bundlesdependency.json</packagesurl>

Note - we did not change defaultpackagesurl

We copied C:\ColdFusion2021\cfusion\lib\neo_updates.xml to each server and they all came up succesfully.

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