Topic: virtual domain redirect - permission error

[bloodshoteye]

Hi all
Couldn't find the answer in this forum, but may have missed it.
I can successfully redirect from Primary to /opt/wordpress using a url-redirect - this means http://my_domain.com sends the user to /opt/wordpress.

Using the same principal, I need to redirect viewers to /opt/other_wordpress when they hit http://my_other_domain.com.
I'm getting this error:
"You don't have permission to access /other_wordpress on this server."

I can't figure out why not - Directory perms are standard, I'm using the same syntax as for the Primary redirect.
What am I missing?

[cactus]

Using the same principal, I need to redirect viewers to /opt/other_wordpress when they hit http://my_other_domain.com.
I'm getting this error:
"You don't have permission to access /other_wordpress on this server."

I can't figure out why not - Directory perms are standard, I'm using the same syntax as for the Primary redirect.
What am I missing?

Can you access the location you are redirecting to directly? If so, I guess the error is in you redirect script. If niot there might be a problem with the configuration direction of your second wordpress blog.

[bloodshoteye]

Can you access the location you are redirecting to directly?

Not quite sure what you mean by this.

there might be a problem with the configuration direction of your second wordpress blog

Are you referring to Options > General > WordPress address (URL): ?
But I need to access the site via http in order to change that, not so?

I tweaked the url_redirect to
<META HTTP-EQUIV="REFRESH" CONTENT="0; URL=http://my_other_domain.com/opt/other_wordpress">
Now I see this error
The requested URL /opt/agtwdpr/ was not found on this server.
I've tried various versions of this, but I'm not clued-up enough to figure out the correct syntax.

[cactus]

Not quite sure what you mean by this.

Simple, you probably made a redirect script in your Primary ibay to refer to the location you shared your /opt/wordpress location? Correct? If so you should be able to open that location in a browser as well by entering the direct url. For instance if you configures the /opt/wordp[ress to be available as location /blog1 you should be able to access it as http://ipnumber/blog1 or http://servername/blog1, if you can not than your problems is not located in the redirect but in the configuration of your blog in the webserver configuration file.

I tweaked the url_redirect to
<META HTTP-EQUIV="REFRESH" CONTENT="0; URL=http://my_other_domain.com/opt/other_wordpress">
Now I see this error
The requested URL /opt/agtwdpr/ was not found on this server.
I've tried various versions of this, but I'm not clued-up enough to figure out the correct syntax.

I think you are slightly mistaken here. In principle there has to be no relation between the location in the local file tree on the server and the location that is used when accessing through the webserver.

If you have done everything properly you have modified the configuration file of the webserver (or preferrably it's templates) and configured the filesystem location (/opt/wordpress in your case) to be available at a certain location on your webserver (for instance before mentioned /blog1). If you have done so you would only need to redirect to http://my_other_domain.com/blog1/ and this location should also be accessible without redirecting but by directly accessing this url in you webbrowser.

[bloodshoteye]

If you have done everything properly...

Evidently I haven't - I can't access the site directly using http://servername/other_wordpress
It still returns a 404 error
(Remember this is a second instance of wordpress in opt - the redirect from Primary to the 1st instance works without errors other than permalink errors)

What I've done so far:

If you have done everything properly...

Evidently I haven't - I can't access the site directly using http://servername/other_wordpress
It still returns a 404 error
(Remember this is a second instance of wordpress in opt - the redirect from Primary to the 1st instance works without errors other than permalink errors)

If you have done everything properly...

Evidently I haven't - I can't access the site directly using http://servername/other_wordpress
It still returns a 404 error
(Remember this is a second instance of wordpress in opt - the redirect from Primary to the 1st instance works without errors other than permalink errors)

What I've done so far:
Untar worpress into a dir in /opt
Add the db details to wp-config.php
Try the redirect mentioned above
That's all - I was wondering if I don't also need an alias - if so, how?
What I've done so far:
Untar worpress into a dir in /opt
Add the db details to wp-config.php
Try the redirect mentioned above
That's all - I was wondering if I don't also need an alias - if so, how?
Untar worpress into a dir in /opt
Add the db details to wp-config.php
Try the redirect mentioned above
That's all - I was wondering if I don't also need an alias - if so, how?

[cactus]

Evidently I haven't - I can't access the site directly using http://servername/other_wordpress
It still returns a 404 error
(Remember this is a second instance of wordpress in opt - the redirect from Primary to the 1st instance works without errors other than permalink errors)

What I've done so far:Evidently I haven't - I can't access the site directly using http://servername/other_wordpress
It still returns a 404 error

Add the db details to wp-config.php
Try the redirect mentioned above
That's all - I was wondering if I don't also need an alias - if so, how?

I will refrain from typing everything triple fold to keep it more readable

If you installed wordpress from a rpm using yum the alias is already created, you probably need to clone that template fragment to also configure your other blog alias.

[bloodshoteye]

Oops, something haywire with my previous post    Excuse the duplications, please
- think I know what I did, but too embarrassed to tell.

If you installed wordpress from a rpm using yum the alias is already created,
you probably need to clone that template fragment to also configure your other blog alias.

Excellent suggestion - I'll give it a try real soon