locust: gevent error when locust server started and browse the website

Describe the bug

When I started the locust server then I browse the website, the log is:

python -m locust
[2019-11-13 00:24:30,516] SQZ777/INFO/locust.main: Starting web monitor at *:8089
[2019-11-13 00:24:30,517] SQZ777/INFO/locust.main: Starting Locust 0.12.2
[2019-11-13 00:24:33,820] SQZ777/ERROR/stderr: <gevent._socket3.socket object, fd=956, family=23, type=1, proto=0>: Invalid HTTP method: '\x16\x03\x01\x02\x00\x01\x00\x01ü\x03\x03Yç\x95ç.d\x9aÿN$¾Ò\x03>þ\\îÅî9³\t\x8e\x90\x8fe\x18J¥D\x8cú Ê*Øî\x08[\x01í\x9c\xad©tá »\x04vðìè\x15E\x96\x8cêXaõCrö\x81\x00"zz\x13\x01\x13\x02\x13\x03À+À/À,À0Ì©Ì¨À\x13À\x14\x00\x9c\x00\x9d\x00/\x005\x00\n'
[2019-11-13 00:24:33,822] SQZ777/ERROR/stderr: <gevent._socket3.socket object, fd=948, family=23, type=1, proto=0>: Invalid HTTP method: '\x16\x03\x01\x02\x00\x01\x00\x01ü\x03\x03\x9c¦d_à\x8b[xý\x9eúaþÒ&\x11m\x00hCºY8ô\x05\x13$úF\t\x98\x94 \x13Ý7J*\x9dÂ)\x9dq_ÐNêÂ¼\x80\x8fáñ\x01·2\x11É\x1f6hKUpÎ\x00"\x1a\x1a\x13\x01\x13\x02\x13\x03À+À/À,À0Ì©Ì¨À\x13À\x14\x00\x9c\x00\x9d\x00/\x005\x00\n'
[2019-11-13 00:24:33,851] SQZ777/ERROR/stderr: <gevent._socket3.socket object, fd=960, family=23, type=1, proto=0>: Invalid http version: '\x16\x03\x01\x02\x00\x01\x00\x01ü\x03\x03)p,.ò\x8d¸\x96ñ\x91þª¸,ûÏØ@<ÆRßÏBº!Ø\x80ñûöÂ cb\x1dLÄ\'\x0fÖG\x84gvm±G\x975$ÏêÎï7\x10\x07sØ»*i_\x17\x00"\x8a\x8a\x13\x01\x13\x02\x13\x03À+À/À,À0Ì©Ì¨À\x13À\x14\x00\x9c\x00\x9d\x00/\x005\x00\n'

Environment settings

OS: Windows 10
Python version: 3.7.5
Locust version: 0.12.2

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 18 (3 by maintainers)

Most upvoted comments

I’ve also faced this issue. The problem on my side was that I was accessing the server using https (https:0.0.0.0:8089) instead of http (http:0.0.0.0:8089). Silly mistake but nothing in the error indicates that this might be the problem so I ended up wasting a lot of time. This issue comes up when searching for the error so I’m just leaving this here in case anyone else makes the same mistake.

wangonya on Mar 29, 2023

@lundstrj I just debugged this same error message with someone and it turned out they had a config error. They has set the worker’s master-port setting to use the WEB_UI port (8089) instead of using the expected/default bind port (5557). Not sure why this was the error in that case, but it went away when they corrected that config issue.

lolwhitaker on Nov 1, 2021