Hot answers tagged

6

Yeah Surely you can do that, just edit the following entries of your magentoroot/app/etc/local.xml file like this: <connection> <host><![CDATA[myinstance.amazonaws.com:3306]]></host> <username><![CDATA[yourDBusername]]></username> <password><![CDATA[yourDBpassword]]></password> <...


6

Magento2 Class Magento\Framework\App\Http\Interceptor does not exist This issue is generate when you have make changes in your construction file and it's Factory class is not update in generated folder For that you need remove generated folder from your magento root rm -rf generated/* After remove generated now compile the site php bin/magento setup:di:...


4

You are comparing dedicated hardware running on bare metal (presumably locally) to shared, highly contended hardware virtualised behind a hypervisor. CPU dictates load time, of which your AWS lottery has served you something 30% slower than your dev. box. Its no surprise a cloud service would be slower, its widely regarded for its poor performance, its ...


4

So after a long and hard look at what might be going wrong my colleague found the problem. There was code added to detect HTTP_X_FORWARDED_PROTO in the magento root index.php which is as following if( isset($_SERVER['HTTP_X_FORWARDED_PROTO']) ) { $_SERVER['HTTPS'] = 'on'; $_SERVER['SERVER_PORT'] = 43; } This code would set https as on which makes ...


3

First of all if you have Flat Category enabled, indexation is going to put your website down. You must create a custom solution for aliasing the tables like described in my Indexation talk at Magento Developers Paradise: https://ivanchepurnyi.github.io/slides/indexation-techiques/index.html Apart from that, it seems like you are using a kind of custom ...


3

I think we got a patch for this exact issue and EE 1.13.0.2. Looking at the code, it appears 1.14.1.0 still has the catalogrule_after_apply observer that calls cleanCache. Should start on line 378 of app/code/core/Enterprise/PageCache/etc/config.xml: <catalogrule_after_apply> <observers> <enterprise_pagecache> <...


3

For #2, Magento creates a session for each visitor; to get an estimate of how much space you need, just multiply the size of one session storage by the highest number of visitors (and multiply by.. let's say 4-5 or maybe even 10, to be safe :D). You can also setup alters in AWS, for when you reach like 80% memory usage. Also, you can check if garbage ...


3

There is no way to do this the way you want. I suggest you to check this answer, it seems to be similar and have a couple of methods to try at least.


3

TL;DR NFS for media, Redis for sessions and cache. If you are asking this question, part of me feels like advising you that you shouldn't attempt this endeavour alone. When running a multi server configuration, you have a huge number of things to factor in. Server application configuration management (ie. Chef/Puppet/Ansible), so that all machines in ...


3

Today I encountered the same issue. The issue was missing media folder.


3

You have to check if RDS MySQL has triggers disabled or enabled, because the latest gen of RDS MySQL has triggers disabled and you have to enable these. Also check this post to how to set pervillages and triggers in RDS Web console.


3

This is a very "BIG" topic but I will cover the basics here ASSUMING YOU ALREADY HAVE an AWS account and CodeDeploy setup Here are the basic that we take on a deployment for M2 Here is the appspec.yml file version: 0.0 os: linux hooks: BeforeInstall: - location: config_files/scripts/beforeInstall.bash runas: root AfterInstall: ...


3

You can run this step-by-step to check the possible things. Run this command to get the Magerun2 to made the changes easier. wget https://files.magerun.net/n98-magerun2.phar && chmod +x ./n98-magerun2.phar && alias n98="./n98-magerun2.phar" Run this command to see if there is some additional base URL in your configurations that aren't ...


3

Things you can try: remove the generated code directory (again): rm generated/code -rf upgrade your modules and re-compile: php bin/magento setup:upgrade php bin/magento setup:di:compile if there are any errors during compile, you found the reason for your problem - fix these errors first, and redo all the steps mentioned here. and if you're in ...


2

After using Magento for almost 3 years, and having used a few companies, I would thoroughly recommend Nimbus Hosting: https://www.nimbushosting.co.uk/ They offer the best value for money currently, but the most important thing is that their service is exceptional. Rapid response time on support and they can handle a lot of your setup processes for you. ...


2

