CUPS Web Interface is Disabled

[mikeboss]

quite often I'm using the CUPS Web Interface. now in macOS Golden Gate (DP1 & DP2) it's not possible to enable it anymore. interestingly, the http server seems to be running (first screenshot). but as soon as I'm trying to got to "Administration" it says "Web Interface is Disabled". I tried "cupsctl WebInterface=yes" which gives the error "cupsctl: Cannot set WebInterface directly.". editing /private/etc/cups/cupsd.conf also did not help (changing "WebInterface No" to "WebInterface Yes". any ideas?

 

[bogdanw]

I have a virtual machine with 27.0 Beta 2 (26A5368g) and http://127.0.0.1:631 returned "Safari can't Connect to the Server".
After running cupsctl WebInterface=yes, that returned cupsctl: Cannot set WebInterface directly. , and cupsctl to see the configuration, the address loaded with the same message "Web Interface is Disabled"

I've edited /private/etc/cups/cupsd.conf with yes and tried sudo launchctl kickstart -k system/org.cups.cupsd to restart the service, but it didn't have any effect.

In Sequoia 15.7.7, the webinterface is disabled by default, but it can be enabled/disabled with cupsctl WebInterface=
If someone can check in Tahoe, maybe we can get an idea if it's a macOS 27 bug or a new restriction.

 

[nmt1900]

On Tahoe it works exactly like on Sequoia, but 27.0 beta2 has same problem here as well...

 

[mikeboss]

... and http://127.0.0.1:631 returned "Safari can't Connect to the Server".

this is normal behavior. after a fresh system start, one has to print something or go into the "Printers & Scanners" section of the "System Settings". afterwards the Web Interface becomes accessible.

 

[mikeboss]

this is interesting: even with the unmolested cupsd.conf (line 23 set to "WebInterface No") I can see an error in /private/var/log/cups/error_log

"Unknown directive WebInterface on line 23 of /private/etc/cups/cupsd.conf"

this is strange...

 

[chrfr]

Seems like it’s worthy of reporting this as a bug.

 

[benwiggy]

No change in beta 3.

 

[eXoenDo]

I noticed this in Beta 1 and reported it immediately, I welcome additional reports though to get some attention on it. It is annoying. But I chose to run Beta software lol. Interestingly, they closed my bug report as "Investigation Complete - Works currently as designed"

 

[clingfreeze]

Lots of CUPS drivers rely on x86_64-Binaries, so try to install Rosetta 2, then it probably should work again. On the other hand, you'll have the same issue when macOS 28 arrives. No more Rosetta 2 then.

softwareupdate --install-rosetta

I have a Brother laser printer, I found brlaser, which is a replacement for that, it's working without Rosetta 2, optimized for Apple Silicon. You can install it via Homebrew, if you feel ok to install it via terminal.

Installing brlaser CUPS drivers for printing on Apple Silicon Macs and Brother printers

Installing brlaser CUPS drivers for printing on Apple Silicon Macs and Brother printers - README.md

gist.github.com

 

[chrfr]

Lots of CUPS drivers rely on x86_64-Binaries, so try to install Rosetta 2, then it probably should work again.

Trying to run the web interface doesn't require Rosetta though. This is a separate issue.