I am trying to deploy the static assets using the command:
php bin/magento setup:static-content:deploy
Also removed the var folder.
after that if I load the site in browser, the css, js files from source are not loaded.
for example the link in the source looks like this:
http://www.example.com/pub/static/version1503771754/_cache/merged/f02fb718e9807603b4bf524157f9fd9b.min.css
when I check the file physical location:
http://www.example.com/pub/static/_cache/merged/f02fb718e9807603b4bf524157f9fd9b.min.css
the file is very much there.
so the signing of the file is making it unreachable.
But If I disable the signing I am getting a 500 internal server error on backend.
any help will be much appreciated.
Problem resolved.
if anyone faces the same problem.
The file .htaccess was not correct. I downloaded the latest and correct version the file and put it in pub/static/ folder and run the command again also removed the var folder all caches.
This resolved the problem.
Related
I have seen this answer in many posts but they have not helped me at all. I followed the regular steps to create the laravel project like this:
I cloned from my repository.
I ran composer update.
I added 777 permissions to storage and bootstrap folders.
I have a .env file.
I verfied the .htacces and it's ok.
It is working in locahost, but when I try to replicate it in Hostinger it does not work, it displays the 500 server error. So I wonder what is the problem?
I checked the logs by the way and they were empty. I put the laravel project debugger to true too.
the website url is xellin.com
The debug:
The logs folder:
Thanks.
I think this is a good opportunity to point out how PHP / Laravel / Underlying Server interacts one to each other.
First:
The HTTP server inspects Document Root and .htaccess to get instructions.
If the file is .php (like Laravel), then it CALLS to the php handler.
The php handler could be a FPM version or a Fast CGI version.
-> If an error ocurrs parsing the .htaccess or with the initial interaction between Http Server and PHP... Laravel never runs for real. All ends in a PHP error log
To find out what's wrong, you need to inspect what PHP / Http Server said about the error in their respective logs.
In short words: at this point is not a Laravel error, but a server/php one.
Second:
If Apache/PHP runs well, then PHP executes the Laravel Applicacion Lifecycle... if Laravel encounters a problem, then you will see the usual output error of Laravel Error Handler.
I think this is a must to know to work with web apps in general, because many times developers miss to catch if the problem was with Laravel, or with PHP / Server itself.
As a side note, that's why it is important to know how to choose propper hosting service for Laravel.
Thanks for reading.
You can try to clear cache
Like as
php artisan optimize
Or
You can manually delete cache files which is located in bootstrap folder and inside bootstrap folder you can see cache folder inside cache folder delete all files except git ignore file your issue fix
If you show again this error on live serve then tou can update your composer and then run
php artisan optimize
at first, if you give any of your folders 777 permissions, you are allowing ANYONE to read, write and execute any file in that directory.... what this means is you have given ANYONE (any hacker or malicious person in the entire world) permission to upload ANY file, virus or any other file, and THEN execute that file...so please be careful because IF YOU ARE SETTING YOUR FOLDER PERMISSIONS TO 777 YOU HAVE OPENED YOUR SERVER TO ANYONE THAT CAN FIND THAT DIRECTORY. please read the full explanation from here
the second here is the detailed steps I used to deploy my projects to the server:
run npm run production then update your github repo.
clone the project from GITHUB to server - clone to an outside folder (not public_html folder)
run cd <cloned folder name>
run composer install
run npm install
copy and configure .env file to cloned folder( be sure name is .env not env).
copy all content of cloned_project_folder_name/public to public_html folder
in index.php inside public_html folder edit as below
$app = require_once __DIR__.'/../cloned_project_folder_name/bootstrap/app.php';
require __DIR__.'/../cloned_project_folder_name/vendor/autoload.php';
set your .htaccess properly.
change permission to 755 to index.php and all file in public_html folder
run composer install --optimize-autoloader --no-dev
run php artisan config:cache
run php artisan route:cache
I think I state it all, hope that will help
I am using Magento ver 7. I have changed the server of my website with the same URL.
So, I export the database from old server and Imported the same database to new server. Apart from this I have also uploaded all the files to the new server.
I have also changed the database credentials in the /public_html/app/etc/local.xml file.
But now when I am open the URL, it shows an error that "Not Found, The requested URL /index.php/ was not found on this server."
I don't know why this is happening.
It works for me.
turn off url rewriting from magento admin configuration>web> Search
Engines Optimization > Use Web Server Rewrites > No
RewriteEngine comment this line in In your .htaccess in the root of your installation
I tried many solutions to resolve this issue.
One thing I did was I removed the local.xml file from the app/etc directory and reinstalled Magento. While reinstalling, in the third step I checked the two check boxes. One is skip base url and the other for url rewrites.
Then it worked like charm.
I also got this problem when I was restoring a backup of the magento folder, The problem was that I copied the files with the wrong command:
cp -R /something/folder/* /folder
This command does recursive copying of all folder but ommits the files which start with ".", therefore the files which make a redirection like ".htaccess" where not copied.
Instead use:
cp -R /something/folder /folder
I installed Joomla 3.1.1 Stable on a Centos system.
I can access it, browse through it's admin backend and frontend, but I found in the Extension Manager/Warnings that "The PHP temporary directory is not set"
I went on google and found a fix: I created a php.ini file where I completed this line:
upload_tmp_dir = var/www/html/joomla/tmp
I did that because that is the location where I installed joomla (var/www/html/joomla/)
The fix I found online gave some other location for this folder, it was something with the home/accountname/public_html/... , but I do not have joomla installed in any accounts, it is installed in the "public": var/www/html folder.
I am asking what am I doing wrong because even after doing this, the warning stays the same:
"The PHP temporary directory is not set"
How can I fix this?
I set up the permissions for the entire joomla folder to 40777, and then to the inner folders and files so I would avoid a permission conflict. I then disabled the FTP from Global Settings (before doing this I was receiving a lot more errors when trying to upload anything)
I seriously thought that installing joomla on Centos would not give me so many headaches.
I need to install an extension in joomla (for a template) and I have an error that says nothing to me:"-1 - An error has occurred." - "Copy file failed" so I try to fix any warnings/errors that may cause this before giving up.
The fixes found online about this error (Copy file failed) refer to joomla 1.5 - 1.6. How is it possible that I still get it in version 3.1 ? It is rather absurd.
Any help would be appreciated.
Try to set it via .htaccess file, just add this:
php_value upload_tmp_dir /var/www/html/joomla/tmp
It started working after I changed permissions to ALL subfolders located in var/www/html/joomla
I will reset those permissions after I finish with configuring and customizing the website.
But for now, that was my solution.
-di3sel - the upload_tmp_dir was set up correctly in the php.ini
Thank you both, but my problem seems to be solved now.
I have installed new site in Joomla 1.7 and its working fine, but when i checked its back-end (administrator) got 500 Internal Server Error.
Note: Site is working fine in Local server.
Please suggestion me any solution.
Thanks in advance.
First you have change folder permission to 775 for the following folders:
cache, logs, tmp & administrator/cache
then go to: configuration.php
find code:
$log_path = 'XXXXXXXXXXXXX';
$tmp_path = 'XXXXXXXXXXXXX';
and change code into:
$log_path = './logs';
$tmp_path = './tmp';
problem solved :)
I had this problem, but none of your advices didn't help.
I fixed a problem only after I switched off all modules via PhpMyAdmin (PMA).
Table modules, changed parameter "published" to 0 for all and then enabled only few modules with these types:
mod_login
mod_menu
mod_sumbenu
mod_toolbar
mod_title
After this I entered admin page and used top menu to enable all needed modules one by one. After admin page started to give me 500 error again I knew what module is faulty and I disabled it again via PMA.
May be some files are not uploded.Check failed transfer of your FTP server.Make sure all the files are uploded online
Check your error logs and backtrace what is causing the error. It sounds like you have MySQL errors, make sure any of your components/modules/aren't tricking out your site.
Think it's a component?
You can login into PHPMyAdmin and disable/enable modules manually by unpublishing them using the table editor, changing isPublished to 0 .
Try reinstalling database with the correct compatibility and also check web.config file on ftp for correct configuration paths !
I experienced something similar on my site. Digging through the log file, /administrator/error_log i saw this error message:
[08-Oct-2012 15:28:59] PHP Fatal error: Call to a member function login() on a non-object in /home/XXX/public_html/administrator/components/com_login/admin.login.php on line 65 .
Problem was, i had a previous installation of Joomla 1.5.x, and uploaded files for Joomla 1.6 to replace the previous files and upgrade security of the site. Took me almost a month to find a solution for my own case;
Finally found out from this website that I needed to completely delete all previous files in the website root directory before uploading a new version of Joomla.
Hope this helps someone out there who is in the same situation!
I also have the same issue on my site backend when editing or saving some articles, modules etc...Finally i solved it...
Add these lines to /etc/httpd/conf.d/mod_secuirity.conf on your server
SecRuleEngine Off
save it...and restart apache...it works fine for me.
Adding these lines disable mod_secuirity engine off.I don't know if it causes secuirity problems in future..
Tnx all...
Change the permission of folder administrator at 775 or 755
I tried all the above ideas. Without avail. For my site (which was an outdated Joomla 1.5.x site- don't ask!!!), where the backend suddenly stopped working, the final solution was switching the servers PHP version from 4 to 5.5 (even 5.4 did not work!).
I then got some strange PHP warnings in the frontend. But I then updated Joomla from the now again working backend to the last 1.5 version and everything worked fine from the on.
Phew! Maybe this helps someone later on...
In my case there was a single file with bad permissions.
It can be tricky to figure out which file has the problem so just run this to set the permissions for all the files in the directory:
chmod -R ug+rwX .
chmod -R o+rX .
Change the permissions of all of your files/directories.
Files should be 755
Directories should be 644
This is my case and my solution:
I have changed my server and got this error. I have protected my administrator folder using password protection method. So I have checked my new server and found that my protection information are not saved in control panel. also my .htaccess file (in administrator folder) is not compatible to my new server.
The solution:
Simply protect my folder using control panel
I have renamed the .htaccess file to htaccess.txt
It is done.
I hope it could be useful ;)
I have installed new site in Joomla 1.7 and its working fine, but when i checked its back-end (administrator) got 500 Internal Server Error.
Note: Site is working fine in Local server.
Please suggestion me any solution.
Thanks in advance.
First you have change folder permission to 775 for the following folders:
cache, logs, tmp & administrator/cache
then go to: configuration.php
find code:
$log_path = 'XXXXXXXXXXXXX';
$tmp_path = 'XXXXXXXXXXXXX';
and change code into:
$log_path = './logs';
$tmp_path = './tmp';
problem solved :)
I had this problem, but none of your advices didn't help.
I fixed a problem only after I switched off all modules via PhpMyAdmin (PMA).
Table modules, changed parameter "published" to 0 for all and then enabled only few modules with these types:
mod_login
mod_menu
mod_sumbenu
mod_toolbar
mod_title
After this I entered admin page and used top menu to enable all needed modules one by one. After admin page started to give me 500 error again I knew what module is faulty and I disabled it again via PMA.
May be some files are not uploded.Check failed transfer of your FTP server.Make sure all the files are uploded online
Check your error logs and backtrace what is causing the error. It sounds like you have MySQL errors, make sure any of your components/modules/aren't tricking out your site.
Think it's a component?
You can login into PHPMyAdmin and disable/enable modules manually by unpublishing them using the table editor, changing isPublished to 0 .
Try reinstalling database with the correct compatibility and also check web.config file on ftp for correct configuration paths !
I experienced something similar on my site. Digging through the log file, /administrator/error_log i saw this error message:
[08-Oct-2012 15:28:59] PHP Fatal error: Call to a member function login() on a non-object in /home/XXX/public_html/administrator/components/com_login/admin.login.php on line 65 .
Problem was, i had a previous installation of Joomla 1.5.x, and uploaded files for Joomla 1.6 to replace the previous files and upgrade security of the site. Took me almost a month to find a solution for my own case;
Finally found out from this website that I needed to completely delete all previous files in the website root directory before uploading a new version of Joomla.
Hope this helps someone out there who is in the same situation!
I also have the same issue on my site backend when editing or saving some articles, modules etc...Finally i solved it...
Add these lines to /etc/httpd/conf.d/mod_secuirity.conf on your server
SecRuleEngine Off
save it...and restart apache...it works fine for me.
Adding these lines disable mod_secuirity engine off.I don't know if it causes secuirity problems in future..
Tnx all...
Change the permission of folder administrator at 775 or 755
I tried all the above ideas. Without avail. For my site (which was an outdated Joomla 1.5.x site- don't ask!!!), where the backend suddenly stopped working, the final solution was switching the servers PHP version from 4 to 5.5 (even 5.4 did not work!).
I then got some strange PHP warnings in the frontend. But I then updated Joomla from the now again working backend to the last 1.5 version and everything worked fine from the on.
Phew! Maybe this helps someone later on...
In my case there was a single file with bad permissions.
It can be tricky to figure out which file has the problem so just run this to set the permissions for all the files in the directory:
chmod -R ug+rwX .
chmod -R o+rX .
Change the permissions of all of your files/directories.
Files should be 755
Directories should be 644
This is my case and my solution:
I have changed my server and got this error. I have protected my administrator folder using password protection method. So I have checked my new server and found that my protection information are not saved in control panel. also my .htaccess file (in administrator folder) is not compatible to my new server.
The solution:
Simply protect my folder using control panel
I have renamed the .htaccess file to htaccess.txt
It is done.
I hope it could be useful ;)