Unable to Auto create Machine running FluidNC from Network connection

[hoddoat-create]

Describe the bug/Issue
I cant get RayForge V1.12 to auto connect to my networked FluidNC CNC/Laser machine. I'm using the correct IP address (which btw allows all other mobile and windows devices to connect). I've set HTTP port to 80 and Websocket port to 23 - but unsure if that's correct.

The terminal window appears to be connecting and attempting to fetch the machine's parameters etc - but then fails with either "Connection status: ERROR - did not receive a valid HTTP response" or "ERROR - Response payload is not completed: <TransferEncodingError: 400, message='Not enough data to satisfy transfer length header.'"

I've tried for hours without success - but it seems to me neraly there!
Ive attached debug logs.

BTW your software looks great!!! - just hope I can get it to connect.

Regards Steve

rayforge_debug_2026-10-02_05-45-53.zip
rayforge_debug_2026-10-02_05-54-37.zip

[knipknap]

Hi Steve, and thanks for the kind words and the detailed debug logs — they made this one much easier to pin down.

Good news: your IP address is fine, and the machine is actually responding. What is tripping things up is the combination of ports you have configured, and I can see exactly what happens in your logs.

When you set the HTTP port to 80 and the WebSocket port to 23, Rayforge does two separate things: it talks to the machine over HTTP on port 80 (which works — your FluidNC answers correctly, and I can see it reporting "FluidNC v4.0.3" in your logs), and then it tries to open a WebSocket connection on port 23 for the live status feed. Port 23 on a FluidNC setup is the raw Telnet port, though — it just speaks plain text G-code, not the WebSocket protocol. So the handshake fails with the "did not receive a valid HTTP response" error you saw: Rayforge asks for a WebSocket conversation, and the machine politely replies with raw status lines like <Idle|MPos:...> instead.

On FluidNC, the WebSocket is not on a separate port at all — it is served by the same web server as the HTTP interface, on port 80 (your logs confirm this: the machine reports its sync port as 80). So the short-term workaround is to set both the HTTP port and the WebSocket port to 80 in the machine settings and let it retry.

That said, I have to be honest: even with the correct port, connecting to FluidNC v4 will currently still have rough edges, because the way Rayforge connects over the network was originally built around a slightly different (ESP3D-style) firmware layout, and FluidNC serves its WebSocket at a specific address on that port rather than the location Rayforge tries first. The "Response payload is not completed" errors you saw are part of the same story — a few of FluidNC's responses are shaped slightly differently than what Rayforge expects, and the connection logic gives up instead of tolerating that.

So the proper fix is on my side: I am going to add first-class FluidNC handling to the network driver so it detects FluidNC automatically and uses the correct WebSocket address and response handling without you having to guess any ports. I don't have a firm release date yet, but this report gives me everything I need to build and test it. In the meantime, if you set both ports to 80 and it gets stuck in a connect/retry loop, that is expected with your firmware version — sorry for the confusing errors, and thanks again for the excellent bug report!

[hoddoat-create]

