[SOLVED*] an error occurred. sorry, the page you are looking for is currently unavailable (nginx)
an error occurred. sorry, the page you are looking for is currently unavailable. please try again later. if you are the system administrator of this resource then you should check the error log for details. faithfully yours, nginx.
an error occurred. sorry, the page you are looking for is currently unavailable. please try again later. if you are the system administrator of this resource then you should check the error log for details. faithfully yours, nginx.
an error occurred. sorry, the page you're trying to find is presently unprocurable. please strive once more later. if you're the computer user of this resource then you ought to check the error log for details. reliably yours, nginx.
Many reasons are analyzed as follows:
1. Before the system victimisation the network cable internal take a look at no downside, at this point the error reportable victimisation the telephone hotspot, the network informatics can't be obtained.
2. The request path of the page doesn't purpose to the required background service address: http://localhost : port variety
3. thanks to the caching mechanism of nginx, restart nginx and clean the browser’s cache:
stop command: nginx.exe -s stop;
Start command: begin nginx;
4. the foremost significant issue is (key):
the previous nginx wasn't closed, however it had been restarted, or this is: at that point, the CMD window was directly closed, thinking that it had been fully closed. In fact, the method isn't closed in the least.
if there are multiple processes, the front-end can visit the back-end and there'll be multiple turns. If miscalculation is reportable, the method should be killed and nginx are going to be OK.
[FIXED*] an error occurred. sorry, the page you are looking for is currently unavailable (nginx)
✍️ SOLUTION:-01:-
✍️ SOLUTION:-02-
EmoticonEmoticon