"Can't connect to 'log-socket': Connection refused
Bernhard Reiter
bernhard at intevation.de
Tue Apr 29 09:51:48 CEST 2025
Am Sonntag 20 April 2025 08:51:44 schrieb aslamK:
> The issue is therefore not with `gnu --verify`, but with the connection
> to `log-socket`:
> ===
> can't connect to '
> socket:///home/user/.gnupg/log-socket
> ': Connection refused
> ===
Check your configuration, e.g. ~/.gnupg/gpg.conf
mine has an inactive
#debug-level basic
#log-file socket:///home/ber/.gnupg/log-socket
so I guess that you do have a `log-file` setting in your configuration
somewhere or
> My config hasn't changed but I did upgrade my OS
> (Ubuntu 20.04.2)
Ubuntu has changed the defaults.
Try setting log-file to a file to see if this changes the connection problem.
(Similiar options exist for gpg-agent.conf and dirmngr, make sure to restart
those daemons if you change their settings to see an effect.)
Bernhard
--
https://intevation.de/~bernhard +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250429/0d0229e3/attachment.sig>
More information about the Gnupg-users
mailing list