Same Problem here with 6.0.1, proxy on server without user and pass.

From the amount and level of information you have provided it is really impossible to provide any help or assistance. Please provide as much detail as possible about your proxy and its configuration settings.

Summary

I am experiencing an issue with Joomla 6 where core updates work correctly, but extension update checks fail when the site is behind an HTTP proxy.

I am not an expert on this topic, but I tried to gather as much relevant technical information as possible.

Environment

• Joomla version: 6.0.1
• PHP version: 8.3 (PHP-FPM)
• Operating system: Debian 12
• Web server: Apache with PHP-FPM
• Database: MariaDB 10.11
• Proxy type: HTTP forward proxy
  • No authentication (username and password are empty)
  • Configured in Joomla (proxy host and port only)
• PHP configuration:
  • allow_url_fopen = Off

Observed behaviour

• Joomla core updates are fetched successfully and show no errors.
• Extension update checks fail with the error message:
  Could not open update site

This occurs consistently for multiple third-party extensions.

Proxy and network verification

To verify that the proxy and network configuration are working correctly, I performed the following tests via SSH on the same server.

CLI curl test via proxy

curl -Iv -x http://proxy:3128 https://cdn.akeeba.com/updates/pkgakeebabackuppro.xml

Result: successful response.

PHP cURL test via proxy

php -r '
$ch = curl_init("https://cdn.akeeba.com/updates/pkgakeebabackuppro.xml");
curl_setopt($ch, CURLOPT_PROXY, "proxy:3128");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
var_dump(curl_exec($ch) !== false);
'

Result: true.

Logs

I checked the Joomla log directory, but no log entries are written when this issue occurs.
It appears that the request fails before anything is logged.

Additional notes

Given that:

• Joomla core updates work
• CLI curl via proxy works
• PHP cURL via proxy works
• allow_url_fopen is disabled

it appears that in Joomla 6 the proxy configuration may not be consistently applied to the HTTP requests used for extension update checks.

The same proxy setup worked correctly with latest Joomla 5 on the same infrastructure. The HTTP transport selection option was already removed in Joomla 5, but extension update checks still worked there. The issue only appeared after upgrading to Joomla 6.

Thank you very much for your time and support — I hope this helps.

How can I manually install the update on Joomla 6.0.2? The update check is blocked and ends with a timeout!

How do I check the extensions now?

Is that a security problem?

Can I return to Joomla 5.0.x?

In my case, the update to Joomla 6.0.2 works without any problems. Unfortunately, the extension still does not work.

How can I manually install the update on Joomla 6.0.2? The update check is blocked and ends with a timeout!

You can download and install the Update Package via upload: https://downloads.joomla.org/cms/joomla6/6-0-2

I see connections that do not go over proxy to the following IP addresses:

172.67.74.86
104.26.14.15

And yes, I can download the update manually...

But: In the backend, the Joomla update check runs on an error message, timeout!

And still: No update check for the extensions!

Update:

I tested this directly in the updater code path.

In libraries/src/Updater/UpdateAdapter.php I switched the HTTP client used for
fetching update sites from Joomla\Http\HttpFactory to Joomla\CMS\Http\HttpFactory.
With this change, extension update checks started working behind our proxy
without any env/http_proxy workarounds.

This makes the issue appear closely related to the missing User-Agent problem
addressed in PR #46553 rather than a general proxy configuration issue.

I did a PR for the Joomla framework, which is used since 6.0 to replace deprecated CMS Http Package (used until 5.4)

joomla-framework/http#71

This should fix update for extensions, when behind proxy or firewall.

Update:

I tested this directly in the updater code path.

In libraries/src/Updater/UpdateAdapter.php I switched the HTTP client used for fetching update sites from Joomla\Http\HttpFactory to Joomla\CMS\Http\HttpFactory. With this change, extension update checks started working behind our proxy without any env/http_proxy workarounds.

This makes the issue appear closely related to the missing User-Agent problem addressed in PR #46553 rather than a general proxy configuration issue.

Update: could you test this PR from @joomdonation that may fix your issue in CMS: #46553
Thank you!

Update: could you test this PR from @joomdonation that may fix your issue in CMS: #46553 Thank you!

The PR would fix the issues in some cases. But I have checked and proxy is completely ignore when we migrated to Http from framework package. There are more works needed to bring proxy support back because from what I see in the code, the framework package even does not support proxy at the moment.

Update: could you test this PR from @joomdonation that may fix your issue in CMS: #46553 Thank you!

The PR would fix the issues in some cases. But I have checked and proxy is completely ignore when we migrated to Http from framework package. There are more works needed to bring proxy support back because from what I see in the code, the framework package even does not support proxy at the moment.

Maybe this is what this open PR will: https://github.com/joomla-framework/http/pull/67/changes

And your system has no direct access to the Internet? Only access to the IP from proxy?

My installations cannot check updates, neither Joomla nor the extensions!

I did the change with CMS!