Location and solution of network connection failure of primary online mobile terminal Report

A user of the company goes abroad on business A China branch B, Mobile phone connection branch B Reports can be viewed normally on the intranet , Connecting to other networks shows ：“ Network connection failed ”.

After the screening ,A China branch B The mobile agent of the intranet is the domestic proxy server , Other networks are A National proxy server ,A The national proxy server executes ：curl Report address Show 403 forbidden, Domestic proxy servers execute ：curl Report address Show 200, So locate the problem .

The network architecture is ：dns->f5-> Mobile proxy server -> Centralized proxy server （nginx）-> Application proxy server (nginx)-> application server

Visit... In your local browser Report address returns 403 forbidden【nginx x.x.x】, It can be judged that it is used for proxy server ng There's a problem here .ng 403 forbidden There are four common reasons , Refer to other online summaries , As shown below ：

 One 、 Due to start users and nginx It's caused by the inconsistency of working users 

1.1 see nginx Start user of , Found to be nobody, And to use root Starting up 

 command ：ps aux | grep "nginx: worker process" | awk'{print $1}'
1.2 take nginx.config Of user Change to be consistent with the starting user ,

 command ：vi conf/nginx.conf

 Two 、 The lack of index.html perhaps index.php file , In the configuration file index index.html index.htm The file specified in this line .

1.    server {
2.      listen       80;
3.      server_name  localhost;
4.      index  index.php index.html;
5.      root  /data/www/;
6.    }
 If in /data/www/ Not below index.php,index.html When , Direct documents , Will be submitted to the 403 forbidden.

 3、 ... and 、 Permission problems , If nginx No, web Operation permission of directory , There will be 403 error .

 terms of settlement ： modify web Read and write permission of directory , Or put nginx The starting user of the directory is changed to the user of the directory , restart Nginx Can solve 

1.    chmod -R 777 /data
2.    chmod -R 777 /data/www/
 Four 、SELinux Set to on （enabled） Why .

4.1、 View the current selinux The state of .

1.    /usr/sbin/sestatus
4.2、 take SELINUX=enforcing  It is amended as follows  SELINUX=disabled  state .

1.    vi /etc/selinux/config
2.
3.    #SELINUX=enforcing
4.    SELINUX=disabled
4.3、 Restart and take effect .reboot.

1.    reboot
 restart php as well as nginx

 killall php-fpm && php-fpm &

 nginx -s reload

Here is the second one , Front end packaging files of two application servers , The directory is different , One of them is missing a directory static and index.html file , This is a small pit dug by the person in charge before the project ...

Reference resources ：

https://blog.csdn.net/darkdragonking/article/details/123199655

https://blog.csdn.net/huangchonghai/article/details/121993331