external/iiab
1
0
Fork 0
mirror of https://github.com/iiab/iiab.git synced 2025-03-09 15:40:17 +00:00
Code Issues Releases Wiki Activity

Update roles/cups/README.md

Browse source
This commit is contained in:
A Holt 2021-07-15 09:13:51 -04:00 • committed by GitHub
parent 695a7498df
commit 8cb617810e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

19
roles/cups/README.md
View file

@ -19,15 +19,11 @@ Or use any Linux user that is a member of the Linux group: `lpadmin`
The above uses 'SystemGroup lpadmin' in `/etc/cups/cups-files.conf` — in coordination with about 15 '@SYSTEM' lines and 'DefaultAuthType Basic' in `/etc/cups/cupsd.conf` The above uses 'SystemGroup lpadmin' in `/etc/cups/cups-files.conf` — in coordination with about 15 '@SYSTEM' lines and 'DefaultAuthType Basic' in `/etc/cups/cupsd.conf`
CUPS creates a 10-year (unsigned) https certificate during installation, that will be very confusing to non-technical users when they log in, as a result of modern browser warnings. CUPS creates a 10-year (unsigned) HTTPS certificate during installation, that will be very confusing to non-technical users when they log in, as a result of modern browser warnings.
## How it Works ## How it Works
http://localhost:631 can be useful if NGINX redirects or CUPS permissions are set wrong. Understand how IIAB configures CUPS for all IP addresses and all hostnames (IIAB redirects around the "since 2009" CUPS problem mentioned below!) by reading these in-line explanations:
Beware that http://box:631 and http://box.lan:631 will not work, due to a [known issue](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530027) with CUPS since 2009.
Understand how IIAB configures CUPS for all IP addresses and all hostnames (despite the above CUPS problem!) by reading these in-line explanations:
- [/opt/iiab/iiab/roles/cups/tasks/install.yml](tasks/install.yml) - [/opt/iiab/iiab/roles/cups/tasks/install.yml](tasks/install.yml)
@ -36,11 +32,20 @@ Modify these 2 files at your own risk:
- [/etc/cups/cupsd.conf](https://www.cups.org/doc/man-cupsd.conf.html) (run `sudo cupsctl` and `sudo cupsd -t` to verify the file!) - [/etc/cups/cupsd.conf](https://www.cups.org/doc/man-cupsd.conf.html) (run `sudo cupsctl` and `sudo cupsd -t` to verify the file!)
- [/etc/nginx/conf.d/cups.conf](templates/cups.conf.j2) - [/etc/nginx/conf.d/cups.conf](templates/cups.conf.j2)
If you make modifications to the above files, don't forget to restart systemd services: If you make modifications to the above files, don't forget to restart systemd services: (run this as root)
``` ```
systemctl restart cups cups-browsed nginx systemctl restart cups cups-browsed nginx
``` ```
## Troubleshooting
http://localhost:631 is very useful if NGINX redirects or CUPS permissions are set wrong.
Beware that http://box:631 and http://box.lan:631 will not work, due to a [known issue](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530027) with CUPS since 2009.
Run `ps aux | grep cups` and `systemctl status cups` to verify the CUPS systemd service is running well.
Finally, keep an eye on `/var/log/cups/error_log` to be sure.
## Docs and Updates ## Docs and Updates