This might be something easy, but it drives me crazy right now.
Joomla 1.5.26 -> site was running until this morning. Now I get an Internal Server Error 500 for the frontpage(html source shows nothing), backend(admin panel) works just fine.
A single editor has worked on some articles, nothing suspicious to me there.
What I have tried so far:
Unpublished all recently created articles
Unpublished modules with dynamic content (calendar, news feeds, recent photos)
reset .htaccess to the original state
reset permissions (all directories 775, all files 644)
enabled all PHP error reporting in configuration.php ( ini_set( 'display_errors', true ); error_reporting( E_ALL ); ) - no error, just a few warinings "PHP Deprecated: Function split()", but I can even get rid of those warings by unpublishing one plugin, after which page is still blank
backend still works
index.php exists and contains the original code, template exists and is assigned
database works, no waiting processes
deleted cache in browser as well as the Joomla cache in the backend
As I have only FTP access to the server, I cannot access any apache logfiles, except the PHP error log. What other options are there to track down such an issue? My hosting company tells me the webserver is working fine, they also told me that they have restarted the server with no changes in site behaviour.
This usually happens when your host upgrades PHP and/or MySQL on the server hosting your website.
Check this post: http://www.itoctopus.com/are-you-suddenly-seeing-an-error-on-every-page-of-your-joomla-website . Your problem is most likely 2.2 (point #2, subpoint #2).
I'm pretty sure that the Apache error logs will reveal something.
Related
I am currently unable to get into my WP Dashboard. The wp-admin page is completely blank throwing no visible errors. I can hit wp-login.php, use my login credentials and hit Log In and then again just blank page, still not logged in. The site it self works fine.
I did enable wp_debug and this still is not showing any errors.
I just took over this site so I do not know of any recent updates or changes made to themes,plugins etc.
UPDATE: I was able to get wp-admin page to load the wp-login page properly by just uploading a clean version of wp-admin/index.php. However I am still seeing a blank page and unable to login after hitting 'log in'
I check the error logs for the server and I do not see anything related to this site.
Make sure that u don't have blank spaces in config and functions file at the top or bottom of theses.
btw, it seems like server's error. See his log :)
Sounds like a PHP error.
Add:
error_reporting(E_ALL);
ini_set('display_errors', '1');
To the top of wp-admin/index.php
A common troubleshooting technique would be to rename your
./wp-content/plugins
folder. This will temporarily deactivate all your plugins. Often such issues are caused by a malfunctioning plugin, usually after an automated update.
Another thing you can try is to switch the php version of your hosting account. Most hosting companies run CloudLinux and you have in cPanel -> Select PHP Version. You can test the administrator login with different versions.
You can also contact your webhosting provider and have them check if the ConfigServer eXploit Scanner (cxs), often installed on shared servers hasn't quarantined any of your website files.
It might be a long shot, but it is also worth checking your .htaccess file.
Good luck!
It may be caused from an error in your theme functions file. If you have a theme backup (which you are sure worked before), try restoring it from the file manager in your host panel. If you don't, try uploading a popular wordpress theme (e.g. twenty-sixteen) then change your default theme from PhpMyAdmin.
Go to your root folder, open wp-config.php,...
Enable Debug mode.(i.e)
define('WP_DEBUG', false);
to
define('WP_DEBUG', true);
And inspect it using Firebug.
I've set up a Drupal 7 site locally and have ftp'd the site over to my ISP's server which is a linux box running PHP and MySQL.
I've never successfully logged into the site before and I have locked myself out. When I go http://www.example.com/?q=user and click on request New Password then I get this error:
Not Found
The requested URL /user/password was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
One thing I've been confused about and that is the .htaccess file. I never had one locally on my Mac and I did not need it (I know it is hidden) - so I downloaded one and deployed it to the web site but then I got 500 errors, it made it worse. I've since deleted that file and at least I get some content - but not very much - just the front page. I overrode the themes name in settings.php as I have user access errors there. I changed it back to one of the default themes and that allowed me to get some content and not the 'white screen of death'
Advice welcome!
I've set up a new server for my magentocommerce.
Unfortunatly when I moved the domain to the new location (tests have been done using another domain) a weird issue started happening: when the login page displays on the frontend, or the backend and I (and customers, of course) do submit the right credentials the page refresh, the cookie gets set but the form is displayed again. It's such a cache being served instead of the right content (catalog).
The only solution actually is delete the cache on the browser and retry.
I've used varnish http accelerator for two days, but since I've had too much issues dealing with it I uninstalled it and cleaned things up (now there's only the apache instance to serve user requests).
I also installed APC caching and Fooman Speedster.
What can it be to cause this issue?
Can you please help me to get in the right direction to fix this issue? On the old server it was not happening, but since that time there have been some modification to the store (nothing to do with authentication anyway).
The apache error log does not report anything, the only thing in there is PHP: syntax error, unexpected BOOL_TRUE in /etc/php5/apache2/conf.d/apc.ini on line 4 which has to do with the line apc.enabled = 1.
Look at the System -> Configuration -> Web tab in the admin panel and see if the Cookie Path and Cookie Domain are set correctly for the new server. You can do it directly in the database as well. In this case, search for rows with web/cookie/cookie_path and web/cookie/cookie_domain paths. Setting them to empty values in the admin panel or NULL in the database may also help.
You should also clear Magento cache (System -> Cache Management) and APC cache (here's how to do it: How to clear APC cache entries?).
I don't know if it solves your specific form problem but we had the same error in the apache error log.
Our failure was, we've copied the apc.ini code from http://magebase.com/magento-tutorials/speeding-up-magento-with-apc-or-memcached/. They use "#" for comments.
Turns out we had to use ";" for comments. After these changes, there were no more errors in the apache error log.
I updated my joomla site to 2.5 from joomla 1.7 I faced below errors:
1- I cannot open global configuration page from the admin area and receive "500 internal server error"
2- When I press the add new article button from the admin area I receive the same error.
3- When I press the add new category button from the admin area I receive the same error.
appreciate if you can help to solve this.
I had the same issue and was about to go crazy (even considered switching to another CMS) ... the problem appears to be related to the fact that Joomla 2.5 is throwing several errors and the PHP engine was trying to write to the php_errors.log file in a directory where it didn't have write permissions, thus the 500 error (misleading I know).
Incidentally, this happened to me on a Windows box running IIS 7.5, not Apache. The solution, intiailly was to edit my PHP.INI file and change the "error_log" setting to point to a folder which had write permissions for all websites. I just created a new folder and gave the 'users' group modify permissions - not the best way to do it but for development purposes, it was ok.
You then have to restart IIS.
It is important that you actually restart IIS, not just restart the application pool, as this didnt seem to force PHP to re-read the config.
Once I got this far, I started noticing errors (which I will continue to post here among other places until I can find a solution). So far, the first error I see is when I go to add a New Menu Item, i get this:
Warning: is_file(): open_basedir restriction in effect. File(\metadata.xml) is not within the allowed path(s): (C:\Inetpub\vhosts\myWebsite.com\httpdocs\) in C:\Inetpub\vhosts\myWebsite.com\httpdocs\libraries\joomla\filesystem\file.php on line 523
It appears that Joomla is trying to verify if the \metadata.xml file exists, however I'm not sure where that file is or what it does. At this point, i suspect it's still ultimately a permissions problem, but I'm still digging...
The most common cause of 500 error that I've seen on Joomla! websites is related to the permissions of the files on the website. eg. yesterday we had to fix a website for a company that had upgraded and in the process somehow set the Group write permission on their /administrator directory.
You can check this quickly through the file manager of your hosting service, if using CPanel you should make sure your directories are set to 755 (User has read/write/execute permissions, Group and World have read permission) and files set to 644 (User has read & write permissions, Group and World have read permission).
These sound like the same issue.
See this rundown of potential upgrade problems by Brian Teeman:
http://brian.teeman.net/joomla-1.7/upgrading-to-joomla-2.5-some-warnings.html
The problem you are having could be related to the database issue he mentions.
I'm trying to use Dreamweaver with an existing code base (not WP, Drupal, or Joomla!) in a PHP/MySQL site. I continue to receive "Dynamically related files could not be found because of an internal server error." I've been googling all day and have read plenty of WP-specific solutions, including the thread on this site. I've tried all the methods listed, no luck.
Setup Info
MAMP 2.0.1
Mac OS X 10.6.8
Dreamweaver CS 5.5
Site's local address: /Users/myName/Sites/siteName
Testing server address: /Applications/MAMP/htdocs/siteName
Attempted solutions:
1) added library to site root (/Users/myName/Sites/siteName/library)
2) added library to MAMP root (/Applications/MAMP/library)
3) added include path for both locations to applied php.ini listed in phpinfo
4) set Dreamweaver to use Site Root paths instead of page-relative paths
5) switched back to page relative paths
6) Restart MAMP, reset ports in Preferences to 8888/8889, or 80/3306
7) checked site info to make sure paths are correctly defined
When I insert the following code, or any require function with a relative path, live view and preview in browser display empty pages.
<?php require_once('includes/initialize.php'); ?>
I'm incredibly frustrated. I had been using XAMPP and a plain text editor for previous work and never had an issue with relative paths. Any help would be appreciated.
Answering my own question; bad form, I'm aware.
EDIT:
Adding to previous list of attempted solutions:
8) tried designating the server ports as 8888/8889 and defining server route as http://localhost:8889/mySite/, like setting up a Drupal/WP/Joomla! testing environment.
9) Uninstalled/Reinstalled MAMP, Dreamweaver, disabled the out-of-the-box Apache server included with OS X, the redefined the site in Dreamweaver.
Fix attempt 8 led to packet error discussed here. Fix attempt 9, plus error reporting that hadn't been working, but did now:
// Report all PHP errors (see changelog)
error_reporting(E_ALL);
showed that the testing server was using the local definition to refer to dynamically related files and, even though that should work, it wasn't working.
After reinstall, created new site with "Site > Manage Sites" and defined Local Site Folder in "Site" menu and the Server Folder in the "Server" Menu as the same directory. (/Applications/MAMP/htdocs/mySite)
Refer to the Setup info in the OP to see my system variables; this may be specific to any/all settings. But only identical local definition and server definition solved the problem. I've recreated previous settings to be sure, and different local/server definitions don't work.
This error can happen with Dreamweaver and PHP sites if the contents of the included file make additional dynamic calls using PHP syntax that Dreamweaver doesn't recognize. Without seeing the contents of initialize.php, I can't be 100% sure this is the case but I am pretty sure that DW is not able to parse the code there and figure out what files to get for display.
Problem Dynamically related files that I see a lot of people run into:
Dreamweaver is scanning whatever is in you Local Copy, it should be a the full installation of WordPress. If you're working locally, download everything on your "Testing server" to your "Local view" in the Files panel.
If you're working with two sets of files, your local copy and what is in MAMP's htdocs or on your "Testing server" should be nearly identical, except for what you're working on of coarse. That's the problem I see people have.
If you're working in kind of "pho-FTP" environment.