• I see the following error in the error log

    1)
    [Wed Feb 10 04:20:08.813387 2021] [proxy_fcgi:error] [pid 19971:tid 139875944363776] [client 3.89.181.164:20064] AH01071: Got error 'PHP message: PHP Fatal error: Uncaught Error: Call to undefined function get_header() in /home/470797.cloudwaysapps.com/mhydpxbvzu/public_html/wp-content/themes/hueman/index.php:1\nStack trace:\n#0 {main}\n thrown in /home/470797.cloudwaysapps.com/mhydpxbvzu/public_html/wp-content/themes/hueman/index.php on line 1', referer: https://surdelsur.com/es/

    2)
    [Wed Feb 10 04:20:05.492099 2021] [autoindex:error] [pid 19971:tid 139875986327296] [client 54.224.145.163:20036] AH01276: Cannot serve directory /home/470797.cloudwaysapps.com/mhydpxbvzu/public_html/wp-content/themes/hueman-child-master/: No matching DirectoryIndex (index.php,default.php,index.html,default.html) found, and server-generated directory index forbidden by Options directive, referer: https://surdelsur.com/es/

    3)
    [Fri Feb 05 11:01:24.981808 2021] [autoindex:error] [pid 14324:tid 139876481496832] [client 54.186.14.141:32216] AH01276: Cannot serve directory /home/470797.cloudwaysapps.com/mhydpxbvzu/public_html/wp-content/plugins/onesignal-free-web-push-notifications/sdk_files/: No matching DirectoryIndex (index.php,default.php,index.html,default.html) found, and server-generated directory index forbidden by Options directive

    What means? How to fix?
    Thanks in advance

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Moderator bcworkz

    (@bcworkz)

    Undefined function error is usually due to code or a browser directly requesting a *.php file instead of making a normal WP permalink style of request. When a .php file is directly requested, the WP environment is not initialized and its functions are not available. The solution is to make a proper permalink style request. The challenge is to find where the request is made and to determine what should be requested instead.

    Cannot serve directory is also caused by bad requests, it’s assuming an index.php file exists where there is none. There wouldn’t normally be requests that deep into the file system. Whatever is making these requests is doing it wrong.

Viewing 1 replies (of 1 total)
  • The topic ‘[autoindex:error] and [proxy_fcgi:error]’ is closed to new replies.