Support » Fixing WordPress » Siteground ModRewrite

  • Hello, has anyone been able to get mod_rewrite working on Siteground? I have had them since April and have tried on and off to get them working. I have asked the Support group there to look into it and they always just point me to the Apache Documentation.

    Here is my htaccess file:
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    # END WordPress

    Anyhelp would be great! Thanks!

Viewing 14 replies - 1 through 14 (of 14 total)
  • They point you to the apache documentation? Does that mean you have access to play with httpd.conf?

    If so, make sure that not only do you have mod_rewrite running, but also have AllowOverride enabled for your blog’s directory.

    More trouble-shooting ideas on the Permalinks page in the codex.

    Sadly, I do not have access to the httpd.conf file. I have tried everything I can on the Codex page, even using the index.php does not work for me. Which it did on my previous host.

    I’m still using WP 2.0.2, but I don’t think that should really be causing the problem.

    I did notice that when I try: /%year%/%monthnum%/%day%/%postname%/
    it puts the post number instead of the postname.

    Hi, Can anyone help me with this? Anyone else using Siteground and able to use mod_rewrite?



    What are you actually trying to do ? Maybe if you could explain what you are trying to achieve, we will be able to point you in the right direction ?



    I am trying to get Permalinks working.

    Dear black2004,

    We have reviewed your case and have found out that there were two lines in your htaccess file that are not needed:

    <IfModule mod_rewrite.c>

    We have disabled these two lines and you should no longer experience problems with the mod_rewrite

    Please post a ticket to SiteGround support team if you still experince difficulities.



    You should have a warning about that on your site – because on the majority of other servers/hosts the default .htaccess file generated by WP, which has those lines, is working.

    SiteGround: It seems that this is still not working. Can you please double check?

    Also I’d love to post to your support groups, but it seems that the only way to directly e-mail you any more is if the server is down. Can you provide instructions on how to contact you?

    I have also posted in your siteground forums.


    You can reach our support team by posting a ticket and here is a detailed explanation how this can be done:



    Thank you. However, can I suggest you create a way to e-mail you about other technical related issues. When I follow that link there is no option to e-mail support. Just to purchase a developer.

    Here’s the latest information from siteground:
    Actually, the issue is caused by the fact that all your WordPress files are in a subdirectory named /wordpress, whereas the blog is being accessed via your domain name only, since the script’s index is in your main directory. This makes the WordPress and mod_rewrite recognize the rewrite base as your domain name only instead of, which is resulting in the issue.

    However, mod_rewrite and WordPress permalinks are working just fine on our servers as you can see from the test installation I have performed here:

    The sample permalink with the default Hello World article is:

    If you wish, we can move all your WordPress files in the main directory of your account, which will fix the Permalinks issue. Please advise if this is suitable for you.

    I don’t agree with them that moving the wordpress support files to the main directory is going to help. I have it set up in /wordpress/.

    Can anyone else suggest something? I have gone through all the Codex suport files for what is there.

    Yes, the AllowOverride All option is enabled in the main Apache configuration file. However, the issue comes from the fact that the rewrite base and the actual WordPress files directory differ, when the WordPress files are in a separate directory, which is why the permalinks are not functioning properly. I am afraid that moving your wordpress files in the main directory is the only option for a reliable functioning rewrite engine at the moment.

    Can someone please confirm this response? I have had my wordpress setup with the index.php in the / and all other wordpress files in /wordpress/ before with no issues.

    Send them to read this one:
    which is proof that the setup you have works on every other host/server.
    (of course, assuming you did follow the steps described in the tutorial)

    Thanks. I sent them that and here’s the reply:

    Well, according to the WordPress documentation, the permalinks should indeed work with your current setup, but it seems that for some reason they are not, even with correctly updated permalinks structure. Alas, there is nothing out of the ordinary with the Apache and more specifically with the mod_rewrite configuration on our servers, which should be causing the issue. I am certain that this comes from the fact that the rewrite base for the rewrite rules adn conditions is different from the actual physical path to your WordPress files. Thus, as I have stated above, I believe that the only available solution at the moment is moving your WordPress files in the main directory.

    As for the register_globals directive – it is set to On.

    So now I’m not sure what to really do….

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Siteground ModRewrite’ is closed to new replies.