Hi All
I've had my Magento 2.2 store up and running fine for a while now. yesterday I rebooted the server and today I am receiving the nginx test page when trying to access my domain.
Does anyone know why this may be the case when in fact nothing else besides the reboot has occured ?
Running nginx -t produces no errors and says that everything is running ok.
Does rebooting automatically create a new nginx.conf file or map to a different directory automatically?
Please help.
Thanks in advance.
Solved! Go to Solution.
@motrMYou can follow the below URL's to properly setting up your virtual host. This is very common for many user as they update the web server configuration file and post update or restart many of the setting goes away.
Problem solved? Please give 'Kudos' and accept 'Answer as Solution'.
@motrMSeems like you virtual host configuration has been lost. Did you setup your website something like www.yourdomain.com? In case this is your local environment then try to setup your website again. In case this has happened at hosting environment your hosting provider must be able to fix it for you.
You must also ask them for proper configuration so that you do not face the same issue again in future.
Problem solved? Please give 'Kudos' and accept 'Answer as Solution'.
Do you know what reasons may have caused this to occur.?
I have checked my local as well as root nginx.conf file and it seems both do not point to the correct directory . I am wondering if somehow the files that were initially working could have been lost and the old ones rolled back ?
To fix this do I simply follow the nginx conf file setup in the magento 2 guide or is there something more to it ?
I'm a novice at this so any detailed explanations are highly appreciated
@motrMYou can follow the below URL's to properly setting up your virtual host. This is very common for many user as they update the web server configuration file and post update or restart many of the setting goes away.
Problem solved? Please give 'Kudos' and accept 'Answer as Solution'.
Many thanks as it seems that upon rebooting the server the apache and nginx services started up in the wrong order. Simply restarting the services fixed the problem we experienced.
For anyone else who has a similar problem, simply stop the services and reboot them in the correct order.