Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scalar: Etherpad widget broken on all platforms "Sorry, this content is not embeddable in Matrix" #9098

Closed
aaronraimist opened this issue Mar 10, 2019 · 9 comments
Labels
A-Scalar A-Widgets P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@aaronraimist
Copy link
Collaborator

Starting in the last day or two I've seen people report that the Etherpad widget is broken on Android and iOS and I can reproduce on web.

Screen Shot 2019-03-10 at 8 22 32 AM

[Error] Failed to load resource: the server responded with a status of 502 () (embeddable, line 0)
[Error] Failed to load resource: the server responded with a status of 403 () (etherpad-03386755b8f994101a68.bundle.js.map, line 0)
[Error] Content is not embeddable – "The string did not match the expected pattern."
	(anonymous function) (etherpad-03386755b8f994101a68.bundle.js:69:8649)
	i (etherpad-03386755b8f994101a68.bundle.js:67:72784)
	_settlePromiseFromHandler (etherpad-03386755b8f994101a68.bundle.js:67:46189)
	_settlePromise (etherpad-03386755b8f994101a68.bundle.js:67:47010)
	_settlePromise0 (etherpad-03386755b8f994101a68.bundle.js:67:47698)
	_settlePromises (etherpad-03386755b8f994101a68.bundle.js:67:48915)
	_drainQueue (etherpad-03386755b8f994101a68.bundle.js:67:2806)
	_drainQueues (etherpad-03386755b8f994101a68.bundle.js:67:2863)
	drainQueues (etherpad-03386755b8f994101a68.bundle.js:67:997)
	promiseReactionJob
@lampholder lampholder added T-Defect P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-Scalar A-Widgets labels Mar 15, 2019
@lampholder
Copy link
Member

@jaywink this still works for me - any ideas?

@jaywink
Copy link
Member

jaywink commented Mar 15, 2019

It looks tbh either a temporary problem with Scalar or Etherpad itself. I can't really tell where the 502 is from in the stack. Could dig deeper but first would like to ask @aaronraimist can you still get a failure? If so, can you let me know the timestamp when you re-tried and I will take a new look at logs?

For me tried web, desktop and mobile, not live and develop, and things seem to work fine atm.

@aaronraimist
Copy link
Collaborator Author

Hmm. No I cannot reproduce it today. I'll reopen if I get it again or hear any more reports. It seems like it was broken for about a 24 hour period before I opened this issue though so it may be worth looking in to those logs.

@florianjacob
Copy link

I have this exact & reproducable behaviour when I use etherpad names that are too long: ABCDEFGHIJKLMNOPQRS as pad name, i.e. 20 chars long works just fine, but ABCDEFGHIJKLMNOPQRST, i.e. 21 chars long, results in a 502 bad gateway and the not embeddable banana. Could that be what was actually causing this? Related: https://github.com/vector-im/riot-web/issues/6039

@Biep
Copy link

Biep commented Jul 23, 2020

A friend of mine has a slightly different issue:
She has an issue with Etherpad - only on the Mac. Elsewhere (iPad, iPhone) she can open the integration just fine, but on the Mac she gets this content is not embeddable in Matrix. both in Safari and in the installed Element Desktop.
On the iPad it crashes sometimes, but otherwise works well.

@k0gen
Copy link

k0gen commented Jan 4, 2021

A friend of mine has a slightly different issue:
She has an issue with Etherpad - only on the Mac. Elsewhere (iPad, iPhone) she can open the integration just fine, but on the Mac she gets this content is not embeddable in Matrix. both in Safari and in the installed Element Desktop.
On the iPad it crashes sometimes, but otherwise works well.

Yes I can confirm that this is still the problem on Safari or Brave and in latest (1.7.16) Element.app on macOS Big Sur 11.1
Element.app:
Element-app 2021-01-4 o 22 22 38
Safari.app:
Safari-2021-01-4 o 22 15 13
Brave.app:
Brave-2021-01-4 o 22 39 17

As much as I don't trust Google Chrome.app for my daily browsing I decided to do a last test and turns out it is the only one that works:
chrome-2021-01-4 o 22 44 44

@jaywink
Copy link
Member

jaywink commented Jan 5, 2021

The issue with Safari is tracked in element-hq/element-integration-manager#19

@k0gen
Copy link

k0gen commented Jan 5, 2021

The issue with Safari is tracked in element-hq/element-integration-manager#19

Yes, thank you for the information. I have decided to write a comment in this issue because it felt more general. Should I open a new issue separately for Element Desktop app (macOS) and Brave Browser?

@jryans
Copy link
Collaborator

jryans commented Jan 14, 2021

Please default to opening new issues, and we can de-duplicate as needed. Generally speaking, closed issue are not watched for new comments and complicate tracking.

@element-hq element-hq locked as resolved and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Scalar A-Widgets P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

7 participants