Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

Hello Robert,

I guess I am not that good at understanding C code yet. As I wrote 
before I found that potential issue by looking at the comments: In line 
368 of http2.c there seemed to be a comment about that.


I recorded the packets that pound and Firefox send to each other using 
Wireshark and decrypted it with the TLS encryption key used by Firefox. 
The resulting files are attached. The last HTTP/2 packet Wireguard shows 
is the GOAWAY packet from the client, telling the server about a 
compression error. The packet before includes a HEADERS stream from the 
server.


Best Regards

Emanuel Loos

On 2/28/22 18:52, Robert Segall via pound wrote:
I am not sure what to make of this. Pound definitely deals with 
changes in the frame size, both in the original settings frame and 
intermediate.


I suggest you look at the code again.

On Sat, 2022-02-05 at 18:17 +0100, Emanuel Loos via pound wrote:


Hello Robert,

sorry for the late response. It still did not work and I tried to 
identify and fix the issue asking my informatics teacher for help 
before I got a response here, but she is quite busy. I think I found 
the issue but I am not fluent enough in C++ to understand the source 
code well enough to fix it alone (I actually found what could be the 
issue by looking at the comments in the code). I thought I would give 
it some time before I write here so there are not two people busy 
because of me. But somehow that did not quite work the way I expected.


Regarding the issue: I think that pound is ignoring the 
MAX_FRAME_SIZE value in 0x4 of the settings frame. Ignoring it is not 
allowed by the specification and if it is the client must throw a 
HTTP2 Protocol Error, see 
https://httpwg.org/specs/rfc7540.html#SETTINGS_MAX_FRAME_SIZE


There is a comment in the code that says pound only cares about 
changes in the table size from the SETTINGS frame.


On 12/8/21 4:14 PM, Robert Segall via pound wrote:

Hallo Emanuel

The issue with the trailing headers has been fixed in 3.0.2. I would 
appreciate your testing.


On Thu, 2021-10-07 at 01:53 +0200, Emanuel Loos via pound wrote:

Thank you for your answer!

The thing is: I get the same error with multiple different 
backends. Everything works when trying to access something with 
lynx but no normal webbrowser displays the page and curl throws an 
error. How can that be related to the backend?


Thanks in advance!

Emanuel Loos

On 4 October 2021 17:30:57 CEST, Robert Segall via pound 
 wrote:

Hallo Emanuel

It looks like there is a problem in reading the response from the 
back-end. Finding the time to track it down is more of a problem 
than actually fixing it :-(


On Sat, 2021-10-02 at 19:38 +0200, Emanuel Loos via pound wrote:
Hello, as my last message was around 20 days ago and there 
haven't been any messages regarding this issue from anyone else 
then me in the last 40 days I just wanted to ask again if anyone 
could help me to get Pound version 3 to work. I also wanted to 
ask how many people are encountering this issue (It seems a 
pretty large one to me as the one thing Pound does isn't 
working). If you don't, do you have a clue why it works for you 
and not for me? Is it because I don't use systemd?


Thanks in advance!

Emanuel Loos


--

Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19

--
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19


--
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19


pound.pcapng
Description: application/pcapng
No. Time   SourceDestination   Protocol 
Length Info
  1 0.00   192.168.178.112   185.128.244.57TCP  74  
   36354 → 443 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 SACK_PERM=1 TSval=366219334 
TSecr=0 WS=128

Frame 1: 74 bytes on wire (592 bits), 74 bytes captured (592 bits) on interface 
unknown, id 0
Ethernet II, Src: LiteonTe_f7:13:c9 (5c:93:a2:f7:13:c9), Dst: AVMAudio_af:8b:86 
(44:4e:6d:af:8b:86)
Internet Protocol Version 4, Src: 192.168.178.112, Dst: 185.128.244.57
Transmission Control Protocol, Src Port: 36354, Dst Port: 443, Seq: 0, Len: 0

No. Time   SourceDestination   Protocol 
Length Info
  2 0.013628   185.128.244.57192.168.178.112   TCP  74  
   443 → 36354 [SYN, ACK] Seq=0 Ack=1 Win=28800 Len=0 MSS=1452 SACK_PERM=1 
TSval=406855812 TSecr=366219334 WS=128

Frame 2: 74 bytes on wire (592 bits), 74 bytes captured (592 bits) on interface 
unknown, id 0
Ethernet II, Src: AVMAudio_af:8b:86 (44:4e:6d:af:8b:86), Dst: LiteonTe_f7:13:c9 
(5c:93:a2:f7:13:c9)
Internet Protocol Version 4, Src: 185.128.244.57, Dst: 192.168.178.112
Transmission Control Protocol, Src Port: 443, Dst Port: 36354, Seq: 0, Ack: 1, 
Len: 0

No. Time   SourceDestination   Protocol 
Length Info
  3 0.013952   192.168.178.112   185.128.244.57TCP  66  
   36354 → 4

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Robert Segall via pound]

I am not sure what to make of this. Pound definitely deals with changes
in the frame size, both in the original settings frame and
intermediate.

I suggest you look at the code again.

