Please check the php error log files and copy paste the errors in pastebin and give us the link. There is only problem with php, Apache2 or whatever server software is running, is running properly :
http://www.ppsllc-us.com/license.txt
http://www.ppsllc-us.com/readme.html
Please check the php error log files and copy paste the errors in pastebin and give us the link. There is only problem with php, Apache2 or whatever server software is running, is running properly :
http://www.ppsllc-us.com/license.txt
http://www.ppsllc-us.com/readme.html
Edit: Make sure that PHP is running. Please check my previous post for a download link to a script – http://wordpress.org/support/topic/moved-to-new-vps-and-now-wordpress-site-doesnt-work?replies=15#post-3199455
Create a sub directory / sub folder on the root (so that we can visit http://www.ppsllc-us.com/bar/foo.php).
Thread Starter
jsnair
(@jsnair)
Im extremely new to this. How do i get to the phpError log Files and how do i put it in a pastebin?
Is this right?
Added a folder to the /public_html – is that the root?
bar/foo.php
Thread Starter
jsnair
(@jsnair)
Thread Starter
jsnair
(@jsnair)
I need more help— i dont think i am doing this right.
Is this right?
Added a folder to the /public_html – is that the root?
bar/foo.php
Yes that it is. You can see, it is giving error :
http://www.ppsllc-us.com/bar/foo.php
It is probably not WordPress specific. You can rename the .htaccess to bak.htaccess and reload http://www.ppsllc-us.com/bar/foo.php ; if still it gives error, you need to contact your web hosting company’s support. They might be upgrading some server software.
Regarding PHP error log file, its location and existence depends on server OS, setup etc.
Added a folder to the /public_html – is that the root?
Yes, public_html is your web root.
The most logical would be to check whether PHP is running or not from Command Line Interface. That however will need root access.
Thread Starter
jsnair
(@jsnair)
Ok changed htaccess to bak.htaccess and i get the same error.
Can I grant root access? or can I check it?
I get the same error on every page i try to load…
Ok changed htaccess to bak.htaccess and i get the same error.
This is server side problem, you must contact your web host.
Can I grant root access? or can I check it?
If you have virtual dedicated server (vps) or dedicated server; you will get root access. We use any SSH client (PuTTY for Windows) to connect and use the command line interface.
In any case, if you are using a managed web hosting account or a shared server, it is not your work to fix, web hosting company will fix after you report or ask. In case of unmanaged, you have to do it yourself to fix. For 500 IS error, these might help you :
https://my.bluehost.com/cgi/help/594
http://support.hostgator.com/articles/cpanel/internal-server-error-help-500-error
http://thecustomizewindows.com/2011/10/500-internal-server-error-wordpress-how-to-fix-500-error/
http://www.cyberciti.biz/tips/http-error-500-internal-server-for-php-pages-and-solution.html
http://forums.cpanel.net/f5/500-internal-server-error-php-file-150233.html
I am taking you are using a Linux-Apache-MySQL-PHP (LAMP) server with cPanel. For LAMP 500 server error comes exclusively with single standalone PHP file happens mainly due to :
Error in .htaccess file
Misconfigaration in php.ini file
Problem with permission
With cPanel or any web hosting panel with substandard host or cost saving shared hosting packages, it is common to get 500 server errors, If you search in Google, you will lot of people are complaining, because they can not probably employ good 24×7 UNIX experts at that cost.
You yourself did everything rightly when you arrived here, we have made you understand the facts :
text files, html files are loading quite nicely. So Apache2 is running.
We asked you to test with that foo.php inside a subfolder disabling .htaccess. Your .htaccess is not responsible for 500 error.
Other points mentioned in the above linked webpages. But you must inform your web host (if applicable).
Thread Starter
jsnair
(@jsnair)
I am using GreenGeeks as a host. So I guess my next step is to talk to them? Its been over a week with this problem. I cant imagine its an upgrade.
I am using GreenGeeks as a host. So I guess my next step is to talk to them? Its been over a week with this problem. I cant imagine its an upgrade.
Definitely.
I can not imagine the site is not actually working for one week. If they do not respond, move to any standard web host.
For any web host, if there is definite server problem or the server is down more than 5 minutes, always let the webhost know in case of managed VPS and shared. For unmanaged VPS (for example your situation) you have to do the server side works, but for these things usually all standard host helps despite being unmanaged.
This problem looks very familiar… so I’ll add to this thread rather than start a new one.
Same issue – 500 internal server error. LAMP installation. I have physical and root access to the server.
Same server is running a BuddyPress site on a different domain. It is working properly.
I can get the wordpress/license.txt file to display on the broken site. If I try the index.php I can see the hard drive light illuminate essentially until the browser times out. Top shows apache using all the cpu cycles when this happens. I can access a phpBB3 installation on the broken site without any issues.
I checked the database with mysqlcheck and noted no errors.
Plenty of drive space.
I can’t find a php error log anywhere…
Site is http://www.nanson.org (www.nanson.org/wordpress)
Any suggestions of what to check next??
Hmm…. disabled the plugin called ‘better-wp-security’ by renaming its directory since it’s got plenty of features that could break a site… a hail-Mary attempt to fix things… and the site works again.
However, I haven’t had an upgrade offered for that plug-in for a while and haven’t made any configuration changes…. so not sure why things have suddenly broken…
For that matter, I don’t think I did any updates before the site broke. Is there a way to see a history of plug-in updates etc.? Something is screwy…
The BuddyPress site that has worked throughout this issue also has better-wp-security installed and running, along with essentially the same group of plug-ins… which also makes me want to dig deeper.
I understood you fixed it, I saw it is working.
You can check the date of modification of the files in FTP – that will give you more file specific date of modification.
FTP is probably not required in your case if you have a GUI installed for the server OS.
It is not a good sign if a file is modified ‘automatically’ or public pages suddenly started throwing 500 error. I want to point you – for your setup, make the security from networking level very strong.
You need to make sure that no one can do unauthorized SSH tunneling. ISP is always a vulnerable point.
I agree, the fact that this site broke without any apparent cause is a big concern. I’m quite concious of security and run behind a hardware firewall. Only the essential services are turned on and since the server sits beside my desk, I can admin it directly.
It seems very odd that Better-WP-Security is suddenly a problem for me! The only thing I can see that was upgraded recently is JetPack. But I’m 95% sure I saw the site working properly after the JetPack upgrade… so not convinced that’s the actual problem!
I also think it’s odd that the BuddyPress site running on the same server also runs Better-WP-Security and JetPack… and is running just fine.
I’ve been through the logs looking for a clue, but so far nothing. And with Better-WP-Security running all the time, I am more confident that things should be better protected than without it.
I’m really not sure what to think of this…
I later view your profile plus from page loading speed, I understood that your setup is quite good.
500 error out of Better-WP-Security was a problem but it has definitely done a good thing, you have been aware of the fact that some effort can be running behind.
I searched in forum whether anyone has reported 500 error with Better-WP-Security. Result points there is something else for you, because their problem was simple, out of .htaccess or improper file permission. Your previously written observation does has value – “hard drive light illuminate essentially until the browser times out. Top shows apache using all the cpu cycles when this happens.“
Use custom 403 (Forbidden) pages :
http://forums.devshed.com/apache-development-15/redirect-403-forbidden-to-a-custom-page-418594.html
It is showing your OS normally. Give more importance to security of Apache :
http://www.kyplex.com/docs/apache-security.html
http://www.linuxsecurity.com/content/view/133913/171/
I think I may have seen the same .htaccess forum post. In the one I read, the file structure in .htaccess was messed up, missing some closing statements… or something like that. That made me check my .htaccess file… but all appears to be fine. AND… since I renamed the Better-WP-Security plug-in directory rather than deactivating or deleting, the .htaccess edits it made are still there. Disabling whatever scripts are in the plug-in gets the site running again, not deleting or editing .htaccess, so I’m not looking there any longer.
My biggest speed issue is the theme I’m running. It’s a release candidate and doesn’t have the fast code in it I’m told. Hopefully that will change, because the theme is great but the performance is sluggish. So there is a big delay before a page is rendered, but once rendering starts I have enough bandwidth to ensure a fast load.
The kyplex link is a good one and I will bookmark it for some later follow-up. You can never be too secure! Thanks again!
