Hi,
I have also seen this error several times. In my experience, it is
almost always caused by a misconfiguration of Nginx.
On my equipment, there is an exception to that rule when Nginx serves
outside connections as a reverse proxy to the local network, i.e.
something like: [1]
(body (list
"p
Hello,
Christopher Baines skribis:
> Ludovic Courtès writes:
>
>> Ludovic Courtès skribis:
>>
>>> The problem is most likely with the connection-to-port caching in
>>> squee’s ‘connection-socket-port’, as can be seen in this other trace
>>> where I added ‘pk’ calls in ‘connection-socket-port’:
Ludovic Courtès writes:
> Ludovic Courtès skribis:
>
>> The problem is most likely with the connection-to-port caching in
>> squee’s ‘connection-socket-port’, as can be seen in this other trace
>> where I added ‘pk’ calls in ‘connection-socket-port’:
>
> Confirmed, with a fix!
>
> https://not
Wow, thank you for the tempoary workaround.
It's quite obscure that it works though.
signature.asc
Description: PGP signature