On Sat, 2022-02-05 at 18:17 +0100, Emanuel Loos via pound wrote:
> 
> Hello Robert,
> sorry for the late response. It still did not work and I tried to
>   identify and fix the issue asking my informatics teacher for
> help
>   before I got a response here, but she is quite busy. I think I
>   found the issue but I am not fluent enough in C++ to understand
>   the source code well enough to fix it alone (I actually found
> what
>   could be the issue by looking at the comments in the code). I
>   thought I would give it some time before I write here so there
> are
>   not two people busy because of me. But somehow that did not
> quite
>   work the way I expected.
> 
> 
> Regarding the issue: I think that pound is ignoring the
>   MAX_FRAME_SIZE value in 0x4 of the settings frame. Ignoring it
> is
>   not allowed by the specification and if it is the client must
>   throw a HTTP2 Protocol Error, see 
> https://httpwg.org/specs/rfc7540.html#SETTINGS_MAX_FRAME_SIZE
> There is a comment in the code that says pound only cares about
>   changes in the table size from the SETTINGS frame.
> On 12/8/21 4:14 PM, Robert Segall via
>   pound wrote:
> 
> 
> 
> >   
> >   Hallo Emanuel
> >   
> > 
> >   
> >   The issue with the trailing headers has been fixed in 3.0.2.
> > I would appreciate your testing.
> >   
> > 
> >   
> >   On Thu, 2021-10-07 at 01:53 +0200, Emanuel Loos via pound
> > wrote:
> >   
> > > Thank you for your answer!
> > > 
> > > 
> > > 
> > > The thing is: I get the same error with multiple
> > > different
> > > backends. Everything works when trying to access
> > > something with
> > > lynx but no normal webbrowser displays the page and curl
> > > throws
> > > an error. How can that be related to the backend?
> > > 
> > > 
> > > 
> > > Thanks in advance!
> > > 
> > > 
> > > 
> > > Emanuel Loos
> > > 
> > > 
> > > 
> > > On 4 October 2021 17:30:57 CEST, Robert
> > >   Segall via pound  wrote:
> > >   
> > > > Hallo Emanuel
> > > > 
> > > > 
> > > > 
> > > > It looks like there is a problem in reading the
> > > >   response from the back-end. Finding the time to
> > > > track it
> > > >   down is more of a problem than actually fixing it
> > > > :-(
> > > > 
> > > > 
> > > > 
> > > > On Sat, 2021-10-02 at 19:38 +0200, Emanuel Loos via
> > > >   pound wrote:
> > > > 
> > > > > Hello, as
> > > > >   my last message was around 20 days ago and
> > > > > there haven't
> > > > >   been any messages regarding this issue from
> > > > > anyone else
> > > > >   then me in the last 40 days I just wanted to
> > > > > ask again if
> > > > >   anyone could help me to get Pound version 3 to
> > > > > work. I
> > > > >   also wanted to ask how many people are
> > > > > encountering this
> > > > >   issue (It seems a pretty large one to me as the
> > > > > one thing
> > > > >   Pound does isn't working). If you don't, do you
> > > > > have a
> > > > >   clue why it works for you and not for me? Is it
> > > > > because I
> > > > >   don't use systemd?
> > > > > 
> > > > >   
> > > > > 
> > > > >   Thanks in advance!
> > > > > 
> > > > >   
> > > > > 
> > > > >   Emanuel Loos
> > > > > 
> > > > >   
> > > > > 
> > > > > 
> > > > 
> > > > 
> > > > -- 
> > > > 
> > > > 
> > > > Robert Segall
> > > > Apsis GmbH
> > > > Postfach, Uetikon am See,
> > > >   CH-8707
> > > > Tel: +41-32-512 30 19
> > > >   
> > > >   
> > > 
> > > 
> > >   
> > 
> >   
> >   -- 
> >   Robert Segall
> >   Apsis GmbH
> >   Postfach, Uetikon am See, CH-8707
> >   Tel: +41-32-512 30 19
> > 
> >   
> > 
> >   
> > 
> 
>   
> 
> 
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19
-- 
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

Hello Robert,

sorry for the late response. It still did not work and I tried to 
identify and fix the issue asking my informatics teacher for help before 
I got a response here, but she is quite busy. I think I found the issue 
but I am not fluent enough in C++ to understand the source code well 
enough to fix it alone (I actually found what could be the issue by 
looking at the comments in the code). I thought I would give it some 
time before I write here so there are not two people busy because of me. 
But somehow that did not quite work the way I expected.


Regarding the issue: I think that pound is ignoring the MAX_FRAME_SIZE 
value in 0x4 of the settings frame. Ignoring it is not allowed by the 
specification and if it is the client must throw a HTTP2 Protocol Error, 
see https://httpwg.org/specs/rfc7540.html#SETTINGS_MAX_FRAME_SIZE 



There is a comment in the code that says pound only cares about changes 
in the table size from the SETTINGS frame.


On 12/8/21 4:14 PM, Robert Segall via pound wrote:

Hallo Emanuel

The issue with the trailing headers has been fixed in 3.0.2. I would 
appreciate your testing.


On Thu, 2021-10-07 at 01:53 +0200, Emanuel Loos via pound wrote:

Thank you for your answer!

The thing is: I get the same error with multiple different backends. 
Everything works when trying to access something with lynx but no 
normal webbrowser displays the page and curl throws an error. How can 
that be related to the backend?


Thanks in advance!

Emanuel Loos

On 4 October 2021 17:30:57 CEST, Robert Segall via pound 
 wrote:

Hallo Emanuel

It looks like there is a problem in reading the response from the 
back-end. Finding the time to track it down is more of a problem 
than actually fixing it :-(


On Sat, 2021-10-02 at 19:38 +0200, Emanuel Loos via pound wrote:
Hello, as my last message was around 20 days ago and there haven't 
been any messages regarding this issue from anyone else then me in 
the last 40 days I just wanted to ask again if anyone could help me 
to get Pound version 3 to work. I also wanted to ask how many 
people are encountering this issue (It seems a pretty large one to 
me as the one thing Pound does isn't working). If you don't, do you 
have a clue why it works for you and not for me? Is it because I 
don't use systemd?


Thanks in advance!

Emanuel Loos


--

Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19

--
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19

-- 
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Robert Segall via pound]

Hallo Emanuel

The issue with the trailing headers has been fixed in 3.0.2. I would
appreciate your testing.

On Thu, 2021-10-07 at 01:53 +0200, Emanuel Loos via pound wrote:
> Thank you for your answer!
> 
> The thing is: I get the same error with multiple different backends.
> Everything works when trying to access something with lynx but no
> normal webbrowser displays the page and curl throws an error. How can
> that be related to the backend?
> 
> Thanks in advance!
> 
> Emanuel Loos
> 
> On 4 October 2021 17:30:57 CEST, Robert Segall via pound <
> pound@apsis.ch> wrote:
> > Hallo Emanuel
> > 
> > It looks like there is a problem in reading the response from the
> > back-end. Finding the time to track it down is more of a problem
> > than actually fixing it :-(
> > 
> > On Sat, 2021-10-02 at 19:38 +0200, Emanuel Loos via pound wrote:
> > > Hello, as my last message was around 20 days ago and there
> > > haven't been any messages regarding this issue from anyone else
> > > then me in the last 40 days I just wanted to ask again if anyone
> > > could help me to get Pound version 3 to work. I also wanted to
> > > ask how many people are encountering this issue (It seems a
> > > pretty large one to me as the one thing Pound does isn't
> > > working). If you don't, do you have a clue why it works for you
> > > and not for me? Is it because I don't use systemd?
> > > 
> > > Thanks in advance!
> > > 
> > > Emanuel Loos
> > > 
> > -- 
> > Robert Segall
> > Apsis GmbH
> > Postfach, Uetikon am See, CH-8707
> > Tel: +41-32-512 30 19
> 
> 
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19
-- 
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

Thank you for your answer!

The thing is: I get the same error with multiple different backends. Everything 
works when trying to access something with lynx but no normal webbrowser 
displays the page and curl throws an error. How can that be related to the 
backend?

Thanks in advance!

Emanuel Loos

On 4 October 2021 17:30:57 CEST, Robert Segall via pound  wrote:
>Hallo Emanuel
>It looks like there is a problem in reading the response from the back-
>end. Finding the time to track it down is more of a problem than
>actually fixing it :-(
>On Sat, 2021-10-02 at 19:38 +0200, Emanuel Loos via pound wrote:
>> Hello, as my last message was around 20 days ago and there haven't
>> been any messages regarding this issue from anyone else then me in
>> the last 40 days I just wanted to ask again if anyone could help me
>> to get Pound version 3 to work. I also wanted to ask how many people
>> are encountering this issue (It seems a pretty large one to me as the
>> one thing Pound does isn't working). If you don't, do you have a clue
>> why it works for you and not for me? Is it because I don't use
>> systemd?
>> 
>> Thanks in advance!
>> 
>> Emanuel Loos
>> 
>-- 
>Robert Segall
>Apsis GmbH
>Postfach, Uetikon am See, CH-8707
>Tel: +41-32-512 30 19
-- 
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Robert Segall via pound]

Hallo Emanuel
It looks like there is a problem in reading the response from the back-
end. Finding the time to track it down is more of a problem than
actually fixing it :-(
On Sat, 2021-10-02 at 19:38 +0200, Emanuel Loos via pound wrote:
> Hello, as my last message was around 20 days ago and there haven't
> been any messages regarding this issue from anyone else then me in
> the last 40 days I just wanted to ask again if anyone could help me
> to get Pound version 3 to work. I also wanted to ask how many people
> are encountering this issue (It seems a pretty large one to me as the
> one thing Pound does isn't working). If you don't, do you have a clue
> why it works for you and not for me? Is it because I don't use
> systemd?
> 
> Thanks in advance!
> 
> Emanuel Loos
> 
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19
-- 
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

FCDAD89A700 thr_http start
>>>     /build/pound-hSCqfU/pound-3.0/src/http.c:535
>>>     7FCDAD89A700 start loop /build/pound-hSCqfU/pound-3.0/src/http.c:539
>>>     7FCDAE09B700 thr_http start
>>>     /build/pound-hSCqfU/pound-3.0/src/http.c:535
>>>     7FCDAE09B700 start loop /build/pound-hSCqfU/pound-3.0/src/http.c:539
>>>     7FCDAE89C700 thr_http start
>>>     /build/pound-hSCqfU/pound-3.0/src/http.c:535
>>>     7FCDAE89C700 start loop /build/pound-hSCqfU/pound-3.0/src/http.c:539
>>>     7FCDAF09D700 thr_http start
>>>     /build/pound-hSCqfU/pound-3.0/src/http.c:535
>>>     7FCDAF09D700 start loop /build/pound-hSCqfU/pound-3.0/src/http.c:539
>>>     7FCDAF09D700 peer address 172.16.237.1
>>>     /build/pound-hSCqfU/pound-3.0/src/http.c:549
>>>     7FCDAF09D700 start sni /build/pound-hSCqfU/pound-3.0/src/util.c:157
>>>     7FCDAF09D700 sni for devuan.local
>>>     /build/pound-hSCqfU/pound-3.0/src/util.c:165
>>>     Segmentation fault
>>>
>>>
>>> -T
>>>
>>>> On Aug 19, 2021, at 16:45, Emanuel Loos via pound >>> <mailto:pound@apsis.ch>> wrote:
>>>>
>>>> Thank you for the kind words!
>>>>
>>>> Looks like pound really wasn't running when you checked. It should 
>>>> when and after you receive this email.
>>>>
>>>> Here is what Pound writes when trying to access a page with Firefox:
>>>>
>>>> 700 start sni /build/pound-hSCqfU/pound-3.0/src/util.c:157
>>>> 7FD71E405700 start do_request 
>>>> /build/pound-hSCqfU/pound-3.0/src/http.c:257
>>>> 7FD71E405700 start do_http2 
>>>> /build/pound-hSCqfU/pound-3.0/src/http2.c:296
>>>> 7FD71E405700 start get_be /build/pound-hSCqfU/pound-3.0/src/http.c:143
>>>> 7FD724C12700 start backend_2 
>>>> /build/pound-hSCqfU/pound-3.0/src/backend.c:213
>>>> 100.64.250.47 - - [Fri Aug 20 01:00:12 2021] "GET /index.php/login 
>>>> HTTP/1.1" 200 8985
>>>>
>>>> Surprisingly it didn't crash this time. Looks like the crashes where 
>>>> independent from this and caused due to restarting it to fast. 
>>>> However, even though Pound says everything goes as it should it 
>>>> doesn't: Firefox reports a Network Protocol Error (see attached 
>>>> screenshots). Lynx (a command line webbrowser), however, is able to 
>>>> access the service without problems. Putting this together with the 
>>>> error curl gives I have an idea what the issue could be: I think, 
>>>> since Pound is writing about HTTP1.1 and curl is writing about HTTP2 
>>>> the HTTP versions might be somehow mixed up or wrongly identified. I 
>>>> don't know how to check and/or fix this, however.
>>>>
>>>> Emanuel Loos
>>>>
>>>> Am 20.08.21 um 00:01 schrieb Todd Fleisher via pound:
>>>>> FWIW - right now I can connect to the public IPv4 address for 
>>>>> nc.emanuel-loos.eu <http://nc.emanuel-loos.eu> 
>>>>> <http://nc.emanuel-loos.eu <http://nc.emanuel-loos.eu>> 
>>>>> (185.128.244.57), only the onion service @ 
>>>>> http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login
>>>>>  
>>>>> <http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login>
>>>>>  
>>>>> <http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login
>>>>>  
>>>>> <http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login>>
>>>>>  is 
>>>>> responding. The public IPv4 address refuses connections.
>>>>>
>>>>> Assuming the onion service points to the same apache2 backend and 
>>>>> it actually works beyond just loading the login page, this would 
>>>>> seem to point to an issue with your pound instance - maybe it is no 
>>>>> longer running due to a crash or you stopped it deliberately. Once 
>>>>> you verify it is running, you could also try to attach an strace to 
>>>>> pound's PID to see what is happening when you make a request to it 
>>>>> and/or when it is hammering your CPU like you mentioned below.
>>>>>
>>>>> -T
>>>>>
>>>>> P.S. Kudos to you for being aware of the power of self-hosting and 
>>>>> trying to learn more about it. It feels like an overlooked concept 
>>>>> with younger generations so it’s refreshing to see sentiments like 
>>>>> yours
>>>>>
>>>>>> On Aug 19, 2021, at 13:34, Emanuel Loos via pound >>>>> <mailto:pound@apsis.ch> <mailto:pound@apsis.ch 
>>>>>> <mailto:pound@apsis.ch>>> wrote:
>>>>>>
>>>>>> Am 19.08.21 um 21:39 schrieb Emanuel Loos via pound:
>>>>>>> If it helps: The backend is an apache2 web server with a lot of 
>>>>>>> PHP (Nextcloud) and also available on this Tor Onion Service:
>>>>>>>
>>>>>>> http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion 
>>>>>>> <http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion> 
>>>>>>> <http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion 
>>>>>>> <http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion>>
>>>>>>>  
>>>>>>>
>>>>>>>
>>>>>>> Thanks in advance!
>>>>>>>
>>>>>>> Emanuel Loos
>>>>>>>
>>>>>>> Am 19.08.21 um 21:02 schrieb Emanuel Loos via pound:
>>>>>>>>> -Original Message-
>>>>>>>>> From: pound >>>>>>>> <mailto:pound-boun...@apsis.ch>> On Behalf Of Emanuel Loos via 
>>>>>>>>> pound
>>>>>>>>> Sent: Thursday, August 19, 2021 10:34 AM
>>>>>>>>> To: pound@apsis.ch <mailto:pound@apsis.ch>
>>>>>>>>> Cc: Emanuel Loos >>>>>>>> <mailto:m...@mailing-lists.emanuel-loos.eu>>
>>>>>>>>> Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and 
>>>>>>>>> ERR_CONNECTION refused in Chromium but lynx works
>>>>>>>>>
>>>>>>>>> Hello the third time,
>>>>>>>>>
>>>>>>>>> just reporting that for some reason Pound just started using 
>>>>>>>>> the full CPU power on one core:
>>>>>>>>>
>>>>>>>>>     PID USER  PR  NI    VIRT    RES SHR S %CPU %MEM ZEIT+ 
>>>>>>>>> BEFEHL
>>>>>>>>>    3590 root  20   0 1274244  16664 3144 R 99,3   0,1 
>>>>>>>>> 37:35.29 pound
>>>>>>>>>
>>>>>>>>> it is not a problem for me right now as it is a small private 
>>>>>>>>> server doing not much else (except sending this email) right 
>>>>>>>>> now but I don't thing that is how it should be. Anyway I think 
>>>>>>>>> I'll still keep Pound running (or maybe restart it) for now so 
>>>>>>>>> if anyone wants to help me with my problem Pound is online and 
>>>>>>>>> the problem can investigated easier.
>>>>>>>>>
>>>>>>>>> Thanks in advance!
>>>>>>>>>
>>>>>>>>> Emanuel Loos
>>>>>>>>>
>>>>>>>>> Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:
>>>>>>>>>> Hello again,
>>>>>>>>>>
>>>>>>>>>> just wanted to add that with curl this happens:
>>>>>>>>>>
>>>>>>>>>> emanuel@devuan-emanuel:~$ curl
>>>>>>>>>> https://nc.emanuel-loos.eu/index.php/login 
>>>>>>>>>> <https://nc.emanuel-loos.eu/index.php/login>
>>>>>>>>>> curl: (92) HTTP/2 stream 0 was not closed cleanly: 
>>>>>>>>>> PROTOCOL_ERROR (err
>>>>>>>>>> 1)
>>>>>>>>>>
>>>>>>>>>> I left Pound running on my server so as long as there is no crash
>>>>>>>>>> (like when trying to connect using Firefox or Chromium but not 
>>>>>>>>>> lynx or
>>>>>>>>>> curl) it should stay online. You are welcome to test it 
>>>>>>>>>> yourself if it
>>>>>>>>>> helps.
>>>>>>>>>>
>>>>>>>>>> Anyone got an idea what the problem could be or how to debug 
>>>>>>>>>> it further?
>>>>>>>>>>
>>>>>>>>>> Thanks in advance!
>>>>>>>>>>
>>>>>>>>>> Emanuel Loos
>>>>>
>>>>>
>>>>>
>>>>
>>>> -- 
>>>> pound mailing list
>>>> pound@apsis.ch <mailto:pound@apsis.ch>
>>>> https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch
>>>>
>>>
>>>
>>
>
>-- 
>pound mailing list
>pound@apsis.ch
>https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch
-- 
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

 refreshing to see sentiments like 
yours


On Aug 19, 2021, at 13:34, Emanuel Loos via pound <mailto:pound@apsis.ch> <mailto:pound@apsis.ch 
<mailto:pound@apsis.ch>>> wrote:


Am 19.08.21 um 21:39 schrieb Emanuel Loos via pound:
If it helps: The backend is an apache2 web server with a lot of 
PHP (Nextcloud) and also available on this Tor Onion Service:


http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion> 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion>> 



Thanks in advance!

Emanuel Loos

Am 19.08.21 um 21:02 schrieb Emanuel Loos via pound:

-Original Message-
From: pound <mailto:pound-boun...@apsis.ch>> On Behalf Of Emanuel Loos via 
pound

Sent: Thursday, August 19, 2021 10:34 AM
To: pound@apsis.ch <mailto:pound@apsis.ch>
Cc: Emanuel Loos <mailto:m...@mailing-lists.emanuel-loos.eu>>
Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and 
ERR_CONNECTION refused in Chromium but lynx works


Hello the third time,

just reporting that for some reason Pound just started using 
the full CPU power on one core:


    PID USER  PR  NI    VIRT    RES SHR S %CPU %MEM ZEIT+ 
BEFEHL
   3590 root  20   0 1274244  16664 3144 R 99,3   0,1 
37:35.29 pound


it is not a problem for me right now as it is a small private 
server doing not much else (except sending this email) right 
now but I don't thing that is how it should be. Anyway I think 
I'll still keep Pound running (or maybe restart it) for now so 
if anyone wants to help me with my problem Pound is online and 
the problem can investigated easier.


Thanks in advance!

Emanuel Loos

Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:

Hello again,

just wanted to add that with curl this happens:

emanuel@devuan-emanuel:~$ curl
https://nc.emanuel-loos.eu/index.php/login 
<https://nc.emanuel-loos.eu/index.php/login>
curl: (92) HTTP/2 stream 0 was not closed cleanly: 
PROTOCOL_ERROR (err

1)

I left Pound running on my server so as long as there is no crash
(like when trying to connect using Firefox or Chromium but not 
lynx or
curl) it should stay online. You are welcome to test it 
yourself if it

helps.

Anyone got an idea what the problem could be or how to debug 
it further?


Thanks in advance!

Emanuel Loos






--
pound mailing list
pound@apsis.ch <mailto:pound@apsis.ch>
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch








--
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

 page with Firefox:

700 start sni /build/pound-hSCqfU/pound-3.0/src/util.c:157
7FD71E405700 start do_request 
/build/pound-hSCqfU/pound-3.0/src/http.c:257

7FD71E405700 start do_http2 /build/pound-hSCqfU/pound-3.0/src/http2.c:296
7FD71E405700 start get_be /build/pound-hSCqfU/pound-3.0/src/http.c:143
7FD724C12700 start backend_2 
/build/pound-hSCqfU/pound-3.0/src/backend.c:213
100.64.250.47 - - [Fri Aug 20 01:00:12 2021] "GET /index.php/login 
HTTP/1.1" 200 8985


Surprisingly it didn't crash this time. Looks like the crashes where 
independent from this and caused due to restarting it to fast. 
However, even though Pound says everything goes as it should it 
doesn't: Firefox reports a Network Protocol Error (see attached 
screenshots). Lynx (a command line webbrowser), however, is able to 
access the service without problems. Putting this together with the 
error curl gives I have an idea what the issue could be: I think, 
since Pound is writing about HTTP1.1 and curl is writing about HTTP2 
the HTTP versions might be somehow mixed up or wrongly identified. I 
don't know how to check and/or fix this, however.


Emanuel Loos

Am 20.08.21 um 00:01 schrieb Todd Fleisher via pound:
FWIW - right now I can connect to the public IPv4 address for 
nc.emanuel-loos.eu <http://nc.emanuel-loos.eu> 
<http://nc.emanuel-loos.eu <http://nc.emanuel-loos.eu>> 
(185.128.244.57), only the onion service @ 
http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login> 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login>> is 
responding. The public IPv4 address refuses connections.


Assuming the onion service points to the same apache2 backend and it 
actually works beyond just loading the login page, this would seem 
to point to an issue with your pound instance - maybe it is no 
longer running due to a crash or you stopped it deliberately. Once 
you verify it is running, you could also try to attach an strace to 
pound's PID to see what is happening when you make a request to it 
and/or when it is hammering your CPU like you mentioned below.


-T

P.S. Kudos to you for being aware of the power of self-hosting and 
trying to learn more about it. It feels like an overlooked concept 
with younger generations so it’s refreshing to see sentiments like yours


On Aug 19, 2021, at 13:34, Emanuel Loos via pound <mailto:pound@apsis.ch> <mailto:pound@apsis.ch 
<mailto:pound@apsis.ch>>> wrote:


Am 19.08.21 um 21:39 schrieb Emanuel Loos via pound:
If it helps: The backend is an apache2 web server with a lot of 
PHP (Nextcloud) and also available on this Tor Onion Service:


http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion> 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion>>


Thanks in advance!

Emanuel Loos

Am 19.08.21 um 21:02 schrieb Emanuel Loos via pound:

-Original Message-
From: pound <mailto:pound-boun...@apsis.ch>> On Behalf Of Emanuel Loos via pound

Sent: Thursday, August 19, 2021 10:34 AM
To: pound@apsis.ch <mailto:pound@apsis.ch>
Cc: Emanuel Loos <mailto:m...@mailing-lists.emanuel-loos.eu>>
Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and 
ERR_CONNECTION refused in Chromium but lynx works


Hello the third time,

just reporting that for some reason Pound just started using the 
full CPU power on one core:


    PID USER  PR  NI    VIRT    RES SHR S %CPU  %MEM ZEIT+ 
BEFEHL
   3590 root  20   0 1274244  16664 3144 R 99,3   0,1 
37:35.29 pound


it is not a problem for me right now as it is a small private 
server doing not much else (except sending this email) right now 
but I don't thing that is how it should be. Anyway I think I'll 
still keep Pound running (or maybe restart it) for now so if 
anyone wants to help me with my problem Pound is online and the 
problem can investigated easier.


Thanks in advance!

Emanuel Loos

Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:

Hello again,

just wanted to add that with curl this happens:

emanuel@devuan-emanuel:~$ curl
https://nc.emanuel-loos.eu/index.php/login 
<https://nc.emanuel-loos.eu/index.php/login>
curl: (92) HTTP/2 stream 0 was not closed cleanly: 
PROTOCOL_ERROR (err

1)

I left Pound running on my server so as long as there is no crash
(like when trying to connect using Firefox or Chromium but not 
lynx or
curl) it should stay online. You are welcome to test it 
yourself if it

helps.

Anyone got an idea what the problem could be or how to debug it 
further?


Thanks in advan

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Todd Fleisher via pound]

entified. I 
> don't know how to check and/or fix this, however.
> 
> Emanuel Loos
> 
> Am 20.08.21 um 00:01 schrieb Todd Fleisher via pound:
>> FWIW - right now I can connect to the public IPv4 address for 
>> nc.emanuel-loos.eu <http://nc.emanuel-loos.eu> (185.128.244.57), only the 
>> onion service @ 
>> http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login
>>  
>> <http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login>
>>  is responding. The public IPv4 address refuses connections.
>> 
>> Assuming the onion service points to the same apache2 backend and it 
>> actually works beyond just loading the login page, this would seem to point 
>> to an issue with your pound instance - maybe it is no longer running due to 
>> a crash or you stopped it deliberately. Once you verify it is running, you 
>> could also try to attach an strace to pound's PID to see what is happening 
>> when you make a request to it and/or when it is hammering your CPU like you 
>> mentioned below.
>> 
>> -T
>> 
>> P.S. Kudos to you for being aware of the power of self-hosting and trying to 
>> learn more about it. It feels like an overlooked concept with younger 
>> generations so it’s refreshing to see sentiments like yours
>> 
>>> On Aug 19, 2021, at 13:34, Emanuel Loos via pound >> <mailto:pound@apsis.ch>> wrote:
>>> 
>>> Am 19.08.21 um 21:39 schrieb Emanuel Loos via pound:
>>>> If it helps: The backend is an apache2 web server with a lot of PHP 
>>>> (Nextcloud) and also available on this Tor Onion Service:
>>>> 
>>>> http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion 
>>>> <http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion>
>>>> 
>>>> Thanks in advance!
>>>> 
>>>> Emanuel Loos
>>>> 
>>>> Am 19.08.21 um 21:02 schrieb Emanuel Loos via pound:
>>>>>> -Original Message-
>>>>>> From: pound  On Behalf Of Emanuel Loos via pound
>>>>>> Sent: Thursday, August 19, 2021 10:34 AM
>>>>>> To: pound@apsis.ch
>>>>>> Cc: Emanuel Loos 
>>>>>> Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION 
>>>>>> refused in Chromium but lynx works
>>>>>> 
>>>>>> Hello the third time,
>>>>>> 
>>>>>> just reporting that for some reason Pound just started using the full 
>>>>>> CPU power on one core:
>>>>>> 
>>>>>> PID USER  PR  NIVIRTRESSHR S %CPU  %MEM ZEIT+ BEFEHL
>>>>>>3590 root  20   0 1274244  16664   3144 R 99,3   0,1 37:35.29 
>>>>>> pound
>>>>>> 
>>>>>> it is not a problem for me right now as it is a small private server 
>>>>>> doing not much else (except sending this email) right now but I don't 
>>>>>> thing that is how it should be. Anyway I think I'll still keep Pound 
>>>>>> running (or maybe restart it) for now so if anyone wants to help me with 
>>>>>> my problem Pound is online and the problem can investigated easier.
>>>>>> 
>>>>>> Thanks in advance!
>>>>>> 
>>>>>> Emanuel Loos
>>>>>> 
>>>>>> Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:
>>>>>>> Hello again,
>>>>>>> 
>>>>>>> just wanted to add that with curl this happens:
>>>>>>> 
>>>>>>> emanuel@devuan-emanuel:~$ curl
>>>>>>> https://nc.emanuel-loos.eu/index.php/login
>>>>>>> curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err
>>>>>>> 1)
>>>>>>> 
>>>>>>> I left Pound running on my server so as long as there is no crash
>>>>>>> (like when trying to connect using Firefox or Chromium but not lynx or
>>>>>>> curl) it should stay online. You are welcome to test it yourself if it
>>>>>>> helps.
>>>>>>> 
>>>>>>> Anyone got an idea what the problem could be or how to debug it further?
>>>>>>> 
>>>>>>> Thanks in advance!
>>>>>>> 
>>>>>>> Emanuel Loos
>> 
>> 
>> 
> 
> -- 
> pound mailing list
> pound@apsis.ch
> https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch
> 

-- 
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

Thank you for the kind words!

Looks like pound really wasn't running when you checked. It should when 
and after you receive this email.


Here is what Pound writes when trying to access a page with Firefox:

700 start sni /build/pound-hSCqfU/pound-3.0/src/util.c:157
7FD71E405700 start do_request /build/pound-hSCqfU/pound-3.0/src/http.c:257
7FD71E405700 start do_http2 /build/pound-hSCqfU/pound-3.0/src/http2.c:296
7FD71E405700 start get_be /build/pound-hSCqfU/pound-3.0/src/http.c:143
7FD724C12700 start backend_2 /build/pound-hSCqfU/pound-3.0/src/backend.c:213
100.64.250.47 - - [Fri Aug 20 01:00:12 2021] "GET /index.php/login 
HTTP/1.1" 200 8985


Surprisingly it didn't crash this time. Looks like the crashes where 
independent from this and caused due to restarting it to fast. However, 
even though Pound says everything goes as it should it doesn't: Firefox 
reports a Network Protocol Error (see attached screenshots). Lynx (a 
command line webbrowser), however, is able to access the service without 
problems. Putting this together with the error curl gives I have an idea 
what the issue could be: I think, since Pound is writing about HTTP1.1 
and curl is writing about HTTP2 the HTTP versions might be somehow mixed 
up or wrongly identified. I don't know how to check and/or fix this, 
however.


Emanuel Loos

Am 20.08.21 um 00:01 schrieb Todd Fleisher via pound:
FWIW - right now I can connect to the public IPv4 address for 
nc.emanuel-loos.eu <http://nc.emanuel-loos.eu> (185.128.244.57), only 
the onion service @ 
http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login> is 
responding. The public IPv4 address refuses connections.


Assuming the onion service points to the same apache2 backend and it 
actually works beyond just loading the login page, this would seem to 
point to an issue with your pound instance - maybe it is no longer 
running due to a crash or you stopped it deliberately. Once you verify 
it is running, you could also try to attach an strace to pound's PID 
to see what is happening when you make a request to it and/or when it 
is hammering your CPU like you mentioned below.


-T

P.S. Kudos to you for being aware of the power of self-hosting and 
trying to learn more about it. It feels like an overlooked concept 
with younger generations so it’s refreshing to see sentiments like yours


On Aug 19, 2021, at 13:34, Emanuel Loos via pound <mailto:pound@apsis.ch>> wrote:


Am 19.08.21 um 21:39 schrieb Emanuel Loos via pound:
If it helps: The backend is an apache2 web server with a lot of PHP 
(Nextcloud) and also available on this Tor Onion Service:


http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion>


Thanks in advance!

Emanuel Loos

Am 19.08.21 um 21:02 schrieb Emanuel Loos via pound:

-Original Message-
From: pound  On Behalf Of Emanuel Loos via 
pound

Sent: Thursday, August 19, 2021 10:34 AM
To: pound@apsis.ch
Cc: Emanuel Loos 
Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and 
ERR_CONNECTION refused in Chromium but lynx works


Hello the third time,

just reporting that for some reason Pound just started using the 
full CPU power on one core:


    PID USER  PR  NI    VIRT    RES    SHR S %CPU  %MEM ZEIT+ 
BEFEHL
   3590 root  20   0 1274244  16664   3144 R 99,3   0,1 
37:35.29 pound


it is not a problem for me right now as it is a small private 
server doing not much else (except sending this email) right now 
but I don't thing that is how it should be. Anyway I think I'll 
still keep Pound running (or maybe restart it) for now so if 
anyone wants to help me with my problem Pound is online and the 
problem can investigated easier.


Thanks in advance!

Emanuel Loos

Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:

Hello again,

just wanted to add that with curl this happens:

emanuel@devuan-emanuel:~$ curl
https://nc.emanuel-loos.eu/index.php/login
curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR 
(err

1)

I left Pound running on my server so as long as there is no crash
(like when trying to connect using Firefox or Chromium but not 
lynx or
curl) it should stay online. You are welcome to test it yourself 
if it

helps.

Anyone got an idea what the problem could be or how to debug it 
further?


Thanks in advance!

Emanuel Loos






--
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Todd Fleisher via pound]

FWIW - right now I can connect to the public IPv4 address for 
nc.emanuel-loos.eu <http://nc.emanuel-loos.eu/> (185.128.244.57), only the 
onion service @ 
http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login
 
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login>
 is responding. The public IPv4 address refuses connections.

Assuming the onion service points to the same apache2 backend and it actually 
works beyond just loading the login page, this would seem to point to an issue 
with your pound instance - maybe it is no longer running due to a crash or you 
stopped it deliberately. Once you verify it is running, you could also try to 
attach an strace to pound's PID to see what is happening when you make a 
request to it and/or when it is hammering your CPU like you mentioned below.

-T

P.S. Kudos to you for being aware of the power of self-hosting and trying to 
learn more about it. It feels like an overlooked concept with younger 
generations so it’s refreshing to see sentiments like yours

> On Aug 19, 2021, at 13:34, Emanuel Loos via pound  wrote:
> 
> Am 19.08.21 um 21:39 schrieb Emanuel Loos via pound:
>> If it helps: The backend is an apache2 web server with a lot of PHP 
>> (Nextcloud) and also available on this Tor Onion Service:
>> 
>> http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion
>> 
>> Thanks in advance!
>> 
>> Emanuel Loos
>> 
>> Am 19.08.21 um 21:02 schrieb Emanuel Loos via pound:
>>>> -Original Message-
>>>> From: pound  On Behalf Of Emanuel Loos via pound
>>>> Sent: Thursday, August 19, 2021 10:34 AM
>>>> To: pound@apsis.ch
>>>> Cc: Emanuel Loos 
>>>> Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION 
>>>> refused in Chromium but lynx works
>>>> 
>>>> Hello the third time,
>>>> 
>>>> just reporting that for some reason Pound just started using the full CPU 
>>>> power on one core:
>>>> 
>>>> PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM ZEIT+ BEFEHL
>>>>3590 root  20   0 1274244  16664   3144 R  99,3   0,1 37:35.29 pound
>>>> 
>>>> it is not a problem for me right now as it is a small private server doing 
>>>> not much else (except sending this email) right now but I don't thing that 
>>>> is how it should be. Anyway I think I'll still keep Pound running (or 
>>>> maybe restart it) for now so if anyone wants to help me with my problem 
>>>> Pound is online and the problem can investigated easier.
>>>> 
>>>> Thanks in advance!
>>>> 
>>>> Emanuel Loos
>>>> 
>>>> Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:
>>>>> Hello again,
>>>>> 
>>>>> just wanted to add that with curl this happens:
>>>>> 
>>>>> emanuel@devuan-emanuel:~$ curl
>>>>> https://nc.emanuel-loos.eu/index.php/login
>>>>> curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err
>>>>> 1)
>>>>> 
>>>>> I left Pound running on my server so as long as there is no crash
>>>>> (like when trying to connect using Firefox or Chromium but not lynx or
>>>>> curl) it should stay online. You are welcome to test it yourself if it
>>>>> helps.
>>>>> 
>>>>> Anyone got an idea what the problem could be or how to debug it further?
>>>>> 
>>>>> Thanks in advance!
>>>>> 
>>>>> Emanuel Loos


