getting 403 error after editing Web domain optioins

[thibotus01]

I tried to create a new subdomain but I got the same error. And I tried to create a new subdomain associated to another domain and it works without problem... weirddd

[thibotus01]

I have just backup my last .vhost file and I realized that the rewrite rule was different:

previous one (works) :

RewriteEngine on
    RewriteCond %{HTTP_HOST}   ^media.domain.com[NC]
    RewriteRule   ^/(.*)$ /home/clients/client0/web12/web/media/$1  [L]
    RewriteCond %{HTTP_HOST}   ^domain2.com [NC]
    RewriteRule   ^/(.*)$ http://www.domain.com/$1  [R]
    RewriteCond %{HTTP_HOST}   ^mrtg.domain.com [NC]
    RewriteRule   ^/(.*)$ /home/clients/client0/web12/web/munin/$1  [L]

new one (403 error):

RewriteEngine on
    RewriteCond %{HTTP_HOST}   ^media.domain.com [NC]
    RewriteRule   ^/(.*)$ /media/$1  [L]
    RewriteCond %{HTTP_HOST}   ^domain2.com [NC]
    RewriteRule   ^/(.*)$ http://www.domain.com$1  [R]
    RewriteCond %{HTTP_HOST}   ^mrtg.domain.com [NC]
    RewriteRule   ^/(.*)$ /munin/$1  [L]

I don't know why ISPCONFIG changed this.

[till]

I don't know why ISPCONFIG changed this.

We had "the new one" as default in ispconfig 3 from the beginning. Then we changed it to the code that you named "the previous one" and after this change the rewriting failed on almost all installed systems so we had to revert back to the code to "the new one".

I also checked the apache documentation and the code "the new one" is the correct one. So thats not the source of the problem.

We will have to find yout why this code does not work on your server. Please try to put the rewrite code part into a directory directive:

<Directory /home/clients/client0/web12/web/>
RewriteEngine on
RewriteCond %{HTTP_HOST} ^media.domain.com [NC]
RewriteRule ^/(.*)$ /media/$1 [L]
RewriteCond %{HTTP_HOST} ^domain2.com [NC]
RewriteRule ^/(.*)$ http://www.domain.com$1 [R]
RewriteCond %{HTTP_HOST} ^mrtg.domain.com [NC]
RewriteRule ^/(.*)$ /munin/$1 [L]
</Directory>

[thibotus01]

It doesn't work.

media.domain.com display me the content of domain.com

[thibotus01]

The problem is still unsolved :/
I temporary use the "old rule".

[thibotus01]

I found the problem !

Website running under Wordpress, subdomain media.domain.com seems to be reserved and used by the CMS. By resulting a 403 error...

I tested twice on 2 websites running with Wordpress.

My question is : why using a Rewrite rule instead of a real vhost for subdomain?

Should I open a ticket?

[till]

media.domain.com display me the content of domain.com

Thats the intended behaviour of the subdomain function.

Looks as if you used the subdomain function (which is for subdomains that do not have a its own directory) instead of creating a new website.

If you like to have a subdomain which has its own directory (new vhost), you click on "new wesbite" and then enter sub.domain.com into the domain field.

[thibotus01]

Take a look on my last message.

The rewrite rule is in conflict with the wordpress rewrite system. And the problem will always be if you create "media" as a sub-domain with a website running Wordpress.

Edit : I read your PM, I understand now... You can reply what you said.

[till]

Please see my answer in #17 in this thread. You used thew rong function. Instead of creating a new website, you created a subdomain record for a existing website which has to point to the website main dir as it is used for cms systems that are capable of running multidomain setups, e.g. wordpress mu, typo3 or joomla.

But you wanted to have a separate directory for a cms without multidomain support, so you must choose to create a new website and not a subdomain for a existing website.