Closed davep closed 5 years ago
can I do anything to help diagnose it further?
By commenting on https://github.com/magit/ghub/issues/89.
Thanks for the pointer. Done.
Fixed with https://github.com/magit/ghub/pull/90.
The company's self-hosted GitLab is accessed via IP address and port. The configuration in .authinfo and Forge is as follows, but the following error is encountered.
machine 192.168.1.220:9081/api/v4 login lucius^forge password xxxxxxxxxx
(add-to-list 'forge-alist
'("192.168.1.220:9081" "192.168.1.220:9081/api/v4"
"192.168.1.220:9081" forge-gitlab-repository))
gnutls.el: (err=[-15] An unexpected TLS packet was received.) boot: (:priority NORMAL:%DUMBFW :hostname 192.168.1.220 :loglevel 0 :min-prime-bits nil :trustfiles (/etc/ssl/cert.pem) :crlfiles nil :keylist nil :verify-flags nil :verify-error nil :pass nil :flags nil :callbacks nil)
gnutls-negotiate: GnuTLS error: #<process 192.168.1.220>, -15
Apologies in advance if this isn't actually a
forge
issue, but having stumbled on #149 while trying to research/diagnose agnutls
error while usingforge
, I thought it worth checking.In the past couple or so days (apologies, I work on different machines often and update things at different times so it's hard to pin down) I've run into a problem that, any time I attempt to
forge-pull
in a repository hosted on either our company-internal gitlab server, or even GitHub, I get an error like this:If I set
gnutls-log-level
to2
I get the following information:Emacs is 26.2. Build options were simply:
Evaluating
gnutls-available-p
returns:Does this seem to be related to how
forge
works and, if so, can I do anything to help diagnose it further?