jDownloads Support Forum

Joomla version: 5.4.6
PHP: 8.3.30
Mariadb: 10.11.10
Domain: jewelosman.com

Hi, I use JDownloads for my Joomla extensions.

After updating JDownloads from version 4.1.4 to 4.1.5, my JED-listed extensions cannot be installed via 'Install from Web'. Additionally, my extensions are not updating through Joomla's extension update feature. In both cases, a 500 error is displayed after trying for a long time. I have rolled back to 4.1.4, and everything is working properly again.

Note that I use this type of link in my extension update XML file-
        <downloads>
            <downloadurl type="full" format="zip">https://jewelosman.com/jo-smart-search/send/5-modules/49-jo-smart-search</downloadurl>
        </downloads>

        <downloads>
            <downloadurl type="full" format="zip">https://jewelosman.com/jo-opening-hours?task=download.send&amp;id=80:jo-opening-hours&amp;catid=5</downloadurl>
        </downloads>

Hi,
thanks for the report and sorry for the trouble. A few quick checks that help us find the 500 cause:

1. Check your webserver/PHP error log for the exact 500 line (timestamp when you triggered the update). Please paste the relevant log lines (stack trace / error message).

2. Try the direct download URL from the XML with curl on the server to see the HTTP response and headers:

- curl -I 'https://.../send/5-modules/49-jo-smart-search'
- curl -v 'https://.../send/5-modules/49-jo-smart-search'
  Post the response (status code, Content-Type, and any redirect or PHP error output).

3. Temporarily enable Joomla debug & maximum PHP error reporting, then reproduce the failure — that usually reveals the thrown exception or fatal error.

4. Possible suspects: PHP 8.3 strictness / a security module (mod_security) blocking querystring download URLs / malformed update XML or download handler throwing an exception for certain URLs.

Workarounds until we know more:
- Try using a plain zip direct link (no query string) in the <downloadurl> and test again.
- Roll back to 4.1.4 if you already confirmed it works (you already did that and it helped).

If you paste the server error log lines and one curl output here, I'll analyse and propose a concrete fix or quick patch.