Service Connection Timeout: Disroot Webchat and Movim Server Unreachability #1441
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Disroot/Disroot-Project#1441
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?
Description:
I am currently experiencing consistent connection failures when attempting to access the Disroot Webchat and the official Movim server. I have verified that these issues persist across multiple devices (mobile and PC) and remain unaffected by local DNS settings, adblocker configurations, or firewall policies.
The connection attempts yield the following error reports:
I have performed a preliminary check of my local network environment, including DNS resolution, adblocking services, and firewall rules, none of which appear to be the cause of this connectivity issue. Please investigate the status of the XMPP/TLS gateway for disroot.org.
I just checked and I could connect to both movim instances without issues with my xmpp account.
I managed to login later that day, but it's still strange.
+1 for random timeouts in general (I've had periods where almost every service has timed out, including parts of the login page - in that case, it appears that the javascript silently times out, resulting in a page with no CSS or js - unstyled - that is nonfunctional).
It can take ~20 minutes to get to a point where the timeouts go away, after which things are mostly okay.