apache config needs some help

i tried searching the forums but i had no idea what to search for

For nothing. This is not a general how-to forum or an apache support forum.

Server setup issues should be asked in specialized forums.

ok well im not sure if it is apache or some setting in wordpress that i have missed.

apache tells me to ask you guys so does fedora forums and now im going in a big circle.

im so lost at why this does not want to work…

Ok so as of right now my wordpress dash board says that my wordpress address is //192.168.0.225/wordpress. My blog address is set to the same thing.

What happens if you change your address to just //192.168.0.225 ?

Your login would look like this //192.168.0.225/wp-admin

p.s. be prepared for complete and total failure just in case.

…just kidding! But make sure you know how to change it back from the database just in case.

ok i popsted in a differnet apache forum. now maybe they can help me out. But as far as you can tell the wordpress site and blog url of https://192.168.0.225/wordpress is correct.

that way works on the server let me check the other machines, BUT the login button does not work.

ok im so lost now.

last time i tried that my theme disappeared and everything went to heck. but now it works. im sooooo lost.

thanx

hopefully it stays this way

Ok i changed the IP to my public IP and its all locked up. Am i supposed to change the wordpress and blog url to my public IP?

thanx

My logic could be flawed here, but looking at your default sites enabled config, it says that your default, enabled web site, is now serving your blog’s content from /var/www/wordpress. I don’t think there is anything wrong with your config file. I think it is the Blog and WordPress url that you are using. (You did do a restart of the service after changing the config file? I think debian is either
/etc/init.d/apache2 restart or sudo apache2 -k stop, start or restart , I can’t recall which is preferred.)

I think what this means, is that when you type 192.168.0.225 in your browser,(preferably not from your server’s browser) you land in /var/www/wordpress by default. If you installed your blog files at /var/www/wordpress, then trying to access your login from /192.168.0.225/wordpress/wp-admin, would imply a file path that looks like this: /var/www/wordpress/wordpress/wp-admin. And that does not exist. At least that is what I think I see.

Probably a Ubuntu server, using only a slightly modified default sites enabled file, now serving one site’s documents from the directory named “wordpress” in the /var/www/ path. In fact the only thing that appears to be changed in the default config are these three items;

ServerAdmin my email address
DocumentRoot /var/www/wordpress
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/wordpress>

So I stand by my previous suggestion, until someone tells me why it may be incorrect, or it just plain doesn’t work. Or am I missing something really obvious?

To the above statement. I finally got it to work internally via LAN. i can go to any web browser and type 192.168.0.225 and it will take me to the /var/www/wordpress folder. if i clik on login it will infact take me right to the wp-admin.php page. everything works flawlessly LAN side. However, public side it does not work. I have my domain name syncrasy.blogsite.org pointing to 66.60.115.51. My router(66.60.115.51) has a tcp port forward for any incomming traffic on port 80 go to 192.168.0.225. the default GW for my server is my router. traceroute even shows that the first hop is my routers LAN ip.

i change the wordpress and blog url in the dashboard to : https://syncrasy.blogsite.org

BUT when i hit the save button i get a the requested URL https://syncrasy.blogsite.org/wp-login.php could not be retrieved.

if i try 192.168.0.225, i notice at the bottom of the browser it says waiting for syncrasy.blogsite.org. why it is NATing my private is beyond me

what is the wp-login file vs the wp-admin?

thanx

“I finally got it to work internally via LAN.”

Could you share the solution? If this is a linux distro-specific symptom I could use the info on how to fix it if it ever comes up again.

I’m just ball-parking here, and you have probably already done this, but have you tried adding your domain information to your default virtual host configuration for ServerName and ServerAlias directives yet? (restart apache2 after any config changes)

ServerAdmin “[email protected]”
DocumentRoot /var/www/wordpress
ServerName “www.yourdomain.com”
ServerAlias yourdomain.com

(I think you probably are now dealing with apache issues).

No quotation marks of course.

Just a guess, I know these config files are pretty touchy about forward slashes. When for example setting your DocumentRoot, the following two lines are not the same thing

DocumentRoot /var/www/wordpress
DocumentRoot /var/www/wordpress/

Just an idea, I was dealing with similar issues when I turned off FollowSymLinks in one of my directory. Everything was working fine with FollowSymLinks and when I turned it off, everything suddenly went to blank. Just guessing. See here for FollowSymLinks if you like: FollowSymLinks