switch from alma linux 9 to other linux distribution with dotnet 10 support

paloni

Hi
I have an app that runs on dotnet 10, but it seems like it's not available for Alma Linux 9. Is it possible to switch me to another server that supports dotnet 10? Currently i'm on opal19.opalstack.com

Thanks!

sean

paloni we do not pre-install dotnet on any of our servers, but you can install it yourself by running the following commands as your shell user:

mkdir ~/dotnet
cd ~/dotnet
wget https://builds.dotnet.microsoft.com/dotnet/Sdk/10.0.101/dotnet-sdk-10.0.101-linux-x64.tar.gz
tar zxf dotnet-sdk-10.0.101-linux-x64.tar.gz -C ~/dotnet
echo 'export DOTNET_ROOT=$HOME/dotnet' >> ~/.bash_profile
echo 'export PATH=$PATH:$HOME/dotnet' >> ~/.bash_profile

You'll need to log out ou and log back in to pick up the new environment variables. Once that's done, dotnet should work as expected:

[demo@opal19 ~]$ dotnet --version
10.0.101

To run a dotnet web app:

Create a Nginx Proxy Port app and assign it to a site.
Configure your dotnet app to listen on the proxy app's assigned port.
Run the app.

Hope this helps 🙂

paloni

hi sean

It was very helpful! I successfully installed dotnet and the app is running
But even when my app is listening on a specified port, i'm getting error '502 Bad Gateway.'

I use the default domain that I connected to my app in OpalStack.
The app is running using the dotnet tool.

Is there something else that needs to be done?

sean

paloni I've confirmed that your app is running and listening on the correct port, but the app itself returns an empty response when you make a request directly to the port, for example (with your port number masked):

$ curl http://127.0.0.1:XXXXX
curl: (52) Empty reply from server

This is not an issue with our infrastructure but something internal to your application.

My recommendation is that you configure your app to write logs into its log directory (under ~/logs/apps/) or run the app as a foreground process and watch the output. This ought to provide some data that will help you troubleshoot the issue.

paloni

yep, seems like i redirected to https by default in the app.
Now things are working!

Thanks for the quick reply and for the right direction to debug.