I recently activated the varnish cache module for my Magento store, this worked pretty well, no problems. Now I copied the code and the DB of this Magento installation and placed it somewhere else on the same server to create a testing environment. I deactivated varnish cache on that testing environment by setting system/varnishcache/enabled to 0 and system/varnishcache/disable_caching to 1.
The problem now is, that I always get:
Error 500 Internal Server Error
Internal Server Error
Guru Meditation:
XID: 628339795
No matter what I do, I cleared the cache, reloaded, tried different browsers, activated the varnish cache module, doesnt help. Any ideas what else I could try?
Thanks!
By default Mageto switches errors output off. If your php is configured not to log php errors web server will send 500 error in case any fatal error occurs.
You can check errors in /var/log/exception.log and /var/log/system.log or enable output of all errors in your magento installation:
edit your index.php :
error_reporting(E_ALL | E_STRICT);
ini_set('display_errors', 1);
and .htaccess:
SetEnv MAGE_IS_DEVELOPER_MODE "true"
Related
I have to refresh an old webapp and i'm facing a problem i can't find...
Old situation :
webapp (Java6, wicket) on Weblogic 10.3, external access via URL rewrite by IIS
everything OK
New situation :
refreshed webapp on WL 12.2, IIS unchanged.
Results : Inside URLs : everything OK
Outside URLs : HTTP 200 OK, but all pages HTTP 302 (redirections) fails
browser receive 503 (unavailable) after a while.
I looked at the logs :
WL12 : process OK, response 302 found, location:inside URL
IIS : found code 400
I looked at [Oracle docs][1], i saw that they added CSRF protection, i believed it could be that, i disabled it, but nothing changed.
Any idea ?
Thanks in advance.
[1]: https://docs.oracle.com/middleware/12213/wls/WBAPP/weblogic_xml.htm#WBAPP-GUID-E3A9B2FC-E098-43B1-ACFF-4A457D6062DE search for "referer-validation"
Forget that.
The WL12 was installed on an "end of life" server running HP Unix.
I deployed the same app on WL12 on redhat, it worked as intended.
HELP! - I am trying to take a PayPal Payments Pro (Magento 1.8.1) API live and I am getting the following error:
exception 'Exception' with message 'PayPal NVP CURL connection error #35:
error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure'
in <my_root_folders>/app/code/core/Mage/Paypal/Model/Api/Nvp.php:986
In the payment_paypal_direct.log file I have the following for every error:
2014-11-08T02:12:36+00:00 DEBUG (7): Array
(
[url] => https://api-3t.sandbox.paypal.com/nvp
[DoDirectPayment] => Array
(
No matter how I set the various flags for sandbox mode, my errors all show the sandbox URL for the API. I have even double checked the paypal/wpp/sandbox_flag in the core_config table in the db and it is flipping from 0 to 1 when I change the configuration in Magento's admin.
Has anyone experienced this persistent sandbox URL?
Sandbox Mode = OFF
SSL Verification = Disabled (have tried it enabled too, no difference)
all caching is disabled (I clear cache often just in case)
I reindex entire site frequently
There were two issues effecting my website:
Our server was not configured in response to the POODLE vulnerability and PayPal was rejecting the server connection.
Sandbox setting was enabled for a child "Configuration Scope" and edits made to the "Default Config" (the parent/master config) were being overridden.
Hopefully this may help someone.
In addition to the above answer you may configure your server and disable SSLv3 by editing you Apache's httpd.conf and adding the following code:
SSLHonorCipherOrder On
SSLProtocol -All +TLSv1
You may also do this via WHM if you have a VPS or Dedicated Server:
Go to Service Configuration -> Apache Configuration -> Include Editor -> Pre Main Include
and add the above two lines.
I just upgraded magento 1.7 to 1.8, it has database size around 3GBs.
Problem is that, Admin dashboard is does not display the content below the header part (But, website is working).
I am not able to reach the configuration settings as solution provided in the link below.
Similar Problem
I traced few PHP error logs,
2013/12/29 00:03:39 [error] 1822#0: *642 FastCGI sent in stderr: "PHP message: PHP
Fatal error: Undefined class constant 'XML_PATH_TAX_NOTIFICATION_URL' in
/var/www/magento/www/app/code/core/Mage/Tax/Block/Adminhtml/Notifications.php on line 174"
while reading response header from upstream, client: 14.98.44.206, server: something.compute-1.amazonaws.com, request: "GET /index.php/admin/dashboard/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "something.compute-1.amazonaws.com", referrer: "http://something.amazonaws.com/index.php/admin/"
I defined that constant in the same class where error is occuring, then it gives another similar error.
Server is a VPS. Nginx Server, configured with php-fpm and mysql.
I will be thankful, if I can get some help.
Taking a look at app/code/core/Mage/Tax/Block/Adminhtml/Notifications.php in a stock Magento 1.8 system, around line 174 (per your error message)
#File: app/code/core/Mage/Tax/Block/Adminhtml/Notifications.php
public function getInfoUrl()
{
return $this->_app->getStore()->getConfig(Mage_Tax_Model_Config::XML_PATH_TAX_NOTIFICATION_URL);
}
It appears PHP is complaining about the use of the Mage_Tax_Model_Config::XML_PATH_TAX_NOTIFICATION_URL constant. Taking a look at that class definition (Again, in a Magento 1.8 system)
#File: app/code/core/Mage/Tax/Model/Config.php
class Mage_Tax_Model_Config
{
//...
const XML_PATH_TAX_NOTIFICATION_URL = 'tax/notification/url';
//...
}
The class constant XML_PATH_TAX_NOTIFICATION_URL is defined.
This leads me to believe your system isn't really updated to Magento 1.8. You either have files that were not correctly deployed, or you're running with a system that has APC (or some other class cache) installed. Get the right files on your system and/or get your APC cache cleared and you should be good to go.
Ok, I found out the reason why app/code/core/Mage/Tax/Model/Config.php did not get loaded,
There was also a file in app/code/local/Mage/Tax/Model/Config.php (mind the local vs. core difference in the filepath). This file did not get updated and overruled the core file.
when i am trying to install Zopim live chat megento extension, i am receiving "Exception during cache and session cleaning". but installed successfully. After installtion with this above error, i tried to open site, its shows "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." 503 error. Please help me how to resolve this problem.
Thanks
Bala
The error you're seeing means Magento is displaying its default HTTP ERROR 503 page. This could be happening for a number of reasons, but most likely it's because the install process (you didn't mention if it was Magento Connect standard, or if it was something else custom) left the maintenance.flag file in the site root. Remove this file from the root of your site, and things should be back to normal.
$ cd /path/to/magento/root
$ rm maintenance.flag
Prototype.js is missing in the Iframe header of the "console".
Just edit /downloader/Maged/Connect.php and find
var response = transport.responseJSON || transport.responseText.JSONeval(true) || {};
replace it with
var response = transport.responseJSON || JSON.parse(transport.responseText) || {};
:-)
Ok, this is not a rewrite error because I did not touch the conf file.
I used http://www.farinspace.com/install-and-configure-nginx-server/ to make the web server.
The thing is CodeIgniter & Kohana does work on http://url.com/sub/ and http://url.com/sub/index.php
But, it does not work with http://url.com/sub/index.php/welcome or any controller (am I calling that right?), I get a 404 Not found.
am I calling that right?
Obviously not. 404 error in kohana / codeigniter means that no matching controller / action could be found. Additionally 404 error by the server means that the overall resource was not found.
Nginx requires a different server configuration than apache. RewriteRule is only one example.