-- 
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

Sorry for writing so many emails, I just saw I didn't answer if I am a 
programmer. I can write quite simple programs in C++ or Python that read 
from stdin, calculate something or something a bit more complex and 
forward it to stdout, but I am not sure that is what you meant as I 
normally don't really understand what is going on when I try to 
understand the code of a bigger "real" computer program. I managed to 
compile a patched Linux kernel for Linux-VServer (which I use for 
containers on my server), cross-compile a Linux kernel with more 
encryption algorithms enabled and compiled this and that (Hiawatha, 
ffmpeg, ...). However mostly there was some guide on the web, some 
manpage or something else explaining how to do this and that. I think I 
do know the Debian GNU/Linux command line quite well though and can also 
write simple bash scripts. However, in no way am I a professional 
programmer. I am actually only 15 years old but was always quite 
interested in informatics and to be more independent from the giant tech 
companies I am hosting my own email server, instant messaging (Matrix) 
server, pastebin and cloud (looking forward to more: some sourch code 
management system [GitLab, Gitea, Kallithea, ...] to self-host source 
code, ...). The last two are currently only accessible through their 
onion services because I decided to switch from using Hiawatha (a quite 
unknown webserver) as my reverse proxy to Pound (because Pound is only a 
reverse proxy and nothing else and because Hiawatha is not developed 
much further except for bugfixes, supports only http1 and I had some 
problem with it that caused the cloud to load forever with no reason 
except wrong configuration or a bug which was quite uncomfortable) and 
am having this problem now. (Hiawatha had quite some DDoS protection 
features though, maybe you would like to implement something like that 
in Pound too?)


