• Resolved raul_coca

    (@raul_coca)


    <Files *.ini>
    Order deny,allow
    Deny from All
    </Files>
    SetEnv PHPRC /home/website/
    <Files *.ini>
    Order deny,allow
    Deny from All
    </Files>
    SetEnv PHPRC /home/website/
    # 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

Viewing 15 replies - 16 through 30 (of 39 total)
  • 3pepe3

    (@3pepe3)

    it seems that now is working
    To recreate the .htacces you must save the permalink structure
    https://www.ziarulargesenilor.ro/wp-admin/options-permalink.php

    Thread Starter raul_coca

    (@raul_coca)

    Yeah it works, but this is the normal behaviour, it only spikes ocasionally.

    Moderator James Huff

    (@macmanx)

    When you generate a new .htaccess file by re-saving your permalinks as mentioned above, this will recreate everything between the begin/end WordPress block.

    Leave that in place for an hour (or longer), and if you have no trouble, slowly begin to introduce the blocks from your old .htaccess file waiting an hour (or longer) between each. If you see the 500 again, you’ll know that the last block you added is the cause of all the trouble.

    Thread Starter raul_coca

    (@raul_coca)

    I don’t need the stuff in the old .htaccess, so this means that I can leave it as it is.

    3pepe3

    (@3pepe3)

    Do you know who is doing the request to the xmlrpc.php file ?
    in your access.log do you have some entries like this ?
    xxx.xxx.xxx.xxx- - [06/Nov/2014:11:29:07 +0100] "POST /xmlrpc.php HTTP/1.1" 200 210 "-" "-"

    Thread Starter raul_coca

    (@raul_coca)

    Yes. The problem is that I can’t see the errors right now because the site is working fine, I have seen that error logs shows the errors only when the website is down.

    Thread Starter raul_coca

    (@raul_coca)

    After I deleted the .htaccess file and recreated it from scratch, the website is running just fine for 4 hours or so without any issues. Thanks guys.

    Thread Starter raul_coca

    (@raul_coca)

    The topic can be closed. Thanks.

    Thread Starter raul_coca

    (@raul_coca)

    Same problem once again…after 6 hours though.

    Moderator James Huff

    (@macmanx)

    Ok, what is the .htaccess file now? And, is it still the same error in the server error log?

    3pepe3

    (@3pepe3)

    Access log ?!

    Thread Starter raul_coca

    (@raul_coca)

    Yes, the same error.

    Moderator James Huff

    (@macmanx)

    Ok, what is the .htaccess file now?

    Thread Starter raul_coca

    (@raul_coca)

    # 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

    Thread Starter raul_coca

    (@raul_coca)

    Ok, now the error has changed a little.

    [Thu Nov 06 22:02:39 2014] [error] [client 79.118.198.65] (12)Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp for /home/public_html/index.php

    Now the old error isn’t showing anymore:

    Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp for /home/public_html/xmlrpc.php

    The .htaccess begins on the second line, the first line is blank. Maybe the code should be moved upwards.

Viewing 15 replies - 16 through 30 (of 39 total)
  • The topic ‘My .htaccess. Is it set right?’ is closed to new replies.