Hi I just updated the printer to the latest release but now all my automation is not working anymore. I cannot login to the FTP server nor the MQTT server of the printer.
Has someone found a solution?
Best regards,
Florian
1 Like
Same here…
FTP password is unchanged. I know little about FTP and secure protocols. After messing with my FTP client I got it working with what it calls “FTP using implicit SSL” on port 990.
The client required me to accept a BBL generated certificate before connecting.
1 Like
Same here for MQTT 
I can no longer connect to FTP, tried Implicit on 990 and was not prompted to accept cert, just failed to connect due to timeout.
Port 990 is open because I can telnet to it !
I am on OSX, I have tried both Transmit and Mountain Duck, Passive / Non Passive modes, transmit says user or password is wrong, user is bblp and the password is 100% correct as displayed on the printer LCD and is the same password used on previous firmware.
Anybody know what TLS version it is using as if it’s TLSV1 or TLSV1.1 then none of my FTP applications will be able to connect, minimum is TLSV1.2.
OK, Bambu Lab Employees / Team
in vsFTPd, can you please set:
require_ssl_reuse=NO
Otherwise many FTP clients will not be able to connect.
The MQTT port is now 8883, and uses TLS. User is bbl, and password is the key in network
1 Like
Managed to connect via port 990 with Filezilla FTP client on OSX 10.15.7
It required me to accept a certificate.
Connection refused when using terminal in Win11 via ftp open (host ip)
And please make the release notes more relevant :/, nothing was indicated concerning MQTT or FTP modifications 
I’m trying to use Fetch 5.8 for macOS 13 (Ventura). Any idea what the settings might be for that client? I’m trying to connect using sFTP to the IP address shown for the X1C on my router using port 990. So far, no response. Thanks.
1 Like
there are many FTP clients that cannot connect, I think because they are using vsFTPd and the server requires the prox-backups config option to be set to make it compliant with most FTP clients.
But I dont think, Bambu will do this anytime soon, it is of no benefit to them 
Thanks. Never mind, I got it. I didn’t much like ruining access for the mobile device apps by enabling LAN Only in the onboard Network settings.
BTW, for anyone who’s interested, the protocol for my client was FTP with TLS/SSL (encryption enabled), rather than SFTP.
1 Like
I can validate these work on an X1 carbon with latest firmware but ONLY in LAN mode. Had to disable certificate validation due to self signed certificate. As soon as I bound the printer it quit responding to my connection requests. Put your IP address in where it shows 192.168.X.X
With the latest firmware version, I did not need to use LAN only mode. The settings in Filezilla that worked for me are as shown in the photo. The password I used came from the “Access Code” in the network tab of the printer.
1 Like
Where can I find a documantation about MQTT for connecting to X1C ?
If I try to connect via MQTT to X1C with username bblp / 8883 / SSL , then I got error:
client error: Error: self signed certificate in certificate chain
Thanks
Connecting using FTP in normal mode (i.e not LAN only mode) was possible also on older firmware versions. Can’t say how far back, though. Several months, at least.
X1C with latest firmware 20230921 and ftps just works in default mode (not using lan mode):
% lftp -u bblp ftps://192.168.1.1
Password:
lftp bblp@192.168.1.1:~> debug 5
lftp bblp@192.168.1.1:~> set ssl:verify-certificate no
lftp bblp@192.168.1.1:~> ls | head -n 1
---- Connecting to 192.168.1.1 (192.168.1.1) port 990
Certificate depth: 0; subject: /CN=00M0...; issuer: /C=CN/O=BBL Technologies Co., Ltd/CN=BBL CA
WARNING: Certificate verification: unable to get local issuer certificate (86:94:D0:76:D4:08:3D:FF:00:D5:B9:9D:0A:D6:FF:E0:19:42:92:AD)
WARNING: Certificate verification: unable to verify the first certificate (86:94:D0:76:D4:08:3D:FF:00:D5:B9:9D:0A:D6:FF:E0:19:42:92:AD)
WARNING: Certificate verification: certificate subject name ‘00M0...’ does not match target host name ‘192.168.1.1’ (86:94:D0:76:D4:08:3D:FF:00:D5:B9:9D:0A:D6:FF:E0:19:42:92:AD)
<--- 220 (vsFTPd 3.0.3)
---> FEAT
<--- 211-Features:
<--- AUTH TLS
<--- EPRT
<--- EPSV
<--- MDTM
<--- PASV
<--- PBSZ
<--- PROT
<--- REST STREAM
<--- SIZE
<--- TVFS
<--- UTF8
<--- 211 End
---> OPTS UTF8 ON
<--- 200 Always in UTF8 mode.
---> USER bblp
<--- 331 Please specify the password.
---> PASS XXXX
<--- 230 Login successful.
---> PWD
<--- 257 "/" is the current directory
---> PBSZ 0
<--- 200 PBSZ set to 0.
---> PROT P
<--- 200 PROT now Private.
---> PASV
<--- 227 Entering Passive Mode (192.168.1.1,195,97).
---- Connecting data socket to (192.168.1.1) port 50017
---> LIST
<--- 150 Here comes the directory listing.
WARNING: Certificate verification: certificate subject name ‘00M0...’ does not match target host name ‘192.168.1.1’ (86:94:D0:76:D4:08:3D:FF:00:D5:B9:9D:0A:D6:FF:E0:19:42:92:AD)
-rw-r--r-- 1 1000 1000 0 Apr 21 11:05 Gauge_3_plate_1.gcode.3mf
lftp bblp@192.168.1.1:/> get Gauge_3_plate_1.gcode.3mf
---> TYPE I
<--- 200 Switching to Binary mode.
---> SIZE Gauge_3_plate_1.gcode.3mf
<--- 213 0
---> MDTM Gauge_3_plate_1.gcode.3mf
<--- 213 20230421110516
---> PASV
<--- 227 Entering Passive Mode (192.168.1.1,195,167).
---- Connecting data socket to (192.168.1.1) port 50087
---> RETR Gauge_3_plate_1.gcode.3mf
<--- 150 Opening BINARY mode data connection for Gauge_3_plate_1.gcode.3mf (0 bytes).
WARNING: Certificate verification: certificate subject name ‘00M0...’ does not match target host name ‘192.168.1.1’ (86:94:D0:76:D4:08:3D:FF:00:D5:B9:9D:0A:D6:FF:E0:19:42:92:AD)
<--- 226 Transfer complete.
lftp bblp@192.168.1.1:/>
(file has 0 bytes on printer)
MQTTX? Disable “SSL Secure” option to stop verifying ssl chain.
1 Like
Just an update here for folks reference:
On a Windows 11 OS, I used the following details to connect to an X1C Printer:
Host: Machines current IP address
User: bblp
Password: “Access Code” shown in Network Section
Port: 990
LAN ONLY mode was not enabled