~tardypad/wee-most-discuss

3 2

Server upgrade to 8.x breaks wee_most.py?

Kjetil Torgrim Homme <kjetilho@ifi.uio.no>
Details
Message ID
<b720297946e8d548682375620684c1c02d814ad1.camel@ifi.uio.no>
DKIM signature
missing
Download raw message
last night, our Mattermost server was upgraded from 7.8.x to 8.1.4. 
using the latest patch in master branch, I get

 rlmm      | Connecting to rlmm
 rlmm  =!= | An error occurred while creating the websocket worker

and after that, once a minute

 rlmm  =!= | An error occurred while updating direct message channels
name

no channels are available.  anyone else having issues after the major
upgrade?

-- 
venleg helsing,
Kjetil T.
Kjetil Torgrim Homme <kjetilho@ifi.uio.no>
Details
Message ID
<b783ef96d7f7a581b7d6d08c7244b262d0e4d8d7.camel@ifi.uio.no>
In-Reply-To
<b720297946e8d548682375620684c1c02d814ad1.camel@ifi.uio.no> (view parent)
DKIM signature
missing
Download raw message
fr. den 03. 11. 2023 klokka 11.00 (+0100) skreiv Kjetil Torgrim Homme:
> last night, our Mattermost server was upgraded from 7.8.x to 8.1.4. 
> using the latest patch in master branch, I get
> 
>  rlmm      | Connecting to rlmm
>  rlmm  =!= | An error occurred while creating the websocket worker

setting "Enable cross-origin requests from: *" works.  I wonder what
wee_most.py does which causes CORS validation to fail.

-- 
venleg helsing,
Kjetil T.
Details
Message ID
<CWQBNGUSGHP2.1M621QIWE5TQW@tardypad.me>
In-Reply-To
<b783ef96d7f7a581b7d6d08c7244b262d0e4d8d7.camel@ifi.uio.no> (view parent)
DKIM signature
missing
Download raw message
> > last night, our Mattermost server was upgraded from 7.8.x to 8.1.4. 
> setting "Enable cross-origin requests from: *" works.  I wonder what
> wee_most.py does which causes CORS validation to fail.

wee_most doesn't do any specific thing. I believe setting this 
configuration server side is actually needed for wee_most to work.

Checking the changelog 
https://docs.mattermost.com/install/self-managed-changelog.html, I see 
the following text here and there.

"For servers wanting to allow websockets to connect from origins other 
than the origin of the site URL, please set the 
ServiceSettings.AllowCorsFrom configuration setting."

-- 
Damien Tardy-Panis
Kjetil Torgrim Homme <kjetilho@ifi.uio.no>
Details
Message ID
<f1e66575464eb0e4c2de0ff886f726ad550efd7f.camel@ifi.uio.no>
In-Reply-To
<CWQBNGUSGHP2.1M621QIWE5TQW@tardypad.me> (view parent)
DKIM signature
missing
Download raw message
la. den 04. 11. 2023 klokka 21.49 (+0100) skreiv Damien Tardy-Panis:
> > > last night, our Mattermost server was upgraded from 7.8.x to 8.1.4. 
> > setting "Enable cross-origin requests from: *" works.  I wonder what
> > wee_most.py does which causes CORS validation to fail.
> 
> wee_most doesn't do any specific thing. I believe setting this 
> configuration server side is actually needed for wee_most to work.
> 
> Checking the changelog 
> https://docs.mattermost.com/install/self-managed-changelog.html, I see 
> the following text here and there.
> 
> "For servers wanting to allow websockets to connect from origins other 
> than the origin of the site URL, please set the 
> ServiceSettings.AllowCorsFrom configuration setting."
> 

yes, but Matterhorn still works, and it runs on "random" workstations
like weechat.  I tried turning on CORS debugging in our Mattermost, but
could not find any relevant logging when connecting using wee_most.py
(with neither "" nor "*").  will have to dig deeper later.

-- 
venleg helsing,
Kjetil T.
Reply to thread Export thread (mbox)