WebP image 403




Wordpress LScache Plugin: WebP image 403

Last Updated on: Wed, 15 Apr 2026 00:00:02
Report number: LSRQYDTY Hello. Thank you for the wonderful plugin. After upgrading the LiteSpeed ??Cache plugin version from 3.6.4 to 4.2 on my site, WebP images newly created / replaced by the image optimization function are no longer displayed properly with a 403 error. Looking at the WebP files on the server, those created after the version 4.2 upgrade have file permissions of 660. WebP before version 3.6.4 was created with 644, which is the same as jpeg and png. Therefore, I tried to create WebP again with Destroy All Optimization Data using Optimization Tools. However, in both versions 4.2 and 4.3, the WebP created will have file permissions of 660. The problem with displaying images on the site was addressed by turning off WebP image replacement and using the original non-optimized file (rewriting the WebP file permissions to 644 also worked). I dont remember making settings that change WebP file permissions around version 3.6.4 to 4.2. However, I also feel that the cause may be due to other plugins, servers, or security settings used on my site. The downgrade to version 3.6.4 is not recommended, so were looking at it in 4.3. I would be grateful if you could give me some hints on what to check to prevent WebP image permissions from becoming 660. The page I need help with: https://tonahazana.com/ Hi, the PHP code for save file is same for v3.6 and v4.2 by file_put_contents https://github.com/litespeedtech/lscache_wp/blob/072fd226ab226e07ff4a3e56751015a83f8915ce/src/img-optm.cls.php#L951 and https://github.com/litespeedtech/lscache_wp/blob/cf4951d18a347897b48fe13d3f777b9aafe8db77/src/img-optm.cls.php#L889 I saw such issue before where LSWS or Linux system user have been incorrect set about umask is it your own server or shared hosting ? Hello, thank you for your reply. I use shared hosting. Should I ask the server administrator about the umask settings? please try this first create a php file in same directory as your wp-config.php file with code



LiteCache Rush: Speed comes from using less, not from doing it faster



Reference