NGINX Deployment Woes

0
0

Hi;

I’m trying to deploy a relatively simple web page application that I’d like to run under nginx on ubuntu 22.04.3 LTS.  Like the previous poster who had problems with this, I think I’ve followed all the instructions…

  • The application builds and runs fine in a local debug session.
  • published the project as a self contained package for a linux environment.
  • All files (from the publish folder) are in place and readable on the server.
  • nginx config contains the proxy_pass statement pointing to the correct URL (In this case http://127.0.0.1:5000/)
  • The web.config contains a valid server license.
  • The application binary starts successfully :

jd@server:/var/www/html/application$ sudo ./application
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:5000
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: /var/www/html/application

  • application : ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=31288f135a186eb28a16ea2f1ce476afa9df72f1, not stripped, too many notes (256)
  • Response from server is:
<!DOCTYPE html>
<html>
<head>
<title>music_db</title>
<meta charset=”utf-8” />
<meta http-equiv=”X-UA-Compatiblecontent=”IE=Edge;IE=11” />
<meta http-equiv=”Cache-Controlcontent=”no-store” />
<script src=”wisej.wx“></script>
</head>
<body>
</body>
</html>

and then a 404 on the subsequent call for wisej.wx

 

I’m obviously doing something a bit stupid (it doesn’t help that I seem to have acquired covid, and my brain is officially mush at the moment).

Can anyone offer some guidance?

 

JD

  • John Daragon
    Oh, and I have installed libgdiplus.
  • John Daragon
    I’ve just noticed the YouTube video on the subject – I’ll go watch it.
  • You must to post comments
0
0

Well, I went and watched the video.  And I got the same result.  I’m embarrassed to report that I then re-imaged the server, and installed apache2 which, surprisingly (to me, at least 🙂 ) appears to be rather more transparent to configure.  As a result, I’m now serving the application fine.  Sorry if I’ve wasted anyone’s time.  Would it be useful if I documented the step-by-step process (there are a couple of gotchas…) for Ubuntu 22?  JD

  • Julie (ITG)
    That would be great! Can you just add it as a comment on this forum post. That way, anyone who googles the same issue should be able to find it.
  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.