Emanuel Loos

Am 19.08.21 um 21:39 schrieb Emanuel Loos via pound:
If it helps: The backend is an apache2 web server with a lot of PHP 
(Nextcloud) and also available on this Tor Onion Service:


http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion

Thanks in advance!

Emanuel Loos

Am 19.08.21 um 21:02 schrieb Emanuel Loos via pound:

Thank you for responding!

I don't think it is a version with debug symbols. I am running the 
Devuan (fork of Debian without systemd) package from the official 
Devuan 4 chimaera (=Debian 11 bullseye without systemd) as I have 
mentioned earlier (apt info pound). I guess I should get and run a 
version with debug symbols then?


Reading symbols from /usr/sbin/pound...
(No debugging symbols found in /usr/sbin/pound)
Attaching to program: /usr/sbin/pound, process 20292
[New LWP 20293]
[New LWP 20294]
[New LWP 20295]
[New LWP 20296]
[New LWP 20297]
[New LWP 20298]
[New LWP 20299]
[New LWP 20300]
[New LWP 20301]
[New LWP 20302]
[New LWP 20303]
[New LWP 20304]
[New LWP 20305]
[New LWP 20306]
[New LWP 20307]
[New LWP 20308]
[New LWP 20309]
[New LWP 20310]
[New LWP 20311]
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".

