Can not access CUPS Administration

Cedrik · 02-27-2012, 03:04 PM

Yes, clear cookies, saved passwords for cups if any etc...

Baasha · 02-27-2012, 05:11 PM

I have Firefox set up to not accept any cookies except from sites on a white list. I checked to see if there were any cookies from cups and there were none. I also found that cups was on the white list so I removed it. But unfortunately there was still no change in cups behaviour.

What I did do, is set up the printer using the Chromium browser and that name now shows on the list generated by cups/admin > manage printers when using Firefox, so that is some progress, but I still can't change anything using Firefox.

Cedrik · 02-27-2012, 06:06 PM

No saved password for cups in preferences/security ?
I didn't even know you could set a white list for accepting cookies, and I still don't see this option in my firefox :/

Baasha · 02-27-2012, 06:22 PM

Well, I was wrong about the saved password. there was one there, but deleting it still didn't make CUPS ask for one.

White list for cookies? It isn't very obvious, but it is there. I used FF for several years before I found out how to do it.

Preferences>Privacy then uncheck the accept cookies box. Then click on the exceptions button and you can fill in whatever url you want and then click Allow. In my book this should be the default behaviour.

fahrgast · 07-09-2013, 06:41 AM

Cedrik, could you solve this problem?

I have precisely the same problem with Firefox (only) trying to administrate a CUPS server in the same local network, and I have no clue of the cause. With other browsers it works fine.

fbicknel · 03-08-2019, 07:20 AM

Positively ancient thread, I know. But I just installed 18.04 and experienced the same lockout from admin functions.

The fix was easy, but I wonder why it's necessary.

I had to make a single change to /etc/cups/cupsd.conf:

Before:

Code:

# Restrict access to the admin pages...
<Location /admin>
  Order allow,deny
</Location>

After:

Code:

# Restrict access to the admin pages...
<Location /admin>
  Order allow,deny
  AuthType Default
  Require user @SYSTEM
</Location>

Of course, we now have systemctl, so restarting is now:

Code:

$ sudo systemctl restart cups

And check up on things with:

Code:

$ sudo systemctl status cups
● cups.service - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2019-03-08 08:14:01 EST; 6s ago
     Docs: man:cupsd(8)
 Main PID: 32079 (cupsd)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/cups.service
           └─32079 /usr/sbin/cupsd -l

Mar 08 08:14:01 bick-ubtu3 systemd[1]: Started CUPS Scheduler.
$

The usual steps of making sure you're part of the lpadmin group still apply, of course. My issue turned out to be that odd manifestation in the conf file.