Testing remote connection while in dev. environment

0
0

Hi there,

I’m trying to test remote connections while I’m running wisej app. in VS dev. environment over a company (http://10.0.x.x) LAN.

I understand this isn’t possible without special configuration, and I’ve been trying to use CONVEYOR (https://keyoti.com/products/conveyor/index.html) to do it.

Fyi: Conveyor automatically provides you with a new port number to use with your IP address, and you access the app. using the IP and port.

I’ve had conveyor working at home, but it doesn’t want to play at work.

The app. starts (loader shows), but then I receive “Cannot connect to server”.

Anyone have any experience with Conveyor? or suggest another way of allowing me to connect multiple, remote clients to my app. while in dev. mode?

Thanks

Darren

Share
  • Darren
    FYI: I can send URL parameters and get a response from a remote connection. I.e. the handler (ashx) is working when using conveyor. What I can’t do is call the main app. remotely using conveyor. A wisej “Cannot connect to server” dialog appears.
  • You must to post comments
Filter
Sort by: Recently Active
0
0

IIS Express doesn’t allow external connections. VS can debug IIS. Simply change the debug option to use IIS instead of IIS Express.

  • Luca (ITG)
    Conveyor is a tunneling app. It simply makes external connections become local (127.0.0.1), which can cause other issues. Using IIS (not IIS Express) with VS in debug mode is quite normal and works very well.
  • Darren
    Hi Luca, If you’re saying that Conveyor, Wisej & IIS Exp. aren’t well suited, what is the best method to test multiple client connections to a web app. whilst developing? (Sorry, it’s still all new to me) Thanks
  • Darren
    Actually, if I select “Use Visual Studio Dev. Server” – the app. no longer works (I don’t even see the loader animation). So only “Use IIS Express” is working for me!
  • Luca (ITG)
    It’s not related to Wisej. Conveyor tunnels the connection that’s why you get 127.0.0.1 as the remote address and need to use the forward-for header. Once you deploy chances are that x-forwarded-for is null.
  • Luca (ITG)
    I don’t see the “Use Visual Studio Dev Server” option. I was referring to “Use IIS”. See https://docs.microsoft.com/en-us/visualstudio/debugger/how-to-enable-debugging-for-aspnet-applications.
Showing 1 result
Your Answer

Please first to submit.