504 Gateway Time-out ASP.NET Core net7.0 on ubuntu 22.04

Question

504 Gateway Time-out ASP.NET Core net7.0 on ubuntu 22.04

Aleksey Volkov 0

Hello! 
I hosted an ASP.NET Core net7.0 project with Nginx on ubuntu 22.04 and everything worked fine. 
After updating the project, the project no longer responds, the browser shows 504 time out.
If I create a new project in a new folder then it doesn't work either and the response is 504.
This is not the first time this problem has arisen; after the first time I reinstalled the system so that my project would start again.
What could be the reason for 504?

Anonymous

2023-10-10T08:25:19.46+00:00

Hi,@Aleksey Volkov,Have you checked the logs on server?Also have you confirmed it was not caused by FireWall and network issue?

Aleksey Volkov 0

1) I check dotnet processes
pgrep -a dotnet
Answer:
1040525 /usr/bin/dotnet /var/www/ipieeja/IPieeja/bin/Debug/net7.0/publish/IPieeja.dll
I understand that my project has been launched, that is, in process.
2) command:
curl localhost:5000
Blank does not display anything for 10 minutes. Then I do ctrl+c.
3) I run the command:
wget localhost:5000
Answer:
wget localhost:5000                                                                                   
--2023-10-10 13:41:11--  http://localhost:5000/                                                                                      
Resolving localhost (localhost)... 127.0.0.1                                                                                         
Connecting to localhost (localhost)|127.0.0.1|:5000... connected.                                                                    
HTTP request sent, awaiting response...                                                                                              

4) I check the nginx log:
sudo journalctl -fu nginx                                                                             
Oct 08 09:25:19 ssdnodes-62698c133b597 systemd[1]: Stopped A high performance web server and a reverse proxy server.                 
Oct 08 09:25:19 ssdnodes-62698c133b597 systemd[1]: nginx.service: Consumed 1.786s CPU time.                                          
Oct 08 09:25:19 ssdnodes-62698c133b597 systemd[1]: Starting A high performance web server and a reverse proxy server...              
Oct 08 09:25:19 ssdnodes-62698c133b597 systemd[1]: Started A high performance web server and a reverse proxy server.                 
Oct 09 17:35:57 ssdnodes-62698c133b597 systemd[1]: Stopping A high performance web server and a reverse proxy server...              
Oct 09 17:35:57 ssdnodes-62698c133b597 systemd[1]: nginx.service: Deactivated successfully.                                          
Oct 09 17:35:57 ssdnodes-62698c133b597 systemd[1]: Stopped A high performance web server and a reverse proxy server.                 
Oct 09 17:35:57 ssdnodes-62698c133b597 systemd[1]: nginx.service: Consumed 1.413s CPU time.                                          
Oct 09 17:35:57 ssdnodes-62698c133b597 systemd[1]: Starting A high performance web server and a reverse proxy server...              
Oct 09 17:35:57 ssdnodes-62698c133b597 systemd[1]: Started A high performance web server and a reverse proxy server.                 
5) I check the log of the application launch service:
 sudo journalctl -fu ipieeja.service                                                                   
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]: warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]   
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]:       No XML encryptor configured. Key {5601cb83-e4f4-4b35-a4aa-7c6e9edb4630} may be persisted to storage in unencrypted form.                                                                                   
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]: info: Microsoft.Hosting.Lifetime[14]                                        
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]:       Now listening on: http://localhost:5000                               
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]: info: Microsoft.Hosting.Lifetime[0]                                         
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]:       Application started. Press Ctrl+C to shut down.                       
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]: info: Microsoft.Hosting.Lifetime[0]                                         
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]:       Hosting environment: Production                                       
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]: info: Microsoft.Hosting.Lifetime[0]                                         
Oct 09 18:04:56 ssdnodes-62698c133b597 IPieeja[1040525]:       Content root path: /var/www/ipieeja/IPieeja/bin/Debug/net7.0/publish  
    
    And in the browser:
    504 Gateway Time-out

1 answer

Your answer

Anonymous

2023-10-10T08:25:19.46+00:00

Hi,@Aleksey Volkov,Have you checked the logs on server?Also have you confirmed it was not caused by FireWall and network issue?

Answer 1

Bruce (SqlWork.com) 77,686 Volunteer Moderator

it not ngnix, if both curl and wget fail calling the site directly (http://localhost:5000). your app is hanging. you should just a attach a debugger and see why or add better logging.

Share via

504 Gateway Time-out ASP.NET Core net7.0 on ubuntu 22.04

1 answer

Your answer