Sunday, September 23, 2018

Working around ASPNET Core virtual host proxy limitation.

Good afternoon,

I've recently finished my ASPNET Core web app (https://github.com/jonekcode/Fileloo any input appreciated), but my intentions weren't to shamelessly plug it.

If you go to the README of the aforementioned repository, you'll see that 'Installation' bit isn't filled at all - which brings us to the issue I'm having.

Right after finishing the app, I've tried to install it.
I've taken all the neccessary steps to get it to work on my linux-based VPS (debian 7 jessie) - and I did get it to run.. sorta.
I could do `wget localhost:5000` just fine, but doing `wget servername` was waiting for the request infinitely - which made me think: either it's an issue with SSL or I simply can't have my PHP-based website alongside a dotnet-driven website.

So, here are the questions I'm having:
- Can you run ASPNET Core website along a PHP-based website?
- Is there any way to make the process less tedious? Creating services, conf files etc was quite a hassle and I would prefer to save some time of potentional users.
- Is ASPNET Core even designed to be used for such things or have I taken a bazooka to kill a fly?

Thank you in advance!

Working around ASPNET Core virtual host proxy limitation. Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team