Report Bugs Here

Moderator: Mmiscool

User avatar
By Mmiscool
#56440 Hello,

Unfortunately the web-sockets port was hard coded in both the javascript and the actual server on the esp.

Tonight I manged to decouple the hard coded port number on the server side and I am trying to make sure I have caught all references to it in the javascript.

Expect a new build with in the next few days addressing this problem with a new box on the settings page to capture this.

The next published build is going to be substantial.

There is a bug fix from tcpipchip for some of the TFT functions and a faster io function from livetv that are going to be in the next build.

Thanks for you patience.
User avatar
By Mmiscool
#56441 I am uploading a new build now that adds control of the web sockets port.

Please note certain ports can not be used for web sockets and the browser will block them. I ran in to this during my testing so check the list in the link below to make sure that what ever port you select is safe to use.

http://www-archive.mozilla.org/projects ... nning.html
User avatar
By rodrigocirilo
#56457
Mmiscool wrote:I am uploading a new build now that adds control of the web sockets port.

Please note certain ports can not be used for web sockets and the browser will block them. I ran in to this during my testing so check the list in the link below to make sure that what ever port you select is safe to use.

http://www-archive.mozilla.org/projects ... nning.html


OK thank you!!

The new version has already been uploaded?

I'm looking forward to it.