![]() I know it can be bothersome and time consuming but you should invest the time to learn about everything that is to know about publishing your app to your production environment. without more information about that it's very hard to give any advise about it. If all of this checks out then the issue most probably is caused outside the vps in your network. you should also inspect the firewall rules of the vps itself. your configuration should be set up to open the port you want on the 0.0.0.0 address.Īlso check if your have published the app in production mode, not development mode. localhost is not the same as it's ip address. Then, create a file inside the VM holding this configuration: webaddr: 0.0.0.0:4040. If on the vps you can access the app from localhost but not from it's actual ip address then probably you have configured the app incorrect. In order to make this work inside a VM, you have to perform some additional steps: First, make sure the VM can be accessed on port 4040. ![]() The other is that you should figure out if your vps is accessible from the internet. the first part is that you should investigate wether the asp.net app is accessible from the vps itself. You can split solving this problem into two parts. It's not basic! The takeaway for this is that you should invest time in doing this. There are many people that have made it their profession to do just that. Doing it for the first time is complex and time consuming. ![]() Once you have your production environment set up correctly and figured out how to deploy your app in a reproducible manner then - and only then - you can say that deploying the next version of your app is a basic task. It's absolutely possible to deploy an asp.net app without using Nginx.įirst of all i want to clarify something. So Nginx doesn't have anything to do with it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |