You don't need to have multiple directories for multiple domains if you are using single magento instance to fulfill your requirements.
Step 1: Point all domains to Magento root directory, i.e. same document root in the webserver (Apache or Nginx) configuration.
Step 2: Configure domain names as base URLs for each website in System Configuration in ...
First, make sure apache “rewrite_module” is enable and then restart the server.
If this hasn't worked. Then do following steps:
Edit the file /etc/apache2/apache2.conf.
Find this code:
Options Indexes FollowSymLinks
Require all granted
Change "AllowOverride None" to ...
You are either using prefork or worker, so you don't need to adjust both settings.
There's two questions that need to be answered though.
What is more important to you, having the "benefit" of more free RAM or having a server that can support more traffic?
Are you using PHP via mod_php or a CGI process
Both questions will heavily influence how many ...
If the error goes away when Apache is restarted, its one of two things.
Either you are using an Apache caching module (unlikely) or you are using mod_php with an opcode cache (eg. APC).
I would assume the latter, and that you have disabled mtime/stat checking in the opcode cache. The end result being an issue that arises, but doesn't clear until the opcode ...
To answer your questions:
1. What exactly do Web Server Rewrites do? I believe they just remove the index.php from the url? How important are they?
Correct, the remove the index.php for the URL to give you pretty URLs. Most modern websites and shops use them and I would recommend to do so.
2. Should this option be checked when using NGINX? Do Magento Web ...
As of PHP 5.6.0 always_populate_raw_post_data is deprecated and is commented out. So this value always equals 0 in php.ini
In order to override this you have two options
1. If you are using CGI/FCGI
Refer to your phpinfo(), find the value for 'user_ini.filename'. It should be sth like .user.ini or php.ini
In your web root create a file with the filename ...
I'd go for Nginx, because this is faster then Apache. There are several benchmarks on the internet about the differences and the pros and cons of them. I'd suggest to read some of them, like this one by HostingAdvice.com.
To speed up Magento more, you should be using your build in caches, of course and you should consider using Varnish, which is available ...
Fileally After Rebuilding Server again
installing php 7.1 mysql marine
got the solution
Source : After successful installation, admin URL is returning a 404?
I was also facing the same problem. My frontend's css is not loading as well as admin panel was giving 404 error page. The solution of both the problem in ubuntu is enable Apache server ...
If you're having issues with Magento not detecting the HTTPS redirect, you can add this to your the Magento .htaccess file located in your docroot:
## Nginx proxy HTTPS Fix for Magento
## Source: https://www.sonassi.com/blog/magento-kb/magento-https-redirect-loop-2
SetEnvIf X-Forwarded-Proto https HTTPS=on
Without seeing the error the only thing that comes to mind is that your production server may be missing something in the php config or have a different php version. Compare the php version on your local vs your production site by running phpinfo() in a php file.
Next you can try running Magento's magento-check.php. Download it from here: http://www....
I'm working on a solution that feels right, but this is by no means authoritative. I'd love to get feedback or questions. Here it is:
The setup involves two users:
The deploy user in the deploy group: the user who writes to the server during deployments via rsync/SSH.
The apache user in the apache group: the user that Apache runs Magento as.
The general ...
Take a look at Ask Unbuntu - How do I install curl in php5?
sudo apt-get install php5-curl php5-mcrypt
You will need to restart the server afterwards:
sudo service apache2 restart
Alternatively, if you are using php-fpm, you'll need to restart php5-fpm instead
sudo service php5-fpm restart
Depending on your PHP version you should install it using:
sudo apt-get install php5-curl
sudo apt-get install php-curl
sudo apt-get install php5-mcrypt
sudo apt-get install php-curl
You then need to restart your webserver to make the new php modules load.
Your .htaccess file is not loaded or does not contain the rewrite section and/or your vhost file from apache does not contain the correct section.
For conf file
Allow from all
It's probably due to the .htaccess not being loaded when using NginX. It's a bit of a guess but the MAGE_RUN_CODE is probably set in the .htaccess which is now ignored.
Another issue might be the domain setup of NginX, but for that you might need to add your NginX configuration to your question.
On a side note: if you're used to working with Apache (and ...
Most people run one or the other. Running them on the same server is a technical high jump and not for the faint of heart when it comes to SysAdmin issues.
The following is taken from a technical blog maintained at kbeezie.com:
Apache and Nginx Together
I’m not going to get into a lot of details about how to install and configure either http server from ...
Final I found the solution.
Replace the Base URL from http://example.com/ to //example.com/
CAUTION! The change is not allowed in magento2 admin.
I made it in MySQL in table cron_config_data and record with path='web/unsecure/base_url'. After cache:clean and varnish restart everything works smoothly in frontend.
Unfortunately problem remains in Backend. ...
The problem wasn't my .vcl file or apache config.
The problem was inside the module I use with my Magento sotre (CE 1.5.1). The module is Phoenix-media pagecache for MAgento (https://github.com/PHOENIX-MEDIA/Magento-PageCache-powered-by-Varnish) that has a function that disable all caching when Magento pages are secure.
To disable this ...
Just to close this out, a good friend of mine suggested I try this, and I am very pleased to say it worked. Perhaps it will help someone else who faces the same issue: In .htaccess file, add these lines:
# Detect the ELB header and set the header magento expects
SetEnvIf X-Forwarded-Proto https HTTPS=on
With the help of Sander Mangel on giving me a direction on what to look for, the NGINX site configuration MAGE_RUN_CODE did not have the store code as store 2, the store I wanted to show. The solution was to change the MAGE_RUN_CODE to the store code set in store 2 and issue was corrected.
You should copy index.php and .htaccess files on your second domain directory.
Open up the index.php file and look for this line (it's the last line of the file):
Add the following code right before the above code:
$mageRunCode = 'YOUR_WEBSITE_CODE';
$mageRunType = 'website';
Lastly, you need ...
You can find how to setup multiple storefronts on one Magento installation by following:
This method works for any store post Magento CE 1.4
Look to the end of the article you will see there are two methods, one that uses separate directories for each domain and a second ...
If I recall correctly, ultimately Magento will rely on session.gc_maxlifetime, despite what you've set in the store admin area.
On top of that, there is always the chance that the garbage collector trashes your session based on session.gc_divisor and session.gc_probability.
After setting your cookie lifetime in the admin to 1200 (in seconds, remember), ...
This is extremely simple to achieve and there is absolutely value in making this change despite not using a formal CDN.
CDN's don't always improve performance for your domestic market (in some cases it will make it slower). You'll lose nothing setting up a few sub domains, and potentially gain a little.
The real advantage to using sub domains for static ...
You can follow below steps to configure your multi store in magento:
1) All domains which you are adding as another domains like xyz.com, point this domain to your main magento website url abc.com
2) open your admin panel, and add website, Store and Store view in your Manage Store
3) open your .htaccess file and add below code
SetEnvIf Host .xyz.com. ...
I've been experiencing the exact same issue as above. Randomly. The site has been operating fine for months and I couldnt put my finger on what triggered it. I initially thought it was related to setting SOAP up. Anyhow, changing the file permissions on the local.xml file to 755 (from 666) seems to have done the trick (for now) but I intend to keep digging.