Notifications
Clear all

Esp8266 not responding to state change if started on a port other than 80

3 Posts
2 Users
0 Likes
581 Views
(@mrbond007)
Member
Joined: 1 year ago
Posts: 34
Topic starter  

   
Quote
(@mrbond007)
Member
Joined: 1 year ago
Posts: 34
Topic starter  

This is what I get in console.

msgport.js:70 {"notify":"init_tab"}
(index):88 Trying to open a WebSocket connection...
(index):119 Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
    at HTMLButtonElement.toggle ( http://192.168.1.3:8005/:119:15) 
toggle @ (index):119
(index):119 Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
    at HTMLButtonElement.toggle ( http://192.168.1.3:8005/:119:15) 
toggle @ (index):119
(index):119 Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
    at HTMLButtonElement.toggle ( http://192.168.1.3:8005/:119:15) 
toggle @ (index):119
(index):119 Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
    at HTMLButtonElement.toggle ( http://192.168.1.3:8005/:119:15) 
toggle @ (index):119
(index):119 Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
    at HTMLButtonElement.toggle ( http://192.168.1.3:8005/:119:15) 
toggle @ (index):119
(index):119 Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
    at HTMLButtonElement.toggle ( http://192.168.1.3:8005/:119:15) 
toggle @ (index):119
(index):119 Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
    at HTMLButtonElement.toggle ( http://192.168.1.3:8005/:119:15) 
toggle @ (index):119
(index):89 WebSocket connection to 'ws://192.168.1.3/ws' failed: 
initWebSocket @ (index):89
onLoad @ (index):112
(index):98 Connection closed
(index):88 Trying to open a WebSocket connection...
192.168.1.3/:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
(index):89 WebSocket connection to 'ws://192.168.1.3/ws' failed: 
initWebSocket @ (index):89
(index):98 Connection closed
(index):88 Trying to open a WebSocket connection...
(index):89 WebSocket connection to 'ws://192.168.1.3/ws' failed: 
initWebSocket @ (index):89
(index):98 Connection closed
(index):88 Trying to open a WebSocket connection...
(index):89 WebSocket connection to 'ws://192.168.1.3/ws' failed: 
initWebSocket @ (index):89
(index):98 Connection closed
(index):88 Trying to open a WebSocket connection...
(index):89 WebSocket connection to 'ws://192.168.1.3/ws' failed: 
initWebSocket @ (index):89
(index):98 Connection closed
(index):88 Trying to open a WebSocket connection...
​ WebSocket connection to 'ws://192.168.1.3/ws' failed: 
initWebSocket @ 192.168.1.3/:89
​ Connection closed
​ Trying to open a WebSocket connection...
​ WebSocket connection to 'ws://192.168.1.3/ws' failed: 
initWebSocket @ 192.168.1.3/:89
​ Connection closed

   
ReplyQuote
Ron
 Ron
(@zander)
Father of a miniature Wookie
Joined: 3 years ago
Posts: 6549
 

@mrbond007 There is a lot going on there, maybe start with something simple. Also let's remove some 'can't be done' and some weird.
Accessing a private network such as 192.168.0.x from the web can't be done without some help.

WEb servers as the code comments say go on port 80. Yes they can go elsewhere but if you are using off the shelf components they may not work. Start by using port 80 then if you want/need to once everything is working change the port.

You did not appear to provide an ssid or password, how did you connect?

Given the sketches and your comments you may have some relevant experience, in order to provide better answers, how many languages are you schooled in and how many years (40hrs x 50 wks) experience do you have?

First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
Sure you can learn to be a programmer, it will take the same amount of time for me to learn to be a Doctor.


   
ReplyQuote