Cloudprint failure and CUPS admin ERR_CONNECTION_REFUSED

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
Tassman
Posts: 7
Joined: Sun Feb 18, 2018 4:00 pm

Cloudprint failure and CUPS admin ERR_CONNECTION_REFUSED

Post by Tassman »

Hello everyone,

Cloudprint stopped working a couple of days/weeks ago, and when I tried to troubleshoot, I found that the Admin page on CUPS can't be reached : I get a connection refused message (it looks like a similar issue was logged some time ago on GitHub)

I uninstallled and re-installed cloudprint (by the way, removing cloud print does not remove CUPS), but the issue is still there.

This is what I get when I run systemctl status cups

Code: Select all

● cups.service - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.service; disabled; vendor preset: enabled)
   Active: active (running) since Tue 2018-10-16 15:51:20 BST; 34min ago
     Docs: man:cupsd(8)
 Main PID: 1408 (cupsd)
   CGroup: /system.slice/cups.service
           └─1408 /usr/sbin/cupsd -l
and with systemctl status cloudprintd -l

Code: Select all

● cloudprintd.service - Google Cloud Print proxy service
   Loaded: loaded (/lib/systemd/system/cloudprintd.service; disabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2018-10-16 16:21:34 BST; 4min 21s ago
  Process: 2620 ExecStart=/usr/sbin/cloudprintd -a /var/lib/cloudprintd/authfile.json (code=exited, statu
s=1/FAILURE)
 Main PID: 2620 (code=exited, status=1/FAILURE)

Oct 16 16:21:34 DietPiTassin systemd[1]: cloudprintd.service: Main process exited, code=exited, status=1/
FAILURE
Oct 16 16:21:34 DietPiTassin systemd[1]: cloudprintd.service: Unit entered failed state.
Oct 16 16:21:34 DietPiTassin systemd[1]: cloudprintd.service: Failed with result 'exit-code'.
Any help would be greatly appreciated,
Thanks
Tassman
Posts: 7
Joined: Sun Feb 18, 2018 4:00 pm

Re: Cloudprint failure and CUPS admin ERR_CONNECTION_REFUSED

Post by Tassman »

Hi everyone,

I just wanted to check if someone else has the same issue, before opening a bug on GitHub

Thanks
Post Reply