Orcaslicer forgets access code for X1C in LAN mode constantly

[kk7ds]

Is there an existing issue for this problem?

• I have searched the existing issues

OrcaSlicer Version

2.1.1

Operating System (OS)

macOS

OS Version

Sonoma 14.5 (latest)

Additional system information

Macbook Pro M1

Printer

Bambu X1C (in LAN-only mode)

How to reproduce

1. Open Orcaslicer
2. Go to device
3. Probably see that the printer in the unbound list
4. Click on it
5. Put in the passcode, see it move to the recent printers list
6. Close Orcaslicer, disconnect from the printer, or just let the laptop go to sleep so it disconnects
7. See that the printer as moved back to the unknown printers list, which will require a code again

Actual results

Printer constantly goes to the unknown list requiring the access code when connecting.

Expected results

Remember the access code. This worked fine before I updated to 2.1.1, continues to work fine in Bambu studio on the same machine with the same printer.

Project file & Debug log uploads

No project file required. Can reproduce just while monitoring an existing print. Very frustrating during a multi-hour print that every time I wake the machine or go back into orca to check on the print, I have to dig out the access code again.

Checklist of files to include

• Log file
• Project file

Anything else?

No response

[markus-k]

Same behaviour on P1S

[notreallylex]

Same behavior on A1 (01.03.00.00)

[chilternflyer]

OMG I thought it was just me.. My P1S does the same thing.
I've gone back to 1.9.1 and it all works fine.

[SeriousSeri]

Same on my X1C with 2.1.1, Win11

[dkoontz]

Same issue on my X1C also with v2.1.1, Win11

[Zalatra]

I'm having the same issue, Orca Slicer 2.1.1, Windows 11. Uploads from slicer when pressing "Print Plate" have also slowed to a crawl - seemed to start at the same time. Sometimes the massive delay in uploading means the transfer fails.

When it does succeed, after taking 10-15 minutes to transfer a 3-5MB file for printing, the system consistently disconnects at the point where it switches to the "Device" tab. I have to reconnect (by reentering the access number) at that point, though the print starts successfully.

[peterloron]

Same here. Orca 2.1.1, MacOS 14.5 M1, X1C

[Zalatra]

I'm having the same issue, Orca Slicer 2.1.1, Windows 11. Uploads from slicer when pressing "Print Plate" have also slowed to a crawl - seemed to start at the same time. Sometimes the massive delay in uploading means the transfer fails.

When it does succeed, after taking 10-15 minutes to transfer a 3-5MB file for printing, the system consistently disconnects at the point where it switches to the "Device" tab. I have to reconnect (by reentering the access number) at that point, though the print starts successfully.

So... as far as I know I have changed absolutely nothing in my setup, but this has stopped happening. 🤷

[kk7ds]

It occasionally doesn't happen for me. I'd say give it time :)

[HodGreeley]

Same for me. A1 Mini, Orca 2.1.1, MacOS 13.4.1.

What does "give it time" mean? It will randomly not require the code, but it's less than 1 in 5 times connecting, at best. I've tried to figure out what makes the code stick, to no avail. I can have my machine connect to watch a print, bring something else into the foreground for a while, and have to enter the code again. Quite frustrating.

[kk7ds]

@HodGreeley I said that because @Zalatra said it seemed to have "stopped happening". My point was "give it time, and I'm sure it will start happening again". Like you, it sometimes works as expected, but almost all of the time does not. I think @Zalatra was just experiencing one of those occasional works as expected spurts, so I was encouraging them not to think it had fixed itself.

[NotLordCalvert]

Sam issue here. I used to experience this from time to time, but since updating to 2.1.1 it happens every single time my computer is brought out of sleep.

[khlam]

On my Windows machine, setting "Network Profile Type" to "Private network" resolved my issue of the passcode being forgotten since updating to 2.1.1. I haven't found a solution for my Mac yet. YMMV

[massa007]

+1

[ghost]

The workaround for this is to get all your bambu printers connected in Orca, close Orca. Open your OrcaSlicer.conf (~/Library/Application Support/OrcaSlicer/OrcaSlicer.conf on macOS), find the "user_access_code" section, and update it to be just "access_code", save & close. Open Orca again, congratulations 🎉 , it won't forget your printers again.