besides the ones already mentioned, magemojo is also good. It depends on your budget, below $25 go with siteground, hostgator, or similar, $25+ Nexcess, $60+ Magemojo is good. good place to check also is Magento official hosting partners: http://partners.magento.com/partner_locator/search.aspx?f0=Types+of+Partners&f0v0=Hosting+Partner


2

You need to have - Use Web Server Rewrites - Enabled System -> Config -> Web -> Search Engine Optimization This should be set to yes. You should also choose 1.9.1 and not 1.7


2

You could keep checkout on a separate node that might have better hardware, since rest of the front end part is more or less protected by Varnish and as such so you might just want to treat checkout differently in terms of the hardware you throw at it.


2

php-redis is a c php extension, it will perform better than native php. If php-redis is available Magento will use that for its communications with redis, if not it will fall back to a native php implementation. You don't need to use php-redis but if its installed you might get slightly better performance.


2

We are using Aurora with Magento1 and its working fine for us. No need to change anything in your database for migration just restore your mysqldump. Note that we did'nt have nay myisam table (catalogtextfullsearch etc, using solr). Readreplica do not use typical mysql replication instead they use the common storage as master (writer) so replica lag is ...


2

Apparently there are some memory issues with the later versions of APC (https://stackoverflow.com/questions/9611676/is-apc-compatible-with-php-5-4-or-php-5-5). I don't know if this is actually affecting you as I've not seen this behavior. In whatever event, the best option would be to upgrade to the opcache as Rob stated.


2

Run following query in database INSERT INTO `core_config_data` (`scope`, `scope_id`, `path`, `value`) VALUES ('default', 0, 'dev/static/sign', '0'); or if you have already value for that path, then change it from 1 to 0. Then flush cache and deploy static content as follows. php bin/magento cache:flush php bin/magento setup:static-content:deploy


2

'session' => array ( 'save' => 'redis', 'redis' => array ( 'host' => '127.0.0.1', 'port' => '6379', 'password' => '', 'timeout' => '2.5', 'persistent_identifier' => '', 'database' => '2', 'compression_threshold' => '2048', 'compression_library' => 'gzip', 'log_level' => '1', ...


2

First, you could check the database connection string in your app/etc/local.xml file. You might find it in the xml structure inside config > global > resources > default_setup > connection > host. The hostname might be inside a CDATA structure and look like myrdsinstancename.a098420934.ap-zone.rds.amazonaws.com. Then, check in AWS RDS > ...


2

Magento 2 recommended folder and file permission Please follow following terminal commands for folder and file permission. find . -type f -exec chmod 644 {} \; find . -type d -exec chmod 755 {} \; find var pub/static pub/media generated/ app/etc -type f -exec chmod g+w {} \; find var pub/static pub/media generated/ app/etc -type d -exec chmod g+ws {} \;...


2

I try following way to solve this problem <?php require('aws.phar'); use Aws\S3\S3Client; use Aws\S3\Exception\S3Exception; $config = array( 'version' => '2006-03-01', 'credentials' => [ 'key' => 'XXXXXXXXXXXXXXXXXXXXXXXXXXX', 'secret' => 'XXXXXXXXXXXXXXXXXXXXXXXXXXX', ], 'region' => 'ap-south-1', // ...


1

when using a CDN, the CDN’s cached copy of your site would need to be purged and updated after making changes. Having your development team set up cache management in the .htaccess would give you options to somewhat control how quickly client’s will see updated versions of your site. Check out this link https://webmasters.stackexchange.com/questions/41060/...


1

After some research it seems that converting those tables using engine "MEMORY" to engine "InnoDB" might work. Although this is not supported, and there seems to be no "official answer", all known facts seem to favour the approach: Some Magento tables are not InnoDB, is it safe to convert all tables to InnoDB? Similar problems on stackexchange have no ...


1

Magento is creating 700 + connections leading to database breakdown whenever cache is flushed or indexing is triggered. Production site remain down for 20 mins till all connections clear. Cache aspect That's "normal" behavior depending on your current traffic. That's why you should not flush entire cache every time you make a simple change on the website. ...


1

If you haven't come across this yet, it should be of use: https://aws.amazon.com/blogs/aws/new-aws-quick-start-magento-for-e-commerce/


Only top voted, non community-wiki answers of a minimum length are eligible