i have the same issue , we updated Magento from 2.2.3 to 2.2.6. then the error started, we changed the PHP to 7 from 7.1 but we still have the same issue.
my frustration is that the hosting company for 2 weeks not sure about the issue.
is it wise to keep Magento 2.2.6 or downgrade?
is it safe to work on the development site while we trying to solve the issue?
is it wise to download the site on a local server and work on it then upload to the live site when issue resolved?
Thanks all
Hello @alaa_hussain,
Please run below command in magento root directory
For static content deploy
php bin/magento cache:clean php bin/magento cache:flush php bin/magento setup:upgrade rm -rf pub/static/frontend/* pub/static/adminhtml/* var/cache/ var/generation/ var/page_cache/ var/view_preprocessed/ var/composer_home generated/ php -dmemory_limit=6G bin/magento setup:static-content:deploy -f chmod -Rf 777 pub/ var/ php bin/magento cache:clean
For permission
find . -type f -exec chmod 644 {} \; find . -type d -exec chmod 755 {} \; find ./var -type d -exec chmod 777 {} \; find ./pub/media -type d -exec chmod 777 {} \; find ./pub/static -type d -exec chmod 777 {} \; chmod 777 ./app/etc chmod 644 ./app/etc/*.xml
If you still got an issue then check server error log and share with us.
--
If my answer is useful, please Accept as Solution & give Kudos
Thanks a lot guys, as I'm not a developer myself, but as a project owner, not a developer, please advise, if it's ok to carry on the development on the site while we have the issue, and would changing the hosting company will solve the issue.
Thanks all