Really this seems like a bug in the bambu network plugin more so than Orca, as the same failure is present in BS.

[kk7ds]

It definitely is a bug in the plugin because it started happening with studio as well. It definitely seems like something Orca should be able to override, as even before this my printer would occasionally be forgotten.

Anyway, I don't have that section in my config at all:

$ grep access ~/Library/Application\ Support/OrcaSlicer/OrcaSlicer.conf
$

Can you show me what it should look like so I can add it?

[HodGreeley]

@katherine-black fix works for me. Conf file section looks like

"access_code": { "serial number": "code" },

Replace serial number with the hex serial number you can find under Device > Update. Code is your 8 digit access code.

[kk7ds]

@katherine-black @HodGreeley This doesn't seem to work for me. I had no "access_code" section to copy. If I add a top-level key like you show, then start Orca, it doesn't see my printer as a "known" one, and when I click on it, it still prompts for the password. After exiting Orca, the config change I made is still there, but sorted in a different place (so it must have been read in and written back out).

[rasika-jay]

The workaround for this is to get all your bambu printers connected in Orca, close Orca. Open your OrcaSlicer.conf (~/Library/Application Support/OrcaSlicer/OrcaSlicer.conf on macOS), find the "user_access_code" section, and update it to be just "access_code", save & close. Open Orca again, congratulations 🎉 , it won't forget your printers again.

Really this seems like a bug in the bambu network plugin more so than Orca, as the same failure is present in BS.

This worked for me too

[kk7ds]

I was eventually able to get it working by putting it in the config, starting orca, selected the printer, put in the code when prompted, then exiting.. Seemed like just putting it in the config was not enough, I had to have it there and then exit orca while that was selected as the active printer or something. After that, it seems to stick now.

Anyway, hopefully Bambu will fix this properly.

[forkineye]

The workaround for this is to get all your bambu printers connected in Orca, close Orca. Open your OrcaSlicer.conf (~/Library/Application Support/OrcaSlicer/OrcaSlicer.conf on macOS), find the "user_access_code" section, and update it to be just "access_code", save & close. Open Orca again, congratulations 🎉 , it won't forget your printers again.

Really this seems like a bug in the bambu network plugin more so than Orca, as the same failure is present in BS.

Thank you! This had been driving me nuts... For those of you that aren't seeing your printer show up under user_access_code, connect to your printer on the device tab, then close OrcaSlicer and it should be there. If on Windows, the path is %appdata%\OrcaSlicer\OrcaSlicer.conf

[adho6298]

I'm having the same issue
Bambu A1 Mini firmware: 01.03.01.02
Orca Slicer: 2.2.0

[kk7ds]

Still having the same problem as well. The "workaround" mentioned above doesn't work for me more than once. As soon as I power off the printer and re-open Orca, it has forgotten it again. It's super annoying.

I note that the later versions of studio are doing the same thing, so I'm sure it's a bug in the plugin and I'm sure bambu isn't going to fix it. It would sure be nice if Orcaslicer could integrate some sort of workaround, where it re-sets the actual code from a value stored separately or something.

[okelk]

The workaround mentioned above works for me as long as I only use one printer.
I use 2 bambulabs printers on two different networks.
As soon as use the other printer on the other network orcaslicer has forgotten all the access codes again 😓

using OrcaSlicer V2.2.0

[f3l1x]

Same problem.

Bambu A1 Mini firmware: 01.04
OrcaSlicer: 2.2.0

[JustSomeHuman]

OK, I have just solved the problem for MacOS 15.1.1 when trying to test the connection and get an error connecting to the printer in the Physical Printer window.

First, make sure that you only have the most recent version of Orca in your /Applications folder Orca Slicer 2.2.0. I still had a copy of one of the beta releases and that was causing me problems.
Next go to System Settings... under the Apple Menu.
Look down (or scroll down) and Click on Privacy & Security.
Next look down (or scroll down) and click on Local Network.
Find Orca Slicer in the list. If Orca Slicer is not enabled, click to enable it. If it is already enabled, click once to disable it and the again to enable it.
If you are using Creality Print and having the same problem, make sure Creality Print is enabled as well.