--Type  for more, q to quit, c to continue without paging--

The PID is different now because I restarted pound.

Thanks in advance!

Emanuel Loos

Am 19.08.21 um 20:19 schrieb jwa--- via pound:
Are you running a build of pound with debug symbols? If so, fire up 
gdb and attach it to the pound process and see where it is 
processing. That should give you a good place to start your diagnosis.


If you're not a programmer, then try this:


gdb /path/to/pound 3590

Using PID 3590 from your example below.

"To stop your program while it is running, type "(ctrl) + c" (hold 
down the ctrl key and press c)."

https://web.eecs.umich.edu/~sugih/pointers/gdbQS.html

Now you should have an interruption in the pound exe, you can list 
and get a call stack. If you have the path/to/exe and the source, 
then you should be able to get actual C code listings of where the 
break occurred.


-- jake

-Original Message-
From: pound  On Behalf Of Emanuel Loos via 
pound

Sent: Thursday, August 19, 2021 10:34 AM
To: pound@apsis.ch
Cc: Emanuel Loos 
Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and 
ERR_CONNECTION refused in Chromium but lynx works


Hello the third time,

just reporting that for some reason Pound just started using the 
full CPU power on one core:


    PID USER  PR  NI    VIRT    RES    SHR S  %CPU  %MEM ZEIT+ 
