Re: [cups] doing things the "right" way
Matt Zagrabelny <[email protected]> Thu, 12 Oct 2023 19:58:59 -0500
| Newsgroups | gmane.comp.printing.cups.general |
|---|---|
| Message-ID | <CAN0T59jLzEPRzJaZUYSo3MAQsV0MPzF+evjW+mW-nKG0ZRG=_Q@mail.gmail.com> |
Hey Doug, Thanks for the assist! Things are working well - for the questions I asked and you answered. :) I'm still having issues with having the printer show up to clients on my local network. I issued: # cupsctl _debug_logging=0 _remote_admin=1 _remote_any=1 _share_printers=1 _user_cancel_any=0 BrowseLocalProtocols=dnssd DefaultAuthType=Basic ErrorPolicy=retry-job HostNameLookups=On IdleExitTimeout=60 JobPrivateAccess=default JobPrivateValues=default MaxLogSize=0 PageLogFormat= ServerName=zed.z.net SubscriptionPrivateAccess=default SubscriptionPrivateValues=default I'm assuming (!!) that I need to have CUPS installed on my clients - which I do - but do I need to have it installed to see shared printers from my print server? Thanks for any additional help! -m On Thu, Oct 12, 2023 at 3:51 PM Douglas Kosovic <[email protected]> wrote: > 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 > _______________________________________________ cups mailing list [email protected] https://lists.cups.org/mailman/listinfo/cups