• Resolved WebCodePoet

    (@senjoralfonso)


    Hey, I am using a server with NGINX and can’t update, the error ist, Download failed, Service Unavailable.

    The WordPress Debug only says:

    [01-Mar-2025 19:14:28 UTC] PHP Deprecated: Calling get_class() without arguments is deprecated in /wp-content/plugins/updatepulse-server/inc/nonce/class-nonce.php on line 197
    [01-Mar-2025 19:14:28 UTC] PHP Deprecated: Calling get_class() without arguments is deprecated in /wp-content/plugins/updatepulse-server/inc/nonce/class-nonce.php on line 198
    [01-Mar-2025 19:14:28 UTC] PHP Deprecated: Calling get_class() without arguments is deprecated in /wp-content/plugins/updatepulse-server/inc/nonce/class-nonce.php on line 201
    [01-Mar-2025 19:14:28 UTC] PHP Deprecated: Calling get_class() without arguments is deprecated in /wp-content/plugins/updatepulse-server/inc/nonce/class-nonce.php on line 202
    [01-Mar-2025 19:14:28 UTC] PHP Deprecated: Calling get_class() without arguments is deprecated in /wp-content/plugins/updatepulse-server/inc/nonce/class-nonce.php on line 204
Viewing 3 replies - 16 through 18 (of 18 total)
  • Thread Starter WebCodePoet

    (@senjoralfonso)

    Hey again, It is a bare metal server, and I am the only admin.
    I already shared all the outputs of the following with you:

    • Nginx error logs (/var/log/nginx/error.log)
    • PHP-FPM logs (/var/log/php-fpm.log)
    • WordPress debug logs (enable?WP_DEBUG?in?wp-config.php)
    sudo nginx -t
    nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    nginx: configuration file /etc/nginx/nginx.conf test is successful

    Server:

    • Kernel: 6.8.0-55-ubuntu22.04-generic
    • Format: x86_64
    • WordPress: 6.7.2
    • HTTP-Server: nginx/1.26.2
    • PHP-Version: 8.4.4 (FPM-FCGI)
    • PHP-Limit: 256M, Max-Usage: 71% (181 MB von 256 MB)
    • CPU AMD EPYC-Milan Processor: 16 Cores
    • RAM: 16 GB

    Now the Voodoo: If I copy the “Update Now” Link: /wp-admin/update.php?action=upgrade-plugin&plugin=dummy-plugin%2Fdummy-plugin.php&_wpnonce=92c6085ddb to the browser it runs and updates all fine. If I click it, it get the error 503.

    Thread Starter WebCodePoet

    (@senjoralfonso)

    It finally works now on all instances except the one with the server itself.
    So, I can no work with it, as long as I update the plugins on the main instance on which the update server runs, by hand.

    Plugin Author Alexandre Froger

    (@frogerme)

    Hi!

    Do you mean you had UP Server and Dummy Plugin on the same instance of WordPress?
    If that was the case, this is definitely the issue: when WordPress attempts to go into maintenance mode to get its plugins updated, it cannot serve updates at the same time!

    If that was indeed the source of the problems, then I am glad it was discovered and that you are able to start providing updates!

Viewing 3 replies - 16 through 18 (of 18 total)
  • You must be logged in to reply to this topic.