I'm trying to install Phabricator on a cPanel/WHM server. According to this page:
https://secure.phabricator.com/book/phabricator/article/configuration_guide/#next-steps
I need to add some URL rewriting configuration to httpd.conf, but that's not really possible with cPanel, and the error is:
Request parameter '__path__' is not set. Your rewrite rules are not configured correctly.
I tried copying the rewrite rules to Phabricator's web root, and this should work, but it doesn't, and gives a 500 error, without any error log entries.
Tried changing this line:
RewriteRule ^(.*)$ /index.php?__path__=$1 [B,L,QSA]
by removing the first slash (in case it didn't recognize this as the root directory), but it didn't help either.
What am I doing wrong, and is there a guide on installing Phabricator with cPanel/WHM (I wasn't able to find one)?
Note: I have root and WHM access to the server, but would like to avoid making changes that would require these permissions, if possible.
While this is really not the biggest problem when installing Phabricator on cPanel/WHM, the solution to it is a vHost-specific include, supported by cPanel/WHM. Here is a simple guide:
http://tecadmin.net/add-custom-settings-in-whm-cpanel-apache-virtualhost/
Some more information (although potentially more confusing) can be found here:
https://documentation.cpanel.net/display/EA/Modify+Virtualhost+Containers+With+Include+Files
Related
I have configured snipe-it following https://snipe-it.readme.io/docs/configuration and I don't seem to get pre-flight to run/launch and there is no instructions on snipe-it website unless I have missed it. I tried to use URL (http://localhost/setup) that I setup in the .env file but it says "This site can not be reached". I also tried IP but no luck. Any one out there have any idea what configuration file I need to check and how to launch it? Thank you all
I am stuck at accessing the installation page, can't seem to get it to work, it always gives me a 500 Internal Server Error error.
I have looked into some of the similar question solutions but they didn't work.
Following error you have given in your post's comment should lead you to the solution after a little search.
The problem is Magento's .htaccess file consists <IfVersion> command.
In order to use this feature mod_version module should have enabled on your Apache web server. Otherwise it will give 500 error.
In Wamp it is disabled by default.
To enable it in Wamp you can do following steps:
Find your apache config file (httpd.conf) : It usually is under /wamp/bin/apache/apache(version)/conf/httpd.conf
Open the configuration file with your favourite text editor: You can simply use Notepad. But I suggest any other one since notepad sometimes doesn't show line breaks. It will be more readable if you do (e.g. Notepad++)
Search the following text: "mod_version"
You will see following line: #LoadModule version_module modules/mod_version.so
Uncomment it, so it will become enabled: Simply delete # sign to uncomment it
Left Click on Wamp and press Restart All Services: Since you have made changes in the configuration file in order to let Apache server know about the changes you should restart at least Apache server.
Now you can check if Magento is working. If it isn't check the error log again. There might be another issue.
Following 6 steps should easily solve the error that you have provided in the comment. Also, please edit your post and add more details e.g. error log.
If first time issue after installation, probably You must enable the Apache mod_rewrite and mod_version modules, simply uncomment strings in file httpd.conf(LoadModule version_module modules/mod_version.so and LoadModule rewrite_module modules/mod_rewrite.so ) save and restart server.
https://devdocs.magento.com/guides/v2.3/install-gde/system-requirements-tech.html
Apache 2.2 or 2.4
In addition, you must enable the Apache mod_rewrite and mod_version modules. The mod_rewrite module enables the server to perform URL rewriting. The mod_version module provides flexible version checking for different httpd versions. For more information, see our Apache documentation.
This one is puzzling me for 2 days now. I've found a solution for a 404 in admin, but it is not the same that is happening here. I have exactly the same version of Magento in my local copy and production server: 1.7.0.2. The extension works great in local. I packaged it using Magento Connect and installed in production the same way. All files are there. It shows in the menu and in Configuration section, but when I click the menu to go to the report, I get the beloved 404. I loged out and in, flushed cache zillion times (including deleting the files manually) but nothing changed.This are the URLs in both envs:
(Dev)http://localhost/magentos/index.php/salestaxes/adminhtml_salestaxes/index/key/c4b8ecb58fa2062f696cacfd340/
(Prod)https://www.myserver.com/index.php/salestaxes/adminhtml_salestaxes/index/key/332e617e74a92a39a40cf5d3/
As you can see is exactly the same. I don't know wahy then I'm getting the error. Can somebody point what can I do to solve this? DO I need to check any setting? What can cause this?
This is a var_dump that I get in the router _validateControllerClassName() method:
string(115) "/home_path/public_html/app/code/community/Surpassweb/SalesTaxes/controllers/Adminhtml/SalestaxesController.php"
string(100) "/home_path/public_html/app/code/community/Surpassweb/SalesTaxes/controllers/IndexController.php"
This is the output of Alam's 404 module:
Controller Name
Controller Name: adminhtml_salestaxes
The controller name adminhtml_salestaxes matches the following controller file, but this file does not exist.
home_path/public_html/app/code/community/MyCompany/SalesTaxes/controllers/Adminhtml/SalestaxesController.php
The file is there and has 755 permissions.
This is the first line in may controller:
class MyCompany_SalesTaxes_Adminhtml_SalesTaxesController extends Mage_Adminhtml_Controller_Action {
Thanks for your time.
Are you absolutely sure the file is there? Named the same? With the same character capitalization? And that you're not in a production setup with multiple frontend webservers?
If you'll indulge me — copy the path of the controller from the Better 404 page to your computer's clipboard. Then type
$ ls -l [PASTE]
into your terminal window. My bet if the file won't be there. Also try
$ls -l app/code/community/Surpassweb/SalesTaxes/controllers/Adminhtml/
to see what files are there.
Looking at the information you provided, Magento is looking for a file named
app/code/community/MyCompany/SalesTaxes/controllers/Adminhtml/SalestaxesController.php
I don't know what your actual file is named, but looking at the class name
MyCompany_SalesTaxes_Adminhtml_SalesTaxesController
leads me to believe it might be incorrectly named SalesTaxesControlle.php. Notice the T in sales taxes is capitalized, vs the lowercase t Magento is looking for.
For some reason magento isn't registering the route to your app.
Either apache doesn't know to let magento handle it or magento doesn't know what to do with it.
Check your htaccess files and virtual host configs for the two environments.
Right off the bat I can see they're not exactly the same. One is http and one is https.
Those are probably two different virtual host configs and could be slightly different.
Next I would make sure the config xml for your module is included in magento/app/etc/modules/ folder. Make sure the module is enabled. There should be a line for that in your modules config xml file.
If you deployed it to the local vs community folder, check the magento/app/etc/local.xml and make sure disable_local_modules is set to no.
Good luck. Troubleshooting in live is always fun.
i have a serious problem in Magento Admin Backend. After login its shows a BLANK Page. i used the same files and database in different server, there it was working fine but when i have transferred files into LIVE then Admin issues came. Please help me over this as i got frustrated from last some dayz. If you need any more dertails then plz ask but i need to resolve this soon. Link: http://studywings.com/index.php/admin/
Magento ver: 1.7
flush your magento root /var/cache folder and /var/session folders, It may have previous server session that may cause problems.
Otherwise disable all third party modules and try again. I think this will help
I had the Same problem,
i have also debug the any errors occured, i tried index.php file
ini_set('display_errors', 1);
error_reporting(E_ALL);
$_SERVER['MAGE_IS_DEVELOPER_MODE'] = true;
pleced above code in index.php file. after that i have tried admin login.
showing the errors are session related, header already send errors.
i have to add the code in root/index.php file in top add the following line.
ob_start();
after that tried the login its worked.
Cheers..!
Is url changes to this after click login button or not?
http://yourdomain.com/index.php/admin/index/index/key/(key value)/
if url changes but not not show the dashboard page then go to
app/code/core/Mage/Core/Model/Session/Abstract/Varien.php
make copy of this file
Find the code for setting session cookie parameters these started on line 77
Comment out the final three lines and be sure to remove the comma after $this->getCookie()->getPath(). You should end up with this:
// set session cookie params
session_set_cookie_params(
$this->getCookie()->getLifetime(),
$this->getCookie()->getPath()
// $this->getCookie()->getDomain(),
// $this->getCookie()->isSecure(),
// $this->getCookie()->getHttponly()
also line 104 comment out :
//call_user_func_array('session_set_cookie_params', $cookieParams);
If there is no change in url after click login then try to uncomment display error and see error_log file of your server
I think this problem is due to file permissions. As you added files from one server to another, permissions might be get changed.. Try to give the permissions to all the files. Check this http://www.mage-shop.com/forum/threads/3-Magento-Admin-Backend-Blank-Page-Error
There are a number of things that can cause it, but it's most common after migrating to a new server, last time it happened to me it was an excessively low php memory_limit setting on the new server - the Admin part of the site uses a lot more resources per user than the frontend.
In general when having this issue:
Flush out your cache by emptying var/cache
Clear out sessions by emptying var/sessions
Check the magento error logs/reports for an error code in var\logs and var/reports
Turn on magento error logs in mysql if logging isn't already on! (look in core_config_data for WHERE path like 'dev/log/active'
Check if your php configuration is displaying errors
Check your apache/php error logs for more clues - memory errors will show up here for example
Try this solution
It sounds like you want to enable Developer mode. Add this to your .htaccess file:
SetEnv MAGE_IS_DEVELOPER_MODE "true"
You may also want to enable display errors in index.php:
ini_set('display_errors', 1);
The best way I have found to debug is with X-Debug in a local environment. You can also use log files to help debug in a production environment, if your unable to run X-Debug in the environment.
I've got a more detailed posting here:
http://www.molotovbliss.com/debugging-tips-and-tricks-with-magento-commerce
Consider also installing XDebug
Hope this helps you!
Just to complete the other answers....
I am upgrading a magento install, and got the same problem, in the end I had another folder inside of var/
magento/var/minifycache
Only worked after clear deleting the files inside of this folder.
I had the same problem after uninstalling an extension. I thought that clearing cache would be enough, and I did without success... later speaking with the technical team, they commented me that it did not work because I hace memcache installed, and needed to be done the cleaning via system - backend (that i coudl not see...)
I got Laravel 4 zip file from gitHub. ("laravel-master").
run composer and get all the dependencies.
i can access it from: "127.0.0.1/laravel-master/public"
but when i rename the "laravel-master" to other names, and then try to access it, i get:
"HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request."
I can not figure out what's going wrong !
You need to set your vhost docroot to /public most likely. You shouldn't be able to access it at /public since that should be the root.
Because you specifically mentioned MAMP (in the comments to an answer below), try going to Preferences on the MAMP app page, and click "--" in the cache dropdown of the PHP tab.
A simple refresh after that cleared up this same issue for me.
see Apathetic012's comment on a similar issue on Github (https://github.com/laravel/framework/issues/625)
EDIT: specifying where MAMP was mentioned.