ESP3D 3.0 git with Octoprint socket connection

[SOliver78]

Hello,
I have a problem connecting ESP3D 3.0 git to Octoprint.
Octoprint 1.10.2 and Network-Printing Plugin (0.1.0) run with ESP3D 2.1.4 without any problems.
With ESP3D 3.0 git I can't get a connection with socket://192.168.110.23:8282, even though the port is open according to nmap.
Does anyone know the problem?

Why I want to use ESP3D 3.0 git? Because I want to use a WT32-ETH01 with LAN.

Thank you.
Olli

[github-actions]

Thank your for submiting, please be sure you followed template or your issue may be dismissed. if you deleted the template it is here

[luc-github]

did you check the port is correct in your settings ?

[SOliver78]

In ESP3D the following settings are set:

In Octoprint the connection is:

But after a few seconds, the status is offline:

The Octoprint server can reach the web socket port of the ESP3D:

Is it possible, to look into any connection logs on the EDP3D?

[luc-github]

I am confused in 2.1 there is no websocket support for extra communication but you mention it works, are you sure you are not using telnet in 2.1 ?

in that case you should use port 23 and looking at octoprint UI I am pretty sure that is what they use
socket is different than websocket

[SOliver78]

In ESP3D 2.1 i used the data port für the socket connection in Octoprint:

Is it not the same as the websocket port in EDP3D 3.0?
If not, where i can configure the data port in ESP3D 3.0?
I have enabled the following in configuration.h:
`/* Use Websocket server

• Enable websocket communications
  */
  #define WS_DATA_FEATURE`

[luc-github]

data port in 2.1 is the telnet port in 3.0 , it is raw tcp actually
so based on your setting use the port 23 for your Network-Printing Plugin

using same port for different purpose between 2.1 and 3.0 is may be confusing, but it is not when you know what is for

[luc-github]

I guess issue is now fixed - I close ticket then

[SOliver78]

Hi, yes if you know that it is the telnet port, it works now ;)

Thanks for the hint.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.