Easyplayer player error 502 bad gateway problem analysis

EasyPlayer The player series project can be said to be a very open player project in the current market , Users can call the interface or develop according to their own needs , Practical , Stability is superior enough .

Today I met a user who asked EasyPlayer The problem with the player , Say you want to send in a network stream address , Can't play ,F12 View debugging information , Give the error report as shown in the figure below , The content of the error report is 502 Bad Gateway：

appear 502 Generally, errors are in the following situations ：

• The server response speed is too slow , The delay time is too long .（ exclude , because EasyPlayer The server deployed by the player has no other services , And the server is running well , Less resource usage ）
• EasyPlayer Web The service restarts frequently , The page cannot respond normally （ exclude ,Web Normal service ）
• nginx By default fastcgi（ Gateway Interface ） The process response buffer is too small , Lead to fastcgi The process is suspended

But with VLC To play and find no problem , Here's the picture ：

Here we can modify nginx To configure , Increase connection waiting time and buffer size , Go back to the page , Start broadcasting again , Problem solving .