New messages in matrix channel fail to post to pnut.io #64

New issue

Closed

opened 2023-04-30 14:25:44 +00:00 by thrrgilag · 2 comments

thrrgilag commented

2023-04-30 14:25:44 +00:00

(Migrated from gitlab.com)

New messages posted to matrix rooms are failing to post to the bridged pnut.io channel. The only indication in the logs oddly enough is pnut-matrix_1 | werkzeug - INFO - *.*.*.* - - [30/Apr/2023 14:17:56] "PUT /_matrix/app/v1/transactions/1?access_token=<redacted> HTTP/1.1" 404 -.

New messages posted to matrix rooms are failing to post to the bridged pnut.io channel. The only indication in the logs oddly enough is `pnut-matrix_1 | werkzeug - INFO - *.*.*.* - - [30/Apr/2023 14:17:56] "PUT /_matrix/app/v1/transactions/1?access_token=<redacted> HTTP/1.1" 404 -`.

thrrgilag commented

2023-04-30 14:25:45 +00:00

(Migrated from gitlab.com)

assigned to @thrrgilag

thrrgilag commented

2023-04-30 15:25:43 +00:00

(Migrated from gitlab.com)

The release notes for Synapse 1.81 indicate a change in what synapse uses for appservice calls.

Synapse now attempts the versioned appservice paths before falling back to the legacy paths. Usage of the legacy routes should be considered deprecated.

https://github.com/matrix-org/synapse/releases/tag/v1.81.0

It's likely the cause of the 404 in the logs and why it's failing to post to pnut.io.

The release notes for Synapse 1.81 indicate a change in what synapse uses for appservice calls. > Synapse now attempts the versioned appservice paths before falling back to the legacy paths. Usage of the legacy routes should be considered deprecated. https://github.com/matrix-org/synapse/releases/tag/v1.81.0 It's likely the cause of the 404 in the logs and why it's failing to post to pnut.io.