Closed tillkamppeter closed 3 years ago
By looking into the source code of PAPPL I have found out how to make the web interface available, it requires -o server-name=...
:
hp-printer-app -o log-level=debug -o server-name=localhost -o server-port=8000 server
This should either get mentioned in the README.md
or better, either localhost
or the server's FQDN should be default and for using it only via the socket a -o socket-only
option should be added.
Printer Applications should be easy-to-use printer drivers.
@tillkamppeter There are serious security considerations when making a web interface available on a TCP/IP interface.
As for the port number, it should be assigning one automatically in the 8xxx range.
Both of those are PAPPL issues, since hp-printer-app is just an example application for PAPPL.
Tracking this in the PAPPL project as PAPPL Issue #147.
To investigate michaelrsweet/pappl#135 I tried to start
hp-printer-app
again, it is starting up and keeps running this time but I cannot access its web interface.I have tried both building and starting it directly and building and starting it as a Snap. I am using current GIT state of both hp-printer-app and PAPPL, and the OpenPrinting version of CUPS.
Command line to run it is
The web interface gets advertised via DNS-SD and gets listed in the output of
avahi-discover
. If I do not specify-o server-port=8000
it gets listed as on port 0, therefore I specified the port (which I do not need for testpappl or for the PostScript Printer Application).I cannot access
https://localhost:8000/
norhttps://till-x1yoga.local:8000/
with a web browswer.The log shows:
If I try to access with a browser nothing gets added to the log.
I can access the server with
hp-printer-app
by itself:and this actually adds to the log:
For me it seems that
hp-printer-app
is only listening on its socket,/tmp/snap.hp-printer-app/tmp/hp-printer-app1000.sock
. This makes the web interface unusable. How can I tell it on the server command line to listen on the URL so that I can access with a web browser?Or is there a bug in the Printer Application?