Technical article 127292

After installing SCO OpenServer MP4 I no longer have access to the CUPS web interface

OpenServer 6.0.0

Written · Last revised

Problem

I have a SCO OpenServer 6.0.0 installed with an earlier Maintenance Pack and I am using CUPS ver 1.1.21.

I have a modified the /etc/cups/cupsd.conf file to allow me to access the CUPS web interface on port 631 of the server. i.e.

http://<CUPS server>:631

Having installed SCO OpenServer 6.0.0 MP4, I can get a

"Page not found"

error when I try to access the above URL.

Cause

SCO OpenServer 6.0.0 MP4 has an updated version of CUPS, version 1.3.9. This version has introduced many changes to CUPS. One of the major changes is the format of the cupsd.conf file.

The previous CUPS 1.1.X cupsd.conf format is not compatible with the CUPS 1.3.9. Therefore, MP4 CUPS installation will make a backup of your old cupsd.conf file and name it "cupsd.conf.bak" and will then install a new default cupsd.conf file.

The new cupsd.conf file needs to be edited in order for you to access the web interface of the new CUPS.

Solution

Edit the /etc/cups/cupsd.conf file and change the following lines:

# Only listen for connections from the local machine.
Listen localhost:631
to:
Listen 0.0.0.0:631

Or you can comment the "Listen localhost:631" and add a new line "Port 631"

# Only listen for connections from the local machine.
#Listen localhost:631
Port 631

This will fix the "Page not found" issue.

If you try to access the web interface now you will get the error:

"403 Forbidden".

To fix this, edit the cupsd.conf file and change the text:

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

to the following, if you want one specific client to have access:

 # Restrict access to the server...
<Location />
  Order allow,deny
  Allow From 10.10.10.2  <--- Single Client
</Location>

or to the following, if you want all clients to have web access

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

You can either add multiple "Allow From <IP>" lines or whole Network/sub-network "Allow From 10.10.10.0"

You will need to do the same also for the Admin Web interface, e.g for a specific client change to:

# Restrict access to the admin pages...
<Location /admin>
  Encryption Required
  Order allow,deny
  Allow From 10.10.10.2  <--- Single Client
</Location>
or for all clients change to:
# Restrict access to the admin pages...
#<Location /admin>
#  Encryption Required
#  Order allow,deny
#</Location>

Note: To allow the changes in the cupsd.conf to take effect, you will need to stop and restart CUPS using:

# /etc/init.d/cups stop
# /etc/init.d/cups start

For more information about CUPS 1.3.9, please visit http://www.cups.org

See also

TA126211 - How can I remotely administer the CUPS server from a web browser on port 631

From the Xinuos technical article database, record 127292. Reproduced with permission. The original is at www.sco.com/ta/127292, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.