The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Inaccessible Subdomains - 403 Forbidden

Discussion in 'General Discussion' started by WindSplitter1, Dec 27, 2014.

  1. WindSplitter1

    WindSplitter1 Registered

    Joined:
    Dec 27, 2014
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Website Owner
    Hello everyone.

    I'm having a major problem that unfortunately forced me to get rid of an MW installation, which after fiddling with it for too long, I decided to look for alternatives:

    I created a subdomain to run a few tests so I'd see whay exactly was the problem with the MW script. Installed it via Softaculous without a hitch and visited the link so I could see what was the problem with it.

    I couldn't post (that's the problem with the script, no surprizes there) but what happened next was worse.

    I got a message saying:

    After making other subdomains and installing other scripts and just uploading dummy index.php and.htaccess files, the same happened again and again...

    The only fix seems to be disabling mod_security, which allows me to do everything I want, including using the MW script at will with no restrictions. But this poses a major security risk, also confirmed by my webhost.

    I've searched here on other threads, googled for it, asked in MW site, IRC and Quora but no joy so far.

    The Error Log only shows me errors about older subdomains that have nothing to do with this.
    Using CHMOD 750/755 on public_html and subdomain.domain folder does nothing.


    I have no SSH, programming expertice and, as of now, ideas... Though my main site works flawlessly.

    This is my .htaccess on the Main.

    Code:
    [I]# 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[/I]
    If it helps... my site is: - Removed -
    I think that somehow, the problem with the MW script is connected with this error so, solving this may definitely solve the other problem.

    Please, do help. There are others too which need assistance...
     
    #1 WindSplitter1, Dec 27, 2014
    Last edited by a moderator: Dec 27, 2014
  2. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    14,470
    Likes Received:
    198
    Trophy Points:
    63
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
    Whats a MW script?
     
  3. WindSplitter1

    WindSplitter1 Registered

    Joined:
    Dec 27, 2014
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Website Owner
    MediaWiki. Do you know what could be causing this?
     
  4. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    14,470
    Likes Received:
    198
    Trophy Points:
    63
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
    When you created the subdomain, did you check to make sure it came up in your browser as expected, prior to installing mediawiki?

    Why no surprises for you? I've just installed it into a subdomain via Softaculous as well and can post as expected.

    What happened when you created a subdomain and added only an index.html? Nothing else.

    You should ask your Hosting Provider to check which ModSecurity rule is causing you the problems.


    None of this is a cPanel issue I don't think, your server environment might be though. Assuming the server is running SuPHP, and the subdomain is created and operating as expected prior to installing any script, and, it all works with ModSec disabled, you'll need to figure out which ModSec rule is blocking the script from working properly.

    Assuming the server has ConfigServer ModSec control installed, Installing the MW script and then accessing it or trying to post to it, should generate viewable errors in CMC > ModSecurity Log. With those details you could whitelist that one specific rule ID in CMC.


    You've no doubt seen this page then:
    /http://www.mediawiki.org/wiki/ModSecurity
     
Loading...

Share This Page