Server running SuSE 10.0, CUPS 1.1.23, run mode 3 Trying to administer CUPS from workstation via port 631 and Firefox browser. At server command line, I've set up lppasswd -g sys -a john and added a password. In browser, connect to http://server:631/admin, enter user name and password and am allowed in. However, I can only add printer and class. Anything else results in error 403, Forbidden. What is causing this message and how can I get round it, please? Many thanks John
On 10/08/06 04:20, John wrote:
Server running SuSE 10.0, CUPS 1.1.23, run mode 3
Trying to administer CUPS from workstation via port 631 and Firefox browser.
At server command line, I've set up lppasswd -g sys -a john and added a password.
In browser, connect to http://server:631/admin, enter user name and password and am allowed in.
However, I can only add printer and class. Anything else results in error 403, Forbidden. What is causing this message and how can I get round it, please?
Many thanks
John
Can you view http://localhost:631/printers
Darryl Gregorash wrote:
On 10/08/06 04:20, John wrote:
Server running SuSE 10.0, CUPS 1.1.23, run mode 3
Trying to administer CUPS from workstation via port 631 and Firefox browser.
At server command line, I've set up lppasswd -g sys -a john and added a password.
In browser, connect to http://server:631/admin, enter user name and password and am allowed in.
However, I can only add printer and class. Anything else results in error 403, Forbidden. What is causing this message and how can I get round it, please?
Many thanks
John
Can you view http://localhost:631/printers
only as 403 Forbidden
John wrote:
Darryl Gregorash wrote:
On 10/08/06 04:20, John wrote:
Server running SuSE 10.0, CUPS 1.1.23, run mode 3
Trying to administer CUPS from workstation via port 631 and Firefox browser.
At server command line, I've set up lppasswd -g sys -a john and added a password.
In browser, connect to http://server:631/admin, enter user name and password and am allowed in.
However, I can only add printer and class. Anything else results in error 403, Forbidden. What is causing this message and how can I get round it, please?
Many thanks
John
Can you view http://localhost:631/printers
only as 403 Forbidden
And it's the same for /jobs and classes
Hi John,
try to run CUPS as user root instead of user lp. Change the following
lines in file “/etc/cups/cups.conf”
User lp
Group lp
RunAsUser No
Darryl Gregorash wrote:
On 10/08/06 04:20, John wrote:
Server running SuSE 10.0, CUPS 1.1.23, run mode 3
Trying to administer CUPS from workstation via port 631 and Firefox browser.
At server command line, I've set up lppasswd -g sys -a john and added a password.
In browser, connect to http://server:631/admin, enter user name and password and am allowed in.
However, I can only add printer and class. Anything else results in error 403, Forbidden. What is causing this message and how can I get round it, please?
Many thanks
John
Can you view http://localhost:631/printers
only as 403 Forbidden
-- Axel Schmidt Technical Specialist Plattform Linux Axel.Schmidt@novell.com +49 179 127 6617 Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready™ www.novell.com/linux
On 10/08/06 10:22, Axel Schmidt wrote:
Hi John,
try to run CUPS as user root instead of user lp. Change the following lines in file “/etc/cups/cups.conf”
User lp Group lp RunAsUser No
AuthType Basic Restart CUPS. Now you are able to login as user root, which hopefully fixes your problem. Perhaps an equivalent, more secure, solution would be to add root as a CUPS administrator.
Darryl Gregorash wrote:
On 10/08/06 10:22, Axel Schmidt wrote:
Hi John,
try to run CUPS as user root instead of user lp. Change the following lines in file “/etc/cups/cups.conf”
User lp Group lp RunAsUser No
AuthType Basic Restart CUPS. Now you are able to login as user root, which hopefully fixes your problem.
Perhaps an equivalent, more secure, solution would be to add root as a CUPS administrator.
do you mean something like lppasswd -g sys -a root?
On 10/08/06 11:40, John wrote:
Darryl Gregorash wrote:
On 10/08/06 10:22, Axel Schmidt wrote:
Hi John,
try to run CUPS as user root instead of user lp. <snip>. Perhaps an equivalent, more secure, solution would be to add root as a CUPS administrator.
do you mean something like lppasswd -g sys -a root?
You won't need the "-g sys" because user root is already in group root, which is one of the groups CUPS looks for when it authenticates.
On Thursday, August 10, 2006, at 02:31PM, Darryl Gregorash
On 10/08/06 11:40, John wrote:
Darryl Gregorash wrote:
On 10/08/06 10:22, Axel Schmidt wrote:
Hi John,
try to run CUPS as user root instead of user lp. <snip>. Perhaps an equivalent, more secure, solution would be to add root as a CUPS administrator.
do you mean something like lppasswd -g sys -a root?
You won't need the "-g sys" because user root is already in group root, which is one of the groups CUPS looks for when it authenticates.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Darryl Gregorash wrote:
On 10/08/06 11:40, John wrote:
Darryl Gregorash wrote:
On 10/08/06 10:22, Axel Schmidt wrote:
Hi John,
try to run CUPS as user root instead of user lp. <snip>.
Perhaps an equivalent, more secure, solution would be to add root as a CUPS administrator.
do you mean something like lppasswd -g sys -a root?
You won't need the "-g sys" because user root is already in group root, which is one of the groups CUPS looks for when it authenticates.
Thanks, Darryl, but I'm afraid that made no difference either. What worries me, having found the access log entries (e.g. "GET /images/navbar.gif HTTP/1.1" 403 0), is that this might be more than just a CUPS issue although this is the first time I've tried to configure CUPS since installing SuSE 10.0. All assistance welcome John
On 10/08/06 13:21, John wrote:
Darryl Gregorash wrote:
On 10/08/06 11:40, John wrote:
Darryl Gregorash wrote:
On 10/08/06 10:22, Axel Schmidt wrote:
Hi John,
try to run CUPS as user root instead of user lp. <snip>. Perhaps an equivalent, more secure, solution would be to add root as a CUPS administrator.
do you mean something like lppasswd -g sys -a root?
You won't need the "-g sys" because user root is already in group root, which is one of the groups CUPS looks for when it authenticates.
Thanks, Darryl, but I'm afraid that made no difference either.
What worries me, having found the access log entries (e.g. "GET /images/navbar.gif HTTP/1.1" 403 0), is that this might be more than just a CUPS issue although this is the first time I've tried to configure CUPS since installing SuSE 10.0.
All assistance welcome
John
navbar.gif should be in /usr/share/doc/packages/cups/images/ and should have the following permissions/ownership: -rw-r--r-- 1 root root What is the result of the following command (you may need to run as root): find /usr/share/doc/packages/cups -name navbar* -exec ls -l "{}" \; It should look something like this: -rw-r--r-- 1 root root 6024 Mar 19 2005 /usr/share/doc/packages/cups/be/images/navbar.gif -rw-r--r-- 1 root root 3927 Mar 19 2005 /usr/share/doc/packages/cups/de/images/navbar.gif -rw-r--r-- 1 root root 4321 Mar 19 2005 /usr/share/doc/packages/cups/es/images/navbar.gif -rw-r--r-- 1 root root 2429 Mar 19 2005 /usr/share/doc/packages/cups/fr/images/navbar.gif -rw-r--r-- 1 root root 2869 Mar 19 2005 /usr/share/doc/packages/cups/images/navbar.gif I am beginning to wonder if perhaps a complete reinstallation of cups is in order. Before you go that route, however, try restarting the cups server (definitely run as root): rccups restart
Darryl Gregorash wrote:
On 10/08/06 13:21, John wrote:
Darryl Gregorash wrote:
On 10/08/06 11:40, John wrote:
Darryl Gregorash wrote:
On 10/08/06 10:22, Axel Schmidt wrote:
Hi John,
try to run CUPS as user root instead of user lp. <snip>.
Perhaps an equivalent, more secure, solution would be to add root as a CUPS administrator.
do you mean something like lppasswd -g sys -a root?
You won't need the "-g sys" because user root is already in group root, which is one of the groups CUPS looks for when it authenticates.
Thanks, Darryl, but I'm afraid that made no difference either.
What worries me, having found the access log entries (e.g. "GET /images/navbar.gif HTTP/1.1" 403 0), is that this might be more than just a CUPS issue although this is the first time I've tried to configure CUPS since installing SuSE 10.0.
All assistance welcome
John
navbar.gif should be in /usr/share/doc/packages/cups/images/ and should have the following permissions/ownership: -rw-r--r-- 1 root root
What is the result of the following command (you may need to run as root):
find /usr/share/doc/packages/cups -name navbar* -exec ls -l "{}" \;
It should look something like this:
-rw-r--r-- 1 root root 6024 Mar 19 2005 /usr/share/doc/packages/cups/be/images/navbar.gif -rw-r--r-- 1 root root 3927 Mar 19 2005 /usr/share/doc/packages/cups/de/images/navbar.gif -rw-r--r-- 1 root root 4321 Mar 19 2005 /usr/share/doc/packages/cups/es/images/navbar.gif -rw-r--r-- 1 root root 2429 Mar 19 2005 /usr/share/doc/packages/cups/fr/images/navbar.gif -rw-r--r-- 1 root root 2869 Mar 19 2005 /usr/share/doc/packages/cups/images/navbar.gif
I am beginning to wonder if perhaps a complete reinstallation of cups is in order. Before you go that route, however, try restarting the cups server (definitely run as root):
rccups restart
Thanks again, Darryl, for your suggestion. I have executed the above command line and get the results you suggest, including the permissions. I have also been looking more closely at the cupsd.conf file; I have verified that /location has order deny,allow (it was allow, deny), that AuthType is just Basic and RunAsUser is No. All of this has, so far, opened up access to all the missing graphics and pages. The downside is that I'm currently doing this from my laptop, and, although it did exhibit the same problems I was originally having from my desktop workstation, I won't be completely satisfied until I get back to the desktop tomorrow and check it. Meanwhile, thanks to all who have helped thus far. Now to get some printers configured! John
Axel Schmidt wrote:
Hi John,
try to run CUPS as user root instead of user lp. Change the following lines in file “/etc/cups/cups.conf”
User lp Group lp RunAsUser No
AuthType Basic Restart CUPS. Now you are able to login as user root, which hopefully fixes your problem.
Regards,
Axel Schmidt
John schrieb:
Darryl Gregorash wrote:
On 10/08/06 04:20, John wrote:
Server running SuSE 10.0, CUPS 1.1.23, run mode 3
Trying to administer CUPS from workstation via port 631 and Firefox browser.
At server command line, I've set up lppasswd -g sys -a john and added a password.
In browser, connect to http://server:631/admin, enter user name and password and am allowed in.
However, I can only add printer and class. Anything else results in error 403, Forbidden. What is causing this message and how can I get round it, please?
Many thanks
John
Can you view http://localhost:631/printers
only as 403 Forbidden
changing cups.conf to:
User root
Group lp
RunAsUser No
[snip] Having just checked the access log, I note entries like: "GET /images/navbar.gif HTTP/1.1" 403 0 appear frequently, so the problem isn't just restricted to the printers, jobs & classes pages. John
participants (4)
-
Axel Schmidt -
Darryl Gregorash -
James Swanson -
John