NetTalk Central

Author Topic: Problem running from localhost  (Read 56 times)

Richard I

  • Sr. Member
  • ****
  • Posts: 419
    • View Profile
    • Email
Problem running from localhost
« on: Today at 03:32:54 AM »
Whats gone wrong?
I was tripping between C12 and C11.1 on the same PC when, following a successful compile and run, on opening the Browser using localhost:80 or 127.0.0.1:80 I get this error-

<localhost uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Unsupported protocol
The client and server don't support a common SSL protocol version or cipher suite.>

I have NO idea how to resolve this, so would appreciate help
thanks
NT 14.35 
Richard
« Last Edit: Today at 03:51:47 AM by Richard I »

Jane

  • Sr. Member
  • ****
  • Posts: 403
  • Expert on nothing with opinions on everything.
    • View Profile
    • Email
Re: Problem running from localhost
« Reply #1 on: Today at 11:10:08 AM »
As a guess, your browser has decided to connect with TLS.
If you copy the address from the browser address bar and paste it into notepad, to you see http:// or https://  ?

Also try compiling the netdemo program and use its web client to verify that you can connect to your app with http


Richard I

  • Sr. Member
  • ****
  • Posts: 419
    • View Profile
    • Email
Re: Problem running from localhost
« Reply #2 on: Today at 02:09:40 PM »
Hi Jane,
Thanks for replying....
I see http://localhost/
but https://127.0.0.1/
and in nedtdemo using client 127.0.0.1
on connect the error message is
<a netwoprk communication error has occured.
Error= - 53 which means Open Timeout or failure error{winsock error = 10061:( WSAECONNREFUSED) Connection refused.No connection could be made because the target machine actively refused it.]
Error occured in functionm NetSimple.TakeEvent>

beyond me !
I await your responce with eager and hopeful anticipation
Cheers
Richard

« Last Edit: Today at 02:38:17 PM by Richard I »

Richard I

  • Sr. Member
  • ****
  • Posts: 419
    • View Profile
    • Email
Re: Problem running from localhost
« Reply #3 on: Today at 06:34:25 PM »
Hi Jane,
I have isolated the problem to PORT 80( which is the local PORT I routinely use) by running a webserver example using PORT 88  The example ran perfectly, and on changing the Port to 80 caused the now familiar error.
Using PORT 88 in my app also was succssful.

The running application now on PORT 80 is elusive, surviving Shut Down.
How can I discover what it is?  as Ive searched Task Manager and got the syntax for Powershell from AI both without success.

Thanks for your contact and help
Cheers
Richard
« Last Edit: Today at 06:36:14 PM by Richard I »