500 http error with v1.0.rc.3

  • Resolved Austin Ginder

    (@austinginder)


    1 year, 1 month ago

    After updating to v1.0.rc.3 my website was giving a 500 HTTP response code. The frontend page seemed to load OK, even though it wasn’t giving the proper 200 response code. Digging into server logs this was the error I was seeing.

    2023/10/04 14:43:03 [error] 98140#98140: *22134 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Error: Call to undefined function symlink() in /public/wp-content/plugins/psn-pagespeed-ninja/ress/classes/filesystem/native.php:226
Stack trace:
#0 /public/wp-content/plugins/psn-pagespeed-ninja/ress/classes/imgoptimizer.php(252): Ressio_Filesystem_Native->symlink('/www/...', '/www/...')
#1 /public/wp-content/plugins/psn-pagespeed-ninja/ress/classes/htmloptimizer/base.php(330): Ressio_ImgOptimizer->convert('/www/...', 'webp')
#2 /public/wp-content/plugins/psn-pagespeed-ninja/ress/classes/htmloptimizer/stream.php(370): Ressio_HtmlOptimizer_Base->imgSrcOptimize('https://elevate...')
#3 /public/wp-content/plugins/psn-pagespeed-ninja/ress/classes/htmloptimizer/stream.php(85): Ressio_HtmlOptimizer_Stream->htmlIterate('<!doctype html>...')
#4 /public/wp-content/plugins/psn-pagespeed-ninja/ress/ressio.php(289): Ressio_HtmlOptimizer_St" while reading response header from upstream, client: 74.125.209.39, server: elevatedcommercialroofing.com, request: "GET /?pagespeedninja=0.8706628294296372 HTTP/2.0", upstream: "fastcgi://unix:/var/run/php8.1-fpm-yeladeqi.sock:", host: "elevatedcommercialroofing.com:37308"

    After turning off and on the plugin the errors seem to go away. Not sure if it was a server caching issue or what. Just wanted to mention incase there is a bug that needs fixed or if anyone else notices these errors.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Denis Ryabov

    (@dryabov)

    Call to undefined function symlink()

    This is a strange bug, because symlink is a standard PHP function, and it can only be disabled via the disable_functions directive in the php.ini file. Anyway, this function was actively used in the previous version of the plugin, and I’d recommend enabling it, as it allows the plugin to use the original image until the optimized one is processed.

    Plugin Author Denis Ryabov

    (@dryabov)

    Work on webservers with symlink disabled has been fixed in version 1.0.RC.4.

    Plugin Author Denis Ryabov

    (@dryabov)

    I’m going to mark this thread as resolved in a couple of days. Do you have any comments to add to it?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘500 http error with v1.0.rc.3’ is closed to new replies.