BEFEHL
   3590 root  20   0 1274244  16664   3144 R  99,3   0,1 
37:35.29 pound


it is not a problem for me right now as it is a small private server 
doing not much else (except sending this email) right now but I 
don't thing that is how it should be. Anyway I think I'll still keep 
Pound running (or maybe restart it) for now so if anyone wants to 
help me with my problem Pound is online and the pr

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

If it helps: The backend is an apache2 web server with a lot of PHP 
(Nextcloud) and also available on this Tor Onion Service:


http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion

Thanks in advance!

Emanuel Loos

Am 19.08.21 um 21:02 schrieb Emanuel Loos via pound:

Thank you for responding!

I don't think it is a version with debug symbols. I am running the 
Devuan (fork of Debian without systemd) package from the official 
Devuan 4 chimaera (=Debian 11 bullseye without systemd) as I have 
mentioned earlier (apt info pound). I guess I should get and run a 
version with debug symbols then?


Reading symbols from /usr/sbin/pound...
(No debugging symbols found in /usr/sbin/pound)
Attaching to program: /usr/sbin/pound, process 20292
[New LWP 20293]
[New LWP 20294]
[New LWP 20295]
[New LWP 20296]
[New LWP 20297]
[New LWP 20298]
[New LWP 20299]
[New LWP 20300]
[New LWP 20301]
[New LWP 20302]
[New LWP 20303]
[New LWP 20304]
[New LWP 20305]
[New LWP 20306]
[New LWP 20307]
[New LWP 20308]
[New LWP 20309]
[New LWP 20310]
[New LWP 20311]
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".

--Type  for more, q to quit, c to continue without paging--

The PID is different now because I restarted pound.

Thanks in advance!

Emanuel Loos

Am 19.08.21 um 20:19 schrieb jwa--- via pound:
Are you running a build of pound with debug symbols? If so, fire up 
gdb and attach it to the pound process and see where it is 
processing. That should give you a good place to start your diagnosis.


If you're not a programmer, then try this:


gdb /path/to/pound 3590

Using PID 3590 from your example below.

"To stop your program while it is running, type "(ctrl) + c" (hold 
down the ctrl key and press c)."

https://web.eecs.umich.edu/~sugih/pointers/gdbQS.html

Now you should have an interruption in the pound exe, you can list 
and get a call stack. If you have the path/to/exe and the source, 
then you should be able to get actual C code listings of where the 
break occurred.


-- jake

-Original Message-
From: pound  On Behalf Of Emanuel Loos via pound
Sent: Thursday, August 19, 2021 10:34 AM
To: pound@apsis.ch
Cc: Emanuel Loos 
Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and 
ERR_CONNECTION refused in Chromium but lynx works


Hello the third time,

just reporting that for some reason Pound just started using the full 
CPU power on one core:


    PID USER  PR  NI    VIRT    RES    SHR S  %CPU  %MEM ZEIT+ 
BEFEHL
   3590 root  20   0 1274244  16664   3144 R  99,3   0,1 37:35.29 
pound


it is not a problem for me right now as it is a small private server 
doing not much else (except sending this email) right now but I don't 
thing that is how it should be. Anyway I think I'll still keep Pound 
running (or maybe restart it) for now so if anyone wants to help me 
with my problem Pound is online and the problem can investigated easier.


Thanks in advance!

Emanuel Loos

Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:

Hello again,

just wanted to add that with curl this happens:

emanuel@devuan-emanuel:~$ curl
https://nc.emanuel-loos.eu/index.php/login
curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err
1)

I left Pound running on my server so as long as there is no crash
(like when trying to connect using Firefox or Chromium but not lynx or
curl) it should stay online. You are welcome to test it yourself if it
helps.

Anyone got an idea what the problem could be or how to debug it 
further?


Thanks in advance!

Emanuel Loos

Am 17.08.21 um 19:15 schrieb Emanuel Loos via pound:

I am trying to use Pound as a reverse proxy on my server to serve
multiple online services available on server intern local IP
addresses through http on their different domains through https using
only one public IP address.

My configuration:

   Global:
 User: "root"
 Group: "root"
   Backends:
   - &nextcloud
   Address: 10.10.2.2
   Port: 80

   HTTPListeners:

   HTTPSListeners:
   -   Address: 185.128.244.57
   Port: 443
   Services:
   -   HeadRequire: "Host: nc.emanuel-loos.eu"
   Backends:
   - *nextcloud
   Certificates:
"/etc/letsencrypt/live/emanuel-loos.eu/fullchain-and-privkey.pem"
   Client: 60
   Ciphers:
   - TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384
   - TLS-DHE-RSA-WITH-3DES-EDE-CBC-SHA
   - TLS-DHE-RSA-WITH-AES-128-CBC-SHA
   - TLS-RSA-WITH-CAMELLIA-128-CBC-SHA

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

Thank you for responding!

I don't think it is a version with debug symbols. I am running the 
Devuan (fork of Debian without systemd) package from the official Devuan 
4 chimaera (=Debian 11 bullseye without systemd) as I have mentioned 
earlier (apt info pound). I guess I should get and run a version with 
debug symbols then?


