Installed smush on a WP bakery site. Smush is not finding images.

Hi @kallenwebdesign

Sorry to hear you are having this issue.

Could you navigate to WordPress > Tools > Site Health > info, click on “Copy site info to clipboard” and paste in the thread response?

Best Regards
Patrick Freitas

` wp-core

version: 6.2.2
site_language: en_US
user_language: en_US
timezone: +00:00
permalink: /%year%/%monthnum%/%day%/%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: open
environment_type: production
user_count: 6
dotorg_communication: true wp-paths-sizes

wordpress_path: /var/www
wordpress_size: loading…
uploads_path: /var/www/wp-content/uploads
uploads_size: loading…
themes_path: /var/www/wp-content/themes
themes_size: loading…
plugins_path: /var/www/wp-content/plugins
plugins_size: loading…
database_size: loading…
total_size: loading… wp-dropins (2)

db-error.php: true
object-cache.php: true wp-active-theme

name: Kroth (kroth)
version: 1.9.6
author: VictorThemes
author_website: https://victorthemes.com/
parent_theme: none
theme_features: core-block-patterns, menus, post-thumbnails, post-formats, automatic-feed-links, title-tag, html5, woocommerce, breadcrumb-trail, widgets-block-editor, widgets, editor-style
theme_path: /var/www/wp-content/themes/kroth
auto_update: Enabled wp-themes-inactive (8)

Kroth Child: version: 2.0, author: VictorThemes, Auto-updates enabled
Twenty Nineteen: version: 2.5, author: the WordPress team, Auto-updates enabled
Twenty Seventeen: version: 3.2, author: the WordPress team, Auto-updates enabled
Twenty Sixteen: version: 2.9, author: the WordPress team, Auto-updates enabled
Twenty Twenty: version: 2.2, author: the WordPress team, Auto-updates enabled
Twenty Twenty-One: version: 1.8, author: the WordPress team, Auto-updates enabled
Twenty Twenty-Three: version: 1.2, author: the WordPress team, Auto-updates enabled
Twenty Twenty-Two: version: 1.4, author: the WordPress team, Auto-updates enabled wp-mu-plugins (2)

Object Cache Pro (MU): version: 1.18.2, author: Rhubarb Group
System Plugin: author: (undefined), version: 4.92.0 wp-plugins-active (21)

Conditional Fields for Contact Form 7: version: 2.3.10, author: Jules Colle, Auto-updates enabled
Contact Form 7: version: 5.8, author: Takayuki Miyoshi, Auto-updates enabled
Envato Market: version: 2.0.10, author: Envato, Auto-updates enabled
FB Messenger Live Chat: version: 1.5.0, author: Zotabox, Auto-updates enabled
Interactive Geo Maps: version: 1.6.3, author: Carlos Moreira, Auto-updates enabled
Kroth Core: version: 1.9.4, author: VictorThemes, Auto-updates enabled
PixelYourSite: version: 9.4.2, author: PixelYourSite, Auto-updates enabled
Popup Maker: version: 1.18.2, author: Popup Maker, Auto-updates enabled
Redirection: version: 5.3.10, author: John Godley, Auto-updates enabled
Redirection for Contact Form 7: version: 3.0.1, author: Qube One, Auto-updates enabled
Search Engine Visibility: version: 0.5, author: GoDaddy, Auto-updates enabled
Search Exclude: version: 2.0.4, author: QuadLayers, Auto-updates enabled
Slider Revolution: version: 6.6.14, author: ThemePunch, Auto-updates enabled
UpdraftPlus - Backup/Restore: version: 1.23.9, author: UpdraftPlus.Com, DavidAnderson, Auto-updates enabled
WPBakery Page Builder: version: 6.10.0, author: Michael M - WPBakery.com (latest version: 7.0), Auto-updates enabled
WPCode Lite: version: 2.1.1, author: WPCode, Auto-updates enabled
WP Job Manager: version: 1.41.0, author: Automattic, Auto-updates enabled
WP Job Manager - Indeed Integration: version: 2.2.0, author: Automattic, Auto-updates enabled
WP Job Manager - ZipRecruiter Integration: version: 1.1.0, author: Automattic, Auto-updates enabled
Yoast Duplicate Post: version: 4.5, author: Enrico Battocchi & Team Yoast, Auto-updates enabled
Yoast SEO: version: 20.13, author: Team Yoast, Auto-updates enabled wp-plugins-inactive (6)

Akismet Anti-Spam: Spam Protection: version: 5.2, author: Automattic - Anti Spam Team, Auto-updates enabled
GoDaddy Email Marketing: version: 1.4.3, author: GoDaddy, Auto-updates enabled
Smush: version: 3.14.1, author: WPMU DEV, Auto-updates enabled
WP Chatbot: version: 4.7, author: MobileMonkey, Auto-updates enabled
WP Migrate DB Pro: version: 1.7.1, author: Delicious Brains, Auto-updates enabled
WP Migrate DB Pro Media Files: version: 1.4.7, author: Delicious Brains, Auto-updates enabled wp-media

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1808
imagemagick_version: ImageMagick 7.1.0-50 beta Q16-HDRI x86_64 20489 https://imagemagick.org
imagick_version: 3.7.0
file_uploads: File uploads is turned off
post_max_size: 100M
upload_max_filesize: 100M
max_effective_size: 100 MB
max_file_uploads: 20
imagick_limits:
imagick::RESOURCETYPE_AREA: 2 TB
imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
imagick::RESOURCETYPE_FILE: 294912
imagick::RESOURCETYPE_MAP: 2 TB
imagick::RESOURCETYPE_MEMORY: 1,008 GB
imagick::RESOURCETYPE_THREAD: 1
imagick::RESOURCETYPE_TIME: 9.2233720368548E+18
imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, ASHLAR, AVI, AVIF, AVS, BAYER, BAYERA, BGR, BGRA, BGRO, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUBE, CUR, CUT, DATA, DCM, DCR, DCRAW, DCX, DDS, DFONT, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, FARBFELD, FAX, FF, FILE, FITS, FL32, FLV, FRACTAL, FTP, FTS, FTXT, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, HALD, HDR, HEIC, HEIF, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, JNG, JNX, JPE, JPEG, JPG, JPS, JSON, JXL, K25, KDC, KERNEL, LABEL, M2V, M4V, MAC, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPEG, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORA, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PHM, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PS, PS2, PS3, PSB, PSD, PTIF, PWP, QOI, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGB565, RGBA, RGBO, RGF, RLA, RLE, RMF, RSVG, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, STRIMG, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TM2, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMV, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YAML, YCbCr, YCbCrA, YUV
gd_version: bundled (2.1.0 compatible)
gd_formats: GIF, JPEG, PNG, BMP
ghostscript_version: 9.56.1 wp-server

server_architecture: Linux 5.4.206-200.el7.x86_64 x86_64
httpd_software: Apache
php_version: 8.0.29 64bit
php_sapi: cgi-fcgi
max_input_variables: 1000
time_limit: 300
memory_limit: 256M
max_input_time: 60
upload_max_filesize: 100M
php_post_max_size: 100M
curl_version: 8.1.2 OpenSSL/1.1.1u
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true wp-database

extension: mysqli
server_version: 5.7.26-29-log
client_version: mysqlnd 8.0.29
max_allowed_packet: 16777216
max_connections: 1000 wp-constants

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /var/www/wp-content
WP_PLUGIN_DIR: /var/www/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: Undefined
DB_CHARSET: utf8
DB_COLLATE: undefined wp-filesystem

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable

• This reply was modified 1 year, 3 months ago by kallenwebdesign.

Hi @kallenwebdesign

Thanks for response!

It looks fine but there are two things that bother me a bit:

1. This part of the shared info:

WP_HOME: undefined
WP_SITEURL: undefined

Could you please go to “Settings -> General” page in site’s back-end and confirm if you have both “WordPress Address (URL)” and “Site Address (URL)” correctly set there? By “correctly” I mean correct address but also correct “https://” prefix rather than “https://” – if the site is protected by SSL

2. And this earlier error that you got:

The authorization header is missing

This may be related here so please do as follows:

a) go to “Settings -> Permalinks” page and simply re-save current settings; no need to make any changes there, just save settings as they are; after that clear all cache on site/server

b) if that error is still visible, check your site’s main .htaccess file and see if there is this line there

RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

If not, add it right between these two lines

RewriteEngine On
RewriteBase /

so it would become

RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /

and then check if the issue (and the error about missing auth header) is still happening.

Kind regards,
Adam

“Could you please go to “Settings -> General” page in site’s back-end and confirm if you have both “WordPress Address (URL)” and “Site Address (URL)” correctly set there? By “correctly” I mean correct address but also correct “https://” prefix rather than “https://” – if the site is protected by SSL”

These are set correctly.

“go to “Settings -> Permalinks” page and simply re-save current settings; no need to make any changes there, just save settings as they are; after that clear all cache on site/server”

Done.

After the above two things, I cleared the cache, then reactivated the plugin again. Same message unfortunately:

_{Scanning Media Library
0%
Image re-check in progress – 1 second remaining
Note: This is taking longer than expected, please hold on.}

I’ve done a lot of .htaccess files for our other non-wordpress clients, but I have not done much with wordpress .htaccess files, unfortunately. The way ours is set up (by another company, of course) is a little odd, and seems to even have repeated section. I’ll paste it below hopefully removing any XXXXXX identifying info since this is public. I’m not sure where to put the auth line you suggested. Thank you for your patience with my issue.

# BEGIN GD-SSL
<IfModule mod_rewrite.c>
Options +FollowSymLinks
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteCond %{HTTP_USER_AGENT} ^(.+)$
RewriteCond %{SERVER_NAME} ^adXXXXXXXare\.com$ [OR]
RewriteCond %{SERVER_NAME} ^78c\.163\.myftXXXXXXXd\.com$
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]
Header add Strict-Transport-Security "max-age=300"
Header always set Content-Security-Policy "upgrade-insecure-requests"
</IfModule>
# END GD-SSL

# BEGIN WordPress
# The directives (lines) between BEGIN WordPress and END WordPress are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Hi @kallenwebdesign

Thank you for response!

Since suggested steps didn’t help so far, let’s continue and let me start with the .htaccess that you shared:

1. You do indeed have the basic set of WordPress rules duplicated so you can safely remove one of them; it’s not necessary but will “unclutter” .htaccess. To do so, simply remove one (no matter which one) “copy” of this code block:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

2. Now let’s add the auth line. So this part of the code

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

becomes like this

RewriteEngine On
RewriteBase /
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteRule ^index\.php$ - [L]

Once that’s done save the file, clear all caches, re-save permalinks again (important!) and test the site to make sure if everything’s still working fine. Then test Smush also – though I suppose it may still not be working and that is because of yet another part of .htaccess.

Specifically, the code at the very top of it between “BEGIN GD-SSL” and “END GD-SSL” lines. This code suggest that you are hosting with GoDaddy and most likely you are using their CDN to get images offloaded to it, with additional rules to “rewrite” so they appear on site like there were not offloaded.

Smush can only work with images that are local to the site so if images are offloaded to any external storage/CDN then:

1. if there are copies on the site’s local server, Smush would work with them but any optimization it makes would only be reflected once that offload/CDN storage is fully refreshed. Smush can’t do/control that and it’s entirely up to such offload/CDN provideer.

2. but if there is such offload and Smush claims it cannot find images, it usually means that images not only are offloaded to such external storage/CDN but also their “local copies” are removed. Furthermore, Smush won’t follow symlinks or htaccess redirects because it needs to be able to work directly with real files to optimize/edit them.

So that being said, please check if you do have option to diable such CDN/Offload (but I’m not that familiar with GoDaddy’s management – so I”m not sure if this would put images back on the local storage to the site; you may consult that with their support) and if images are then fully present and served from locations “local” to the WordPress intallation – it should work.

Kind regards,
Adam

Then test Smush also – though I suppose it may still not be working and that is because of yet another part of .htaccess.

…This code suggest that you are hosting with GoDaddy and most likely you are using their CDN to get images offloaded to it, with additional rules to “rewrite” so they appear on site like there were not offloaded.

Smush can only work with images that are local to the site…

Hi Adam,

I have deleted the duplicated section in .htaccess and also added the auth line, cleared cache, resaved permalinks, and tested site health again. The errors are gone except for the scheduled event failing which does not seem to be affecting anything.

I then ran smush again and same result. My money is that you are exactly right, the CDN is causing the images to not be found. I ran a gtmetrix test and there was no indication that large/uncompressed images were an issue. And I don’t want to take a chance with crashing the site by removing the godaddy CDN. So at this point I think I should probably give up on smush and on compressing images.

Your attention to my cry for help is very much appreciated. Thank you so much!

Hi @kallenwebdesign,

Hope this message finds you well and thanks for the update.

Sorry to hear about the issue with GoDaddy CDN. We hope you can give Smush a second try in the future.

Let us know if we can mark this issue as solved.

Kind regards,
Laura

Let us know if we can mark this issue as solved.

I will not need further assistance so I think this can be closed. Thanks again!