Hi Samuel Thanks for your prompt response. I also experimented and found that I could actually get Rayforge to connect and Home – Jog etc. BUT then (as you pointed out below) it started playing up with random payload fails etc. So it seems I’ll have to wait for you FluidNC driver update. Clearly your very passionate – keep up the great work. Warmest Regards Steve 0418675823 From: Samuel ***@***.***> Sent: Friday, 2 October 2026 4:50 PM To: barebaric/rayforge ***@***.***> Cc: hoddoat-create ***@***.***>; Author ***@***.***> Subject: Re: [barebaric/rayforge] Unable to Auto create Machine running FluidNC from Network connection (Issue #490) <https://avatars.githubusercontent.com/u/149321?s=20&v=4> knipknap left a comment (barebaric/rayforge#490) <#490 (comment)> Hi Steve, and thanks for the kind words and the detailed debug logs — they made this one much easier to pin down. Good news: your IP address is fine, and the machine is actually responding. What is tripping things up is the combination of ports you have configured, and I can see exactly what happens in your logs. When you set the HTTP port to 80 and the WebSocket port to 23, Rayforge does two separate things: it talks to the machine over HTTP on port 80 (which works — your FluidNC answers correctly, and I can see it reporting "FluidNC v4.0.3" in your logs), and then it tries to open a WebSocket connection on port 23 for the live status feed. Port 23 on a FluidNC setup is the raw Telnet port, though — it just speaks plain text G-code, not the WebSocket protocol. So the handshake fails with the "did not receive a valid HTTP response" error you saw: Rayforge asks for a WebSocket conversation, and the machine politely replies with raw status lines like <Idle|MPos:...> instead. On FluidNC, the WebSocket is not on a separate port at all — it is served by the same web server as the HTTP interface, on port 80 (your logs confirm this: the machine reports its sync port as 80). So the short-term workaround is to set both the HTTP port and the WebSocket port to 80 in the machine settings and let it retry. That said, I have to be honest: even with the correct port, connecting to FluidNC v4 will currently still have rough edges, because the way Rayforge connects over the network was originally built around a slightly different (ESP3D-style) firmware layout, and FluidNC serves its WebSocket at a specific address on that port rather than the location Rayforge tries first. The "Response payload is not completed" errors you saw are part of the same story — a few of FluidNC's responses are shaped slightly differently than what Rayforge expects, and the connection logic gives up instead of tolerating that. So the proper fix is on my side: I am going to add first-class FluidNC handling to the network driver so it detects FluidNC automatically and uses the correct WebSocket address and response handling without you having to guess any ports. I don't have a firm release date yet, but this report gives me everything I need to build and test it. In the meantime, if you set both ports to 80 and it gets stuck in a connect/retry loop, that is expected with your firmware version — sorry for the confusing errors, and thanks again for the excellent bug report! — Reply to this email directly, view it on GitHub <#490?email_source=notifications&email_token=CQJVFQADJYDBZQME44FJDB35R5F2TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOJUGY4TIOBVGI22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5946948525> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/CQJVFQFS6KQXJIPDNBPGZBT5R5F2TAVCNFSNUABFKJSXA33TNF2G64TZHM4TENZSGM2TIMBQHNEXG43VMU5TKNRXGM3DGMRQGU22C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CQJVFQD2XZGYM6THOYUSIT35R5F2TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOJUGY4TIOBVGI22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CQJVFQCPCDA3HBIQDH6EFR35R5F2TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOJUGY4TIOBVGI22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA> . Download it today! You are receiving this because you authored the thread. <https://github.com/notifications/beacon/CQJVFQFKCGTNX5KQ6X77MCD5R5F2TBFCNFSM6AAAAADBAQJ3YGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTYAAAAACYTXHOW2M4TFMFZW63VGMF2XI2DPOI.gif> Message ID: ***@***.*** ***@***.***> >

[knipknap]

Hi Steve, good news — I've opened a PR that adds first-class FluidNC support to the network driver: #491

It adds a "FluidNC" protocol variant that speaks FluidNC's native web API (including serving the WebSocket on the same port as the web interface), so you won't have to guess any ports anymore. Once it's merged and released, selecting the FluidNC variant in the machine setup should just work with your v4.0.3 firmware.

Thanks again for the excellent debug logs — they made building and testing this straightforward!

[hoddoat-create]

Hey Sam – WOW now that’s responsive – huge thanks for getting onto that. Cant wait to test it out – my new 30W diode laser arrives this week. PS. Where are you located – I’m here in Victoria Australia. Warmest Regards Steve 0418675823 From: Samuel ***@***.***> Sent: Friday, 2 October 2026 9:20 PM To: barebaric/rayforge ***@***.***> Cc: hoddoat-create ***@***.***>; Author ***@***.***> Subject: Re: [barebaric/rayforge] Unable to Auto create Machine running FluidNC from Network connection (Issue #490) <https://avatars.githubusercontent.com/u/149321?s=20&v=4> knipknap left a comment (barebaric/rayforge#490) <#490 (comment)> Hi Steve, good news — I've opened a PR that adds first-class FluidNC support to the network driver: #491 <#491> It adds a "FluidNC" protocol variant that speaks FluidNC's native web API (including serving the WebSocket on the same port as the web interface), so you won't have to guess any ports anymore. Once it's merged and released, selecting the FluidNC variant in the machine setup should just work with your v4.0.3 firmware. Thanks again for the excellent debug logs — they made building and testing this straightforward! — Reply to this email directly, view it on GitHub <#490?email_source=notifications&email_token=CQJVFQFUCXSNDBA2FM52LKL5R6FNJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOJVGEZDCNRYGAZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5951216802> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/CQJVFQBC3JXAUGMD3RT3QND5R6FNJAVCNFSNUABFKJSXA33TNF2G64TZHM4TENZSGM2TIMBQHNEXG43VMU5TKNRXGM3DGMRQGU22C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CQJVFQEVGRUD5SCGDGMEO435R6FNJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOJVGEZDCNRYGAZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CQJVFQDJZZSPR2EHG3QTUUT5R6FNJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOJVGEZDCNRYGAZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA> . Download it today! You are receiving this because you authored the thread. <https://github.com/notifications/beacon/CQJVFQHH77IONJC5IDUINAD5R6FNJBFCNFSM6AAAAADBAQJ3YGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTYAAAAACYVYLSRKM4TFMFZW63VGMF2XI2DPOI.gif> Message ID: ***@***.*** ***@***.***> >

[hoddoat-create]

Hi Samuel Thanks, but how do I get the updated version? It appears no change on your website. Warmest Regards Steve 0418675823 From: Samuel ***@***.***> Sent: Sunday, 4 October 2026 11:39 PM To: barebaric/rayforge ***@***.***> Cc: hoddoat-create ***@***.***>; Author ***@***.***> Subject: Re: [barebaric/rayforge] Unable to Auto create Machine running FluidNC from Network connection (Issue #490) Closed #490 <#490> as completed via #491 <#491> . — Reply to this email directly, view it on GitHub <#490?email_source=notifications&email_token=CQJVFQCJ3ZJOUY3N5KGTPC35SJAGBA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTGMRUGQZTANBZG42TJJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#event-32443049754> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/CQJVFQGTI5ULT5UQKUKYJWT5SJAGBAVCNFSNUABFKJSXA33TNF2G64TZHM4TENZSGM2TIMBQHNEXG43VMU5TKNRXGM3DGMRQGU22C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CQJVFQF27AT4JGRBXEHNEDL5SJAGBA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTGMRUGQZTANBZG42TJJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/CQJVFQC5REJ263CIXRESJA35SJAGBA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTGMRUGQZTANBZG42TJJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI> . Download it today! You are receiving this because you authored the thread. <https://github.com/notifications/beacon/CQJVFQG7HSXOFI5DTIED7CL5SJAGBBFCNFSM6AAAAADBAQJ3YGWGG33NNVSW45C7OR4XAZNWJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XKUY3PNVWWK3TUL5UWJTYAAAAAPDOBU4NKM4TFMFZW63VGMF2XI2DPOI.gif> Message ID: ***@***.*** ***@***.***> >