Reading symbols from /usr/sbin/pound...
(No debugging symbols found in /usr/sbin/pound)
Attaching to program: /usr/sbin/pound, process 20292
[New LWP 20293]
[New LWP 20294]
[New LWP 20295]
[New LWP 20296]
[New LWP 20297]
[New LWP 20298]
[New LWP 20299]
[New LWP 20300]
[New LWP 20301]
[New LWP 20302]
[New LWP 20303]
[New LWP 20304]
[New LWP 20305]
[New LWP 20306]
[New LWP 20307]
[New LWP 20308]
[New LWP 20309]
[New LWP 20310]
[New LWP 20311]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type  for more, q to quit, c to continue without paging--

The PID is different now because I restarted pound.

Thanks in advance!

Emanuel Loos

Am 19.08.21 um 20:19 schrieb jwa--- via pound:

Are you running a build of pound with debug symbols? If so, fire up gdb and 
attach it to the pound process and see where it is processing. That should give 
you a good place to start your diagnosis.

If you're not a programmer, then try this:


gdb /path/to/pound 3590

Using PID 3590 from your example below.

"To stop your program while it is running, type "(ctrl) + c" (hold down the ctrl key 
and press c)."
https://web.eecs.umich.edu/~sugih/pointers/gdbQS.html

Now you should have an interruption in the pound exe, you can list and get a 
call stack. If you have the path/to/exe and the source, then you should be able 
to get actual C code listings of where the break occurred.

-- jake

-Original Message-
From: pound  On Behalf Of Emanuel Loos via pound
Sent: Thursday, August 19, 2021 10:34 AM
To: pound@apsis.ch
Cc: Emanuel Loos 
Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused 
in Chromium but lynx works

Hello the third time,

just reporting that for some reason Pound just started using the full CPU power 
on one core:

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM ZEIT+ BEFEHL
   3590 root  20   0 1274244  16664   3144 R  99,3   0,1 37:35.29 pound

it is not a problem for me right now as it is a small private server doing not 
much else (except sending this email) right now but I don't thing that is how 
it should be. Anyway I think I'll still keep Pound running (or maybe restart 
it) for now so if anyone wants to help me with my problem Pound is online and 
the problem can investigated easier.

Thanks in advance!

Emanuel Loos

Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:

Hello again,

just wanted to add that with curl this happens:

emanuel@devuan-emanuel:~$ curl
https://nc.emanuel-loos.eu/index.php/login
curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err
1)

I left Pound running on my server so as long as there is no crash
(like when trying to connect using Firefox or Chromium but not lynx or
curl) it should stay online. You are welcome to test it yourself if it
helps.

Anyone got an idea what the problem could be or how to debug it further?

Thanks in advance!

Emanuel Loos

Am 17.08.21 um 19:15 schrieb Emanuel Loos via pound:

I am trying to use Pound as a reverse proxy on my server to serve
multiple online services available on server intern local IP
addresses through http on their different domains through https using
only one public IP address.

My configuration:

   Global:
 User: "root"
 Group: "root"
   Backends:
   - &nextcloud
   Address: 10.10.2.2
   Port: 80

   HTTPListeners:

   HTTPSListeners:
   -   Address: 185.128.244.57
   Port: 443
   Services:
   -   HeadRequire: "Host: nc.emanuel-loos.eu"
   Backends:
   - *nextcloud
   Certificates:
"/etc/letsencrypt/live/emanuel-loos.eu/fullchain-and-privkey.pem"
   Client: 60
   Ciphers:
   - TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384
   - TLS-DHE-RSA-WITH-3DES-EDE-CBC-SHA
   - TLS-DHE-RSA-WITH-AES-128-CBC-SHA
   - TLS-RSA-WITH-CAMELLIA-128-CBC-SHA
   - TLS-RSA-WITH-AES-128-CCM
   - TLS-RSA-WITH-AES-256-GCM-SHA384
   - TLS-RSA-WITH-RC4-128-MD5
   - TLS-RSA-WITH-3DES-EDE-CBC-SHA


However when trying to connect Firefox throws a PR_END_OF_FILE_ERROR
and Pound crashes wi

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[jwa--- via pound]

Are you running a build of pound with debug symbols? If so, fire up gdb and 
attach it to the pound process and see where it is processing. That should give 
you a good place to start your diagnosis.

If you're not a programmer, then try this:

> gdb /path/to/pound 3590

Using PID 3590 from your example below.

"To stop your program while it is running, type "(ctrl) + c" (hold down the 
ctrl key and press c)."
https://web.eecs.umich.edu/~sugih/pointers/gdbQS.html

Now you should have an interruption in the pound exe, you can list and get a 
call stack. If you have the path/to/exe and the source, then you should be able 
to get actual C code listings of where the break occurred. 

-- jake

-Original Message-
From: pound  On Behalf Of Emanuel Loos via pound
Sent: Thursday, August 19, 2021 10:34 AM
To: pound@apsis.ch
Cc: Emanuel Loos 
Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused 
in Chromium but lynx works

Hello the third time,

just reporting that for some reason Pound just started using the full CPU power 
on one core:

   PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM ZEIT+ BEFEHL
  3590 root  20   0 1274244  16664   3144 R  99,3   0,1 37:35.29 pound

it is not a problem for me right now as it is a small private server doing not 
much else (except sending this email) right now but I don't thing that is how 
it should be. Anyway I think I'll still keep Pound running (or maybe restart 
it) for now so if anyone wants to help me with my problem Pound is online and 
the problem can investigated easier.

Thanks in advance!

