Problems using docker-compose

22 views
Skip to first unread message

Claudio Viana

unread,
May 15, 2024, 9:25:23 AMMay 15
to bigbluebutton-greenlight
Hello, can you help me? 
I'm trying to use Greenlight by pointing to an instance we already have of BBB to evaluate use in the company, initially I'm running it locally on a Macbook.

When running Docker-compose locally the process ends, without errors, but when executing the operations below the errors described occur:

Action:
- Accessing http://localhost:5050 in the host browser is redirected to https (I cleared cache, tried in incognito tab and other browsers)
Result:
-- Browser is redirected
-- Console log
---- HTTP parse error, malformed request: #<Puma::HttpParserError: Invalid HTTP format, parsing fails. Are you trying to open an SSL connection to a non-SSL Puma?>

Action:
--Run from host via CURL http://localhost:5050
Result:
-- Returns nothing

Action:
-- Enter the container and run a WGET http://localhost:3000 (original port)
Result:
-- Returns the error:
---- Connecting to localhost:3000 (127.0.0.1:3000)
---- Connecting to localhost:3000 (127.0.0.1:3000)
---- 48EBFFFFFF7F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:354:
---- ssl_client: SSL_connect
---- wget: error getting response: Connection reset by peer
-- Console log
---- HTTP parse error, malformed request: #<Puma::HttpParserError: Invalid HTTP format, parsing fails. Are you trying to open an SSL connection to a non-SSL Puma?>


The service is apparently up and running because after start its possible to execute telnet from the host on port 5050

As WGET from inside the container also redirected to https, I understand that it is not a problem with the browser, but with some internal configuration

Is there any additional configuration, or something else that I should do?

Thanks
Reply all
Reply to author
Forward
0 new messages