Guilherme Pereira Leme

It makes total sense, have you made any coding to pull request this change? I would like to see some.

(Update) - Depending on this merge to be released, so that we can fix this issue: https://github.com/resque/resque/pull/1806

(Update) - The new [version of redis-namespace](https://rubygems.org/gems/redis-namespace/versions/1.9.0) has been released and we also updated the Gemfile for the version 1.9.0. But as we can see from [this comment](https://github.com/resque/redis-namespace/issues/193#issuecomment-1215378868), apparently, we...

Hello, guys, sorry for the delayed response. So, I tested this PR with a reverse proxy and only one instance of BBB, and there is something I want you to...

Yeah, it seems that for the client to connect to the pad, it has to get the session for the etherpad component, so, I guess this request to `/pad/socket.io...` would...

As I already commented on #15753 there are some fixes to the etherpad's files for nginx to avoid other CORS problem and resolve item B on #15436, so in #15753...

> I think this is something else. Pad requests never should go through the proxy. Maybe someone is generating a URL /pad/... somewhere which would lead the browser to the...

Hey @BrentBaccala, I suggested a slight change in the code just to ensure those warnings won't break and display incomplete information.

Hey @kepstin. > Re-running the bbb-record --addcustomgems command a second time keeps appending to the existing file, which can cause conflicts if for example some tries to update a gem...

Hey @fireba11, can you give us some more info on what happened? e.g.: logs of scalelite, logs of `bbb-conf --check`, `bbb-conf --status`, and other additional info/settings that you find interesting...