-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
localhost subdomain #44
Comments
This was my fault. iisexpress-proxy tried to bind to |
It seems what I described was somehow coincidental. When binding to just the default network interface, it will work most of the time for my aspnet core app. But randomly it will still fail to as another example, i use
so i will command output:
it didn't bind to 9003. EDIT: I also tried to just increment the port
and again it does not bind to port 9004. But then DOES NOT produce the error. a reboot fixes all of this.Do you have a suggestion of what could cause this? P.S. I really appreciate the work you have done here, it saves me so much time when demoing my project changes to my boss and QA team. |
Hello,
I have multiple websites served from my asp.net core mvc app.
specifically,
ct-1.localhost
andct-2.localhost
.this is the command line i tried:
npx iisexpress-proxy http://ct-1.localhost:62114 to 3000
and this is the response upon requesting it externally:
if I serve 62114 to 3000 my web portal shows, and displays my default behavior of showing me links to
ct-1.localhost
andct-2.localhost
, so the website is working correctly at bare minimum.I have also tried
ct-1.desktop-name:3000
and the browser returns IP not found.I have used your tool many times for other web apps, and I am very happy it has worked so well!
This is just a out-of-the-norm use-case. Any help is appreciated, Thanks!
The text was updated successfully, but these errors were encountered: