Problem with https and WS_URL

List overview All Threads
Download

newer

older

Configuring Site and domain for...

Sometime we met the problem blow...

Philippe Mazet (OSS)

20 Nov 2020 20 Nov '20

4:27 a.m.

Hello,

While testing 2020.10 with https enabled, we have noticed the following problem: In /etc/lava-dispatcher/lava-worker, if we set WS_URL="--ws-url http://<master's address>/ws/" (or do not this variable at all), we get the following error on worker:

2020-11-19 15:14:57,751 INFO PING => server SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7f9a0d704160> transport: <_SelectorSocketTransport fd=8 read=polling write=<idle, bufsize=0>> Traceback (most recent call last): File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received ssldata, appdata = self._sslpipe.feed_ssldata(data) File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.7/ssl.py", line 767, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

Still, even with those errors the worker is fully functional.

Now, the only way to get rid of such errors is to explicitly specify the port, 8001: WS_URL="--ws-url http://<master's address>:8001/ws/"

Have you experienced similar problems? Did we miss something on our setup?

Thanks a lot,

Philippe

Show replies by date

Remi Duraffort

20 Nov 20 Nov

10:20 p.m.

New subject: [Lava-users] Problem with https and WS_URL

Hello,

have you tried to set WS_URL to "https://" and not "http://" ?

Le jeu. 19 nov. 2020 à 16:27, Philippe Mazet (OSS) < philippe.mazet@oss.nxp.com> a écrit :

...

Hello,

While testing 2020.10 with https enabled, we have noticed the following problem: In /etc/lava-dispatcher/lava-worker, if we set WS_URL="--ws-url http://<master's address>/ws/" (or do not this variable at all), we get the following error on worker:

2020-11-19 15:14:57,751 INFO PING => server SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7f9a0d704160> transport: <_SelectorSocketTransport fd=8 read=polling write=<idle, bufsize=0>> Traceback (most recent call last): File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received ssldata, appdata = self._sslpipe.feed_ssldata(data) File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.7/ssl.py", line 767, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

Still, even with those errors the worker is fully functional.

Now, the only way to get rid of such errors is to explicitly specify the port, 8001: WS_URL="--ws-url http://<master's address>:8001/ws/"

Have you experienced similar problems? Did we miss something on our setup?

Thanks a lot,

Philippe

Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

-- Rémi Duraffort LAVA Architect Linaro

Philippe Mazet (OSS)

11:05 p.m.

New subject: [Lava-users] Problem with https and WS_URL

Yes. Actually this is just in the example below that I forgot the “s” in https. I do have the problem with https in WS_URL.

From: Remi Duraffort remi.duraffort@linaro.org Sent: Friday, November 20, 2020 10:20 AM To: Philippe Mazet (OSS) philippe.mazet@oss.nxp.com Cc: lava-users@lists.lavasoftware.org lava-users@lavasoftware.org Subject: Re: [Lava-users] Problem with https and WS_URL

Hello,

have you tried to set WS_URL to "https://" and not "http://" ?

Le jeu. 19 nov. 2020 à 16:27, Philippe Mazet (OSS) <philippe.mazet@oss.nxp.commailto:philippe.mazet@oss.nxp.com> a écrit : Hello,

While testing 2020.10 with https enabled, we have noticed the following problem: In /etc/lava-dispatcher/lava-worker, if we set WS_URL="--ws-url http://<master'shttp://%3cmaster's address>/ws/" (or do not this variable at all), we get the following error on worker:

Still, even with those errors the worker is fully functional.

Now, the only way to get rid of such errors is to explicitly specify the port, 8001: WS_URL="--ws-url http://<master'shttp://%3cmaster's address>:8001/ws/"

Have you experienced similar problems? Did we miss something on our setup?

Thanks a lot,

Philippe

_______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.orgmailto:Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

-- Rémi Duraffort LAVA Architect Linaro

Remi Duraffort

24 Nov 24 Nov

5:39 a.m.

New subject: [Lava-users] Problem with https and WS_URL

That's really strange because this setup ha been tested with https://master.lavasoftware.org for a long time.

You can connect to the even stream using websocket over https and the apache config is the default lava one.

Le ven. 20 nov. 2020 à 11:05, Philippe Mazet (OSS) < philippe.mazet@oss.nxp.com> a écrit :

...

Yes. Actually this is just in the example below that I forgot the “s” in https.

I do have the problem with https in WS_URL.

*From:* Remi Duraffort remi.duraffort@linaro.org *Sent:* Friday, November 20, 2020 10:20 AM *To:* Philippe Mazet (OSS) philippe.mazet@oss.nxp.com *Cc:* lava-users@lists.lavasoftware.org lava-users@lavasoftware.org *Subject:* Re: [Lava-users] Problem with https and WS_URL

Hello,

have you tried to set WS_URL to "https://" and not "http://" ?

Le jeu. 19 nov. 2020 à 16:27, Philippe Mazet (OSS) < philippe.mazet@oss.nxp.com> a écrit :

Hello,

While testing 2020.10 with https enabled, we have noticed the following problem: In /etc/lava-dispatcher/lava-worker, if we set WS_URL="--ws-url http://<master's address>/ws/" (or do not this variable at all), we get the following error on worker:

2020-11-19 15:14:57,751 INFO PING => server SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7f9a0d704160> transport: <_SelectorSocketTransport fd=8 read=polling write=<idle, bufsize=0>> Traceback (most recent call last): File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received ssldata, appdata = self._sslpipe.feed_ssldata(data) File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.7/ssl.py", line 767, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

Still, even with those errors the worker is fully functional.

Now, the only way to get rid of such errors is to explicitly specify the port, 8001: WS_URL="--ws-url http://<master's address>:8001/ws/"

Have you experienced similar problems? Did we miss something on our setup?

Thanks a lot,

Philippe

Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

--

Rémi Duraffort

LAVA Architect

Linaro

-- Rémi Duraffort LAVA Architect Linaro

LABBE Corentin

12 Feb 12 Feb

10:09 p.m.

New subject: [Lava-users] Problem with https and WS_URL

Hello

I hit the same issue. I use a first reverseproxy for handling TLS which proxypass to the "default LAVA apache proxy".

I fixed this issue by adding the "ws proxypass" in my first reverse proxy (the 2 lines below): ProxyPass /ws/ ws://127.0.0.1:10080/ws/ ProxyPassReverse /ws/ ws://127.0.0.1:10080/ws/ # my original Proxy lines ProxyPass / http://127.0.0.1:10080/ ProxyPassReverse / http://127.0.0.1:10080/

Regards

1408

days inactive

1493

days old

lava-users@lists.lavasoftware.org

4 comments

participants

tags (0)

participants (3)

LABBE Corentin
Philippe Mazet (OSS)
Remi Duraffort