[Etherpad] - Error when adding comment #1445
Labels
No labels
🔥
🦾 1
🦾 2
🦾 3
🦾 4
🦾 5
🦾 6
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
🙌 Decission needed
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
forgejo
Free to take
Funding
fun_project
help wanted
high impact
housekeeping
Howto
infra
In progress
🤔️ Investigate
ios
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low impact
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
PR ready
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
sysadmin
Themes
TOR
upstream issue
Website
windows
WIP
wontfix
xmpp
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Disroot/Disroot-Project#1445
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Trying to add a comment results in an error:
@muppeth this issue is coz of CSP. If we set them back as before worked on them (check PR 357 on host_vars), we don't have the issue anymore. Should we get back to what we have before?
Also, I've seen in Firefox console quick a few number of this kind o message :
GET wss://pad.disroot.org/socket.io/?padId=test&EIO=4&transport=websocket&sid=sPsdfsfdsfdsfdsf NS_ERROR_WEBSOCKET_CONNECTION_REFUSEDSo I'm wondering if this could be related to Anubis blocking.
yes on both sides I think. For now reverting the csp is good. I would say fix it in prod and make PR. I will be doing my cleanup on proxies this week (hopefully) so then I will run it. As for anubis we need to check how to do it properly to avoid websockets connection failures. My guess is we should route all non sock traffic through anubis. I will check the docs cause I guess this use case is even documented.
fixed on prod + PR done on host_vars