This resolved all the issues I was having.

[flybrys]

Workaround kind of works for me but I still need to manually select the printer each time I load Orca

[kk7ds]

Yeah, the problem is that if the computer goes to sleep with orca running (which it does several times during a print) a script modifying orca's config won't have any effect. Which means I'd have to close and re-open orca to notice the config change, which means I'd have to save my project (which I rarely do). This should just work the way it used it - clearly there's some regression here that needs fixing.

[tueftler0]

You're right - thats bad. I thought that would be a chance for now...

[kazolar]

Solution is find the OrcaSlicer.conf -- find access_code -- you will notice it has a \n at the end of the code, get rid of the \n -- it should be just the code, then the problem will go away

If you mean inside the quoted string of the code, that's definitely not the case in my config. And if you mean outside the quoted string, that makes no sense, since the JSON deserializer wouldn't care about any whitespace.

yes, inside the quoted string. The "\n" was inside the quoted string. Fixing that has cleared the issue for me

[Coninox]

Solution is find the OrcaSlicer.conf -- find access_code -- you will notice it has a \n at the end of the code, get rid of the \n -- it should be just the code, then the problem will go away

If you mean inside the quoted string of the code, that's definitely not the case in my config. And if you mean outside the quoted string, that makes no sense, since the JSON deserializer wouldn't care about any whitespace.

yes, inside the quoted string. The "\n" was inside the quoted string. Fixing that has cleared the issue for me

When the problem appear, the entry "access_code" is not here. It's removed by Orca. (and when it's here, there is no \n)

[kazolar]

after I cleaned up the config -- i haven't had an issue (it's been just one day) -- I'm using 2.2.

[christopher-lambe]

I have this issue too. Removed Bambu Studio and enabled LAN mode on my P1S. Removed the bambu %appdata% sutff too. Deleted my OrcaSlicer.conf and BambuNetworkEngine.conf too.

OrcaSlicer 2.2 somehow forgets the printer while OrcaSlicer is running and on close removes the access_code or user_access_code entry from the OrcaSlicer.conf file. I saw it live in notepad++ - the file has changed wanna view changes? Yes and then the access_code or user_access_code entry was gone.

[TinyWorkshopDesign]

mee too same behavior there's no \n and the code disappear .....

[olsonjj]

This is extremely annoying and I'm sure others are having this issue more now since many of us are shifting our printers to LAN mode due to recent firmware news.

I've read elsewhere this seems to be related to the Bambu network plugin. Its present in both OrcaSlicer and Bambu Studio.

Perhaps @SoftFever can code around a better fix?

[orthadoxtesla]

i haven't updated my firmware on the A1 in months but it is happening to me as well and I'm hoping theres a solution soon. i had thought it might just be my crappy internet but it would appear not. any word from Orca Devs? I just moved over to orca and i like the interface but this is rather annoying.

[cswingler]

I diffed BambuStudio.conf against OrcaStudio.conf, which revealed that this block belongs at the top level of the JSON object, outside of app or other elements.

