Re: [cups] doing things the "right" way

Hi Matt,

I think the following might do what you want

ServerName zed.z.net

HostNameLookups On


I had to use HostNameLookups to prevent http://zed.z.net:631 being upgraded and redirected to https://192.168.0.254:631 instead of its hostname after enabling encryption for all CUPS locations. I would have thought ServerName would have sufficed without HostNameLookups On, but whatever.


Cheers,
Doug
-----Original Message-----
From: Matt Zagrabelny <[email protected]> 
Sent: Friday, October 13, 2023 3:28 AM
To: [email protected]
Subject: [cups] doing things the "right" way

Greetings CUPS!

I've always just hacked my way through CUPS and I'm installing a new Debian system and would like to correctly configure my print server.

I have a router, DNS/DHCP, print server with a fqdn of zed.z.net, but I'd like to configure CUPS from a client on the LAN, not the router itself.

I've configured cupsd.conf to have:

ServerAlias *

Is there a more elegant way than using a wildcard to allow me to browse to CUPS without getting a "Bad request"?

and also cupsd.conf to have:

Listen zed.z.net:631

and I browse to that location and then to /admin, which I then receive:

"""
Upgrade required

You must access this page using the URL https://192.168.0.254:631/admin.

"""

What am I doing wrong that CUPS now wants to serve via the "192" URL?

CUPS redirects the browser, but I'd like to configure things to "work correctly".


Thanks for any help!

-m

_______________________________________________
cups mailing list
[email protected]
https://lists.cups.org/mailman/listinfo/cups