ntsili

Thank you again!

I did a long search and found this:
PHP execution limits | Managed WordPress – GoDaddy Help AE
Now, if I understand well, it is Godaddy that blocks all .php in /wp-content !!!! So why yesterday they told me it is a plugin’s error ???

I think it is time to move from Godaddy, their incompetence is inacceptable. Do you know any good alternatives?

• This reply was modified 1 year, 8 months ago by ntsili.
• This reply was modified 1 year, 8 months ago by ntsili.

I just did it using the exact names you proposed and it gives 403 error forbidden.

Whatever .php in this folder, even if it does not exist, will give the same error.

I created a .txt file in the same folder /wp-content/false-plugin/false-plugin.txt and it works ok.

• This reply was modified 1 year, 8 months ago by ntsili.

Sorry for my english, here is the correct message:

Hello again. I contacted Godaddy support and during the 20` of the chat they checked my WP site. They insist that the error is because of the LiteSpeed plugin….

Hello again. I contacted Godaddy support and during 20` of chat they checked my WP site. They insist that the error is because of a plugin′s problem….

Hello again, here a the folders containing a .htaccess file : 


/html/wp-content/mu-plugins/vendor/godaddy/mwc-core/vendor/phenx/php-font-lib/.htaccess

/html/wp-content/plugins/litespeed-cache/data/.htaccess

/html/wp-content/updraft/.htaccess

/html/wp-content/updraft/plugins-old/cloudflare/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/cloudflare/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/cloudfront/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/envhttps/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/loadbalancer/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/serverhttps1/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/serverhttpson/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/serverhttpxforwardedssl1/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/serverhttpxforwardedsslon/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/serverhttpxproto/.htaccess

/html/wp-content/updraft/plugins-old/really-simple-ssl/testssl/serverport443/.htaccess

/html/wp-content/updraft/uploads-old/sucuri/.htaccess

/html/wp-content/updraft/uploads-old/wc-logs/.htaccess

/html/wp-content/updraft/uploads-old/woocommerce_uploads/.htaccess

/html/wp-content/uploads/sucuri/.htaccess

/html/wp-content/uploads/wc-logs/.htaccess

/html/wp-content/uploads/woocommerce_uploads/.htaccess



Should I delete any/all of them?

• This reply was modified 1 year, 8 months ago by ntsili.

In my Fairy theme I activated the CSS options I needed, but excluded style.css in “Tuning Settings – CSS“. Perhaps it can work for you.

If this does not work, you must find the exact CSS that is causing the issue. Check in the developer tools what other CSS load and try to exclude them, one at the time.

Thank you for your reply, there is no .htaccess file in /wp-content/

Another info that could help you is that the .txt files in the same folder open without problems. Example: /wp-content/plugins/litespeed-cache/readme.txt

The problem seems to occur only with php files in the folder. Examples: The guest.vary.php I posted about and also /wp-content/plugins/litespeed-cache/autoload.php etc give forbidden 403.

*Also the “working” .txt file has the same ownership with the .php files.

• This reply was modified 1 year, 8 months ago by ntsili.
• This reply was modified 1 year, 8 months ago by ntsili.
• This reply was modified 1 year, 8 months ago by ntsili.

also : file permission for the file is set to 644. File permissions for parent directories are set to 755.

Thank you for your reply, but the error persists…

I had the same issue, so I installed the needed fonts locally and it worked like a charm. I used local-google-fonts plugin that detects and installs the fonts.