At the top of OrcaStudio.conf, after the first {, just add a block like this:

{
    "access_code": {
        "<serial number>": "<access code>"
    },
    "app": {
<snip>

I put my serial number and access code there (actually just copy/pasted it from BambuStudio.conf, and OrcaSlicer quit bothering me for my access code each time.

[kk7ds]

I diffed BambuStudio.conf against OrcaStudio.conf, which revealed that this block belongs at the top level of the JSON object, outside of app or other elements.

At the top of OrcaStudio.conf, after the first {, just add a block like this:

{
    "access_code": {
        "<serial number>": "<access code>"
    },
    "app": {
<snip>

I put my serial number and access code there (actually just copy/pasted it from BambuStudio.conf, and OrcaSlicer quit bothering me for my access code each time.

This is exactly where mine is. If it's there before Orca starts, then it works. If the computer goes to sleep or the printer is taken offline while orca is running, it forgets it again.

I really (really) don't think there's any amount of hacking the config file outside of Orca that is going to fix this, because the access code will be forgotten while Orca is running if the printer is unreachable on the network for any amount of time.

[TinyWorkshopDesign]

I diffed BambuStudio.conf against OrcaStudio.conf, which revealed that this block belongs at the top level of the JSON object, outside of app or other elements.
At the top of OrcaStudio.conf, after the first {, just add a block like this:

{
    "access_code": {
        "<serial number>": "<access code>"
    },
    "app": {
<snip>

I put my serial number and access code there (actually just copy/pasted it from BambuStudio.conf, and OrcaSlicer quit bothering me for my access code each time.

This is exactly where mine is. If it's there before Orca starts, then it works. If the computer goes to sleep or the printer is taken offline while orca is running, it forgets it again.

I really (really) don't think there's any amount of hacking the config file outside of Orca that is going to fix this, because the access code will be forgotten while Orca is running if the printer is unreachable on the network for any amount of time.

Worked for me,
in fact the string was already preset but with another (old) access code

[grahamb]

I'm seeing this myself; macOS 15.2, OrcaSlicer 2.2.0. P1S in LAN mode. My user_access_code is in the top-level of the JSON, and contains no newline characters.

[JustSomeHuman]

OK, what (or where) have I missed?I’m running the exact same situation and I have never run into an access code or any issues. PEOn Jan 27, 2025, at 1:02 PM, Graham Ballantyne ***@***.***> wrote: I'm seeing this myself; macOS 15.2, OrcaSlicer 2.2.0. P1S in LAN mode. My user_access_code is in the top-level of the JSON, and contains no newline characters. Screenshot.2025-01-27.at.12.00.34.png (view on web) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[spali]

Had the same problem, but in my case even added multiple times via add printer dialog, it contained a wrong access code in the json. So editing the json manually and enter the correct access code fixed it for me (at least today no problems).

[TinyWorkshopDesign]

Update: after changing the code at the beginning of the file, the problem appear less frequently, but still appear from time to time...

[KatieCakezz]

I diffed BambuStudio.conf against OrcaStudio.conf, which revealed that this block belongs at the top level of the JSON object, outside of app or other elements.

At the top of OrcaStudio.conf, after the first {, just add a block like this:

{
    "access_code": {
        "<serial number>": "<access code>"
    },
    "app": {
<snip>

I put my serial number and access code there (actually just copy/pasted it from BambuStudio.conf, and OrcaSlicer quit bothering me for my access code each time.

EDIT: Nope. Temp fix. stopped working after 3 projects without my computer going to sleep.

on macOS 15.2 I did this but also deleted the access section completely at the bottom of orca config. When I opened orca it gave me an error about it having to fix the config for me, had me set up the first part of the program as if it was freshly downloaded, but as soon as it was done, my printer was already there and I no longer have to re enter the code every time I open orca.

[kk7ds]

I think most people are experiencing temporary success, like the first start after changing the config, or something. Here's my definitive steps for reproduction:

0. Close Orca
1. Delete all the Orca config stuff so it's a fresh install, or modify the config all you want
2. Start Orca, find the printer, log in with the code if necessary
3. With Orca open and connected to the printer on the device tab, turn off wifi on your computer or the printer so it disappears from the network
4. Wait until Orca sees it as disconnected
5. Close and re-open Orca
6. Reconnect wifi, power on the printer, etc
7. When the printer shows up in the left-hand side of the Device tab, it's logged out (i.e. under "Other Device") and will require a code when I click on it

Every. Single. Time. Config. No config. Mangled Config. Praying to the unicorn gods. Doesn't matter.

[KatieCakezz]

I think most people are experiencing temporary success, like the first start after changing the config, or something. Here's my definitive steps for reproduction:

0. Close Orca
1. Delete all the Orca config stuff so it's a fresh install, or modify the config all you want
2. Start Orca, find the printer, log in with the code if necessary
3. With Orca open and connected to the printer on the device tab, turn off wifi on your computer or the printer so it disappears from the network
4. Wait until Orca sees it as disconnected
5. Close and re-open Orca
6. Reconnect wifi, power on the printer, etc
7. When the printer shows up in the left-hand side of the Device tab, it's logged out (i.e. under "Other Device") and will require a code when I click on it

Every. Single. Time. Config. No config. Mangled Config. Praying to the unicorn gods. Doesn't matter.

yeap. temporary for sure. I got about an hour and 3 projects before it started doing it again. I'm mad at the unicorn gods for not answering us.

[Noisyfox]

Please try this PR #8256

[TinyWorkshopDesign]

Tried via Tailscale with an x1c, seem not Working only viable solution for me right now is this python script: https://gist.githubusercontent.com/Alex-Schaefer/72a9e2491a42da2ef99fb87601955cc3/raw/0bc2423a099ebde636b4067c4cb7316df2c9fa9c/bambu-ssdp-discovery.py bambu-ssdp-discovery Text Document · 4 KB

…

On Jan 31, 2025, at 2:25 PM, Noisyfox ***@***.***> wrote: Please try this PR #8256 <#8256> — Reply to this email directly, view it on GitHub <#6169 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFS56AJJKHCQFXRKCY52LM32NN2WBAVCNFSM6AAAAABLBUJ6L2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRXGMZTMNRSGI>. You are receiving this because you commented.

[spali]

Tried via Tailscale with an x1c,
seem not Working

only viable solution for me right now is this python script:

https://gist.githubusercontent.com/Alex-Schaefer/72a9e2491a42da2ef99fb87601955cc3/raw/0bc2423a099ebde636b4067c4cb7316df2c9fa9c/bambu-ssdp-discovery.py
bambu-ssdp-discovery
Text Document · 4 KB
…

Not 100% sure about tailscale... and never checked how bambu does it exactly.
But usually most VPN's do not forward broadcast especially not SSDP which is most of the time only broadcasts to site-local address (239.255.255.250). So your script does probably the same as the printer, but in the name of the printer in the local network.
So this is probably not solvable by orca. Except providing an option to add printer by IP address directly.

[Noisyfox]

Tried via Tailscale with an x1c,
seem not Working

only viable solution for me right now is this python script:

https://gist.githubusercontent.com/Alex-Schaefer/72a9e2491a42da2ef99fb87601955cc3/raw/0bc2423a099ebde636b4067c4cb7316df2c9fa9c/bambu-ssdp-discovery.py
bambu-ssdp-discovery
Text Document · 4 KB
…

Which part did it not working? Because in theory if the python script works this new PR should also works. Could you give some more details?

[cavanaug]

So the issue I believe is OrcaSlicer erroneously removing the passcode from the config file. It seems if any connectivity problems occur while orcaslicer is open then it thinks there is a problem and then removes it from the config file. Its probably a safety mechanism to not hammer a device with an incorrect pw, but it is overly aggressive in situations where an intermittant network issue may occur. I would suggest that the app be less aggressive in removing, or retain the previous pw in a separate location in the config file and auto populate it back when doing a connect to a "new" device.

[Noisyfox]

So the issue I believe is OrcaSlicer erroneously removing the passcode from the config file. It seems if any connectivity problems occur while orcaslicer is open then it thinks there is a problem and then removes it from the config file. Its probably a safety mechanism to not hammer a device with an incorrect pw, but it is overly aggressive in situations where an intermittant network issue may occur. I would suggest that the app be less aggressive in removing, or retain the previous pw in a separate location in the config file and auto populate it back when doing a connect to a "new" device.

yes

[RyanHope]

So the issue I believe is OrcaSlicer erroneously removing the passcode from the config file. It seems if any connectivity problems occur while orcaslicer is open then it thinks there is a problem and then removes it from the config file. Its probably a safety mechanism to not hammer a device with an incorrect pw, but it is overly aggressive in situations where an intermittant network issue may occur. I would suggest that the app be less aggressive in removing, or retain the previous pw in a separate location in the config file and auto populate it back when doing a connect to a "new" device.

I agree, it will lose the connection and password mid print. So f'ing annoying.