Emanuel Loos

Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:
> Hello again,
>
> just wanted to add that with curl this happens:
>
> emanuel@devuan-emanuel:~$ curl 
> https://nc.emanuel-loos.eu/index.php/login
> curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 
> 1)
>
> I left Pound running on my server so as long as there is no crash 
> (like when trying to connect using Firefox or Chromium but not lynx or
> curl) it should stay online. You are welcome to test it yourself if it 
> helps.
>
> Anyone got an idea what the problem could be or how to debug it further?
>
> Thanks in advance!
>
> Emanuel Loos
>
> Am 17.08.21 um 19:15 schrieb Emanuel Loos via pound:
>> I am trying to use Pound as a reverse proxy on my server to serve 
>> multiple online services available on server intern local IP 
>> addresses through http on their different domains through https using 
>> only one public IP address.
>>
>> My configuration:
>>
>>   Global:
>> User: "root"
>> Group: "root"
>>   Backends:
>>   - &nextcloud
>>   Address: 10.10.2.2
>>   Port: 80
>>
>>   HTTPListeners:
>>
>>   HTTPSListeners:
>>   -   Address: 185.128.244.57
>>   Port: 443
>>   Services:
>>   -   HeadRequire: "Host: nc.emanuel-loos.eu"
>>   Backends:
>>   - *nextcloud
>>   Certificates: 
>> "/etc/letsencrypt/live/emanuel-loos.eu/fullchain-and-privkey.pem"
>>   Client: 60
>>   Ciphers:
>>   - TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384
>>   - TLS-DHE-RSA-WITH-3DES-EDE-CBC-SHA
>>   - TLS-DHE-RSA-WITH-AES-128-CBC-SHA
>>   - TLS-RSA-WITH-CAMELLIA-128-CBC-SHA
>>   - TLS-RSA-WITH-AES-128-CCM
>>   - TLS-RSA-WITH-AES-256-GCM-SHA384
>>   - TLS-RSA-WITH-RC4-128-MD5
>>   - TLS-RSA-WITH-3DES-EDE-CBC-SHA
>>
>>
>> However when trying to connect Firefox throws a PR_END_OF_FILE_ERROR 
>> and Pound crashes with a storage access error. However when I try to 
>> connect using lynx it works perfectly.
>>
>>
>> root@Server:~# pound -d 1
>> start get_others /build/pound-hSCqfU/pound-3.0/src/config.c:564
>> start get_global /build/pound-hSCqfU/pound-3.0/src/config.c:74
>> start get_backends /build/pound-hSCqfU/pound-3.0/src/config.c:123
>> start get_https /build/pound-hSCqfU/pound-3.0/src/config.c:489
>> start get_services /build/pound-hSCqfU/pound-3.0/src/config.c:209
>> start get_certificates /build/pound-hSCqfU/pound-3.0/src/config.c:451
>> start
>> get_one(/etc/letsencrypt/live/emanuel-loos.eu/fullchai

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

Hello the third time,

just reporting that for some reason Pound just started using the full 
CPU power on one core:


  PID USER  PR  NI    VIRT    RES    SHR S  %CPU  %MEM ZEIT+ BEFEHL
 3590 root  20   0 1274244  16664   3144 R  99,3   0,1 37:35.29 pound

it is not a problem for me right now as it is a small private server 
doing not much else (except sending this email) right now but I don't 
thing that is how it should be. Anyway I think I'll still keep Pound 
running (or maybe restart it) for now so if anyone wants to help me with 
my problem Pound is online and the problem can investigated easier.


Thanks in advance!

Emanuel Loos

Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:

Hello again,

just wanted to add that with curl this happens:

emanuel@devuan-emanuel:~$ curl https://nc.emanuel-loos.eu/index.php/login
curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

I left Pound running on my server so as long as there is no crash 
(like when trying to connect using Firefox or Chromium but not lynx or 
curl) it should stay online. You are welcome to test it yourself if it 
helps.


Anyone got an idea what the problem could be or how to debug it further?

Thanks in advance!

Emanuel Loos

Am 17.08.21 um 19:15 schrieb Emanuel Loos via pound:
I am trying to use Pound as a reverse proxy on my server to serve 
multiple online services available on server intern local IP 
addresses through http on their different domains through https using 
only one public IP address.


My configuration:

  Global:
    User: "root"
    Group: "root"
  Backends:
  - &nextcloud
  Address: 10.10.2.2
  Port: 80

  HTTPListeners:

  HTTPSListeners:
  -   Address: 185.128.244.57
  Port: 443
  Services:
  -   HeadRequire: "Host: nc.emanuel-loos.eu"
  Backends:
  - *nextcloud
  Certificates: 
"/etc/letsencrypt/live/emanuel-loos.eu/fullchain-and-privkey.pem"

  Client: 60
  Ciphers:
  - TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384
  - TLS-DHE-RSA-WITH-3DES-EDE-CBC-SHA
  - TLS-DHE-RSA-WITH-AES-128-CBC-SHA
  - TLS-RSA-WITH-CAMELLIA-128-CBC-SHA
  - TLS-RSA-WITH-AES-128-CCM
  - TLS-RSA-WITH-AES-256-GCM-SHA384
  - TLS-RSA-WITH-RC4-128-MD5
  - TLS-RSA-WITH-3DES-EDE-CBC-SHA


However when trying to connect Firefox throws a PR_END_OF_FILE_ERROR 
and Pound crashes with a storage access error. However when I try to 
connect using lynx it works perfectly.



root@Server:~# pound -d 1
start get_others /build/pound-hSCqfU/pound-3.0/src/config.c:564
start get_global /build/pound-hSCqfU/pound-3.0/src/config.c:74
start get_backends /build/pound-hSCqfU/pound-3.0/src/config.c:123
start get_https /build/pound-hSCqfU/pound-3.0/src/config.c:489
start get_services /build/pound-hSCqfU/pound-3.0/src/config.c:209
start get_certificates /build/pound-hSCqfU/pound-3.0/src/config.c:451
start 
get_one(/etc/letsencrypt/live/emanuel-loos.eu/fullchain-and-privkey.pem) 
/build/pound-hSCqfU/pound-3.0/src/config.c:376

start get_ciphers /build/pound-hSCqfU/pound-3.0/src/config.c:334
Starting resurrector thread /build/pound-hSCqfU/pound-3.0/src/util.c:80
7F445B27F700 start service /build/pound-hSCqfU/pound-3.0/src/http.c:45
7F445AA7E700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F445A27D700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4459A7C700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4458279700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4458A7A700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4457A78700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4457277700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F445927B700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4457277700 start sni /build/pound-hSCqfU/pound-3.0/src/util.c:157
Speicherzugriffsfehler


root@Server:~# apt info pound
Package: pound
Version: 3.0-2
Priority: optional
Section: net
Maintainer: Carsten Leonhardt 
Installed-Size: 156 kB
Pre-Depends: init-system-helpers (>= 1.54~)
Depends: lsb-base, sysuser-helper (<< 1.4), libc6 (>= 2.25), 
libmbedcrypto3 (>= 2.13), libmbedtls12 (>= 2.13), libmbedx509-0 (>= 
2.0), libnanomsg5 (>= 1.1.5), libpcre3, libyaml-0-2

Homepage: https://www.apsis.ch/pound.html
Tag: interface::daemon, network::load-balancing, network::server,
 protocol::http, protocol::ssl, role::program, use::proxying,
 web::server
Download-Size: 62,6 kB
APT-Manual-Installed: yes
APT-Sources: http://deb.devuan.org/mer

Re: [pound] PR_END_OF_FILE_ERROR in Firefox and ERR_CONNECTION refused in Chromium but lynx works

[Emanuel Loos via pound]

Hello again,

just wanted to add that with curl this happens:

emanuel@devuan-emanuel:~$ curl https://nc.emanuel-loos.eu/index.php/login
curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

I left Pound running on my server so as long as there is no crash (like 
when trying to connect using Firefox or Chromium but not lynx or curl) 
it should stay online. You are welcome to test it yourself if it helps.


Anyone got an idea what the problem could be or how to debug it further?

Thanks in advance!

Emanuel Loos

Am 17.08.21 um 19:15 schrieb Emanuel Loos via pound:
I am trying to use Pound as a reverse proxy on my server to serve 
multiple online services available on server intern local IP addresses 
through http on their different domains through https using only one 
public IP address.


My configuration:

  Global:
    User: "root"
    Group: "root"
  Backends:
  - &nextcloud
  Address: 10.10.2.2
  Port: 80

  HTTPListeners:

  HTTPSListeners:
  -   Address: 185.128.244.57
  Port: 443
  Services:
  -   HeadRequire: "Host: nc.emanuel-loos.eu"
  Backends:
  - *nextcloud
  Certificates: 
"/etc/letsencrypt/live/emanuel-loos.eu/fullchain-and-privkey.pem"

  Client: 60
  Ciphers:
  - TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384
  - TLS-DHE-RSA-WITH-3DES-EDE-CBC-SHA
  - TLS-DHE-RSA-WITH-AES-128-CBC-SHA
  - TLS-RSA-WITH-CAMELLIA-128-CBC-SHA
  - TLS-RSA-WITH-AES-128-CCM
  - TLS-RSA-WITH-AES-256-GCM-SHA384
  - TLS-RSA-WITH-RC4-128-MD5
  - TLS-RSA-WITH-3DES-EDE-CBC-SHA


However when trying to connect Firefox throws a PR_END_OF_FILE_ERROR 
and Pound crashes with a storage access error. However when I try to 
connect using lynx it works perfectly.



root@Server:~# pound -d 1
start get_others /build/pound-hSCqfU/pound-3.0/src/config.c:564
start get_global /build/pound-hSCqfU/pound-3.0/src/config.c:74
start get_backends /build/pound-hSCqfU/pound-3.0/src/config.c:123
start get_https /build/pound-hSCqfU/pound-3.0/src/config.c:489
start get_services /build/pound-hSCqfU/pound-3.0/src/config.c:209
start get_certificates /build/pound-hSCqfU/pound-3.0/src/config.c:451
start 
get_one(/etc/letsencrypt/live/emanuel-loos.eu/fullchain-and-privkey.pem) 
/build/pound-hSCqfU/pound-3.0/src/config.c:376

start get_ciphers /build/pound-hSCqfU/pound-3.0/src/config.c:334
Starting resurrector thread /build/pound-hSCqfU/pound-3.0/src/util.c:80
7F445B27F700 start service /build/pound-hSCqfU/pound-3.0/src/http.c:45
7F445AA7E700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F445A27D700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4459A7C700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4458279700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4458A7A700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4457A78700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4457277700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F445927B700 thr_http start /build/pound-hSCqfU/pound-3.0/src/http.c:535
7F4457277700 start sni /build/pound-hSCqfU/pound-3.0/src/util.c:157
Speicherzugriffsfehler


root@Server:~# apt info pound
Package: pound
Version: 3.0-2
Priority: optional
Section: net
Maintainer: Carsten Leonhardt 
Installed-Size: 156 kB
Pre-Depends: init-system-helpers (>= 1.54~)
Depends: lsb-base, sysuser-helper (<< 1.4), libc6 (>= 2.25), 
libmbedcrypto3 (>= 2.13), libmbedtls12 (>= 2.13), libmbedx509-0 (>= 
2.0), libnanomsg5 (>= 1.1.5), libpcre3, libyaml-0-2

Homepage: https://www.apsis.ch/pound.html
Tag: interface::daemon, network::load-balancing, network::server,
 protocol::http, protocol::ssl, role::program, use::proxying,
 web::server
Download-Size: 62,6 kB
APT-Manual-Installed: yes
APT-Sources: http://deb.devuan.org/merged chimaera/main amd64 Packages


Thank you very much in advance!

Emanuel Loos




--
pound mailing list
pound@apsis.ch
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch