Can’t establish a connection to the server at ws://wikimon.hatnote.com:9220/.

[hugolpz]

Your tool is cited by the MOOC Wikidata from Wikimedia France. The community has pointed out widespread bug, while other users can access the service normally.

On Firefox / Ubuntu : http://listen.hatnote.com/#wikidata

Firefox can’t establish a connection to the server at ws://wikimon.hatnote.com:9220/.

On google chrome / Ubuntu : http://listen.hatnote.com/#wikipedia

Failed to load resource: the server responded with a status of 404 (Not Found)

WebSocket connection to 'ws://wikimon.hatnote.com:9000/' failed: WebSocket is closed before the connection is established.

[mahmoud]

Hey @hugolpz! So usually this issue is caused by local firewalls or network rules that block those ports and/or websockets, usually at a workplace/school setting. Our monitoring hasn't shown any connectivity outages from 5+ geographic locations in the last 24 hours. When you say the community has pointed out a widespread issue, can you share a link with more details? Thanks!

[hugolpz]

Hello @mahmoud , your hypothesis is correct !

Wikimedia France just opened a MOOC Wikidata . We mostly marketed it to universities. I'm indeed working at and using my university wifi connection to access this page. (Screenshot of forum to come.)

After testing with my personal cellphone as hotspot, I can confirm your assessment :

1. personal 5G connection : it works.
2. university connection : it stops. (see : no more Qid, only legacy dying out circle shapes from previous phase)

While your diagnosis is correct, if no server answer for a while then a warning message encouraging the user to checks its network firewall or switch wifi would be interesting. Should I open a ticket for this ?

(2) Also, could you temporally grant me some higher user-rights so I may do some minor clean up on your issues ? I'm familiar with github / wikimedia project management, doing a clean up would take me 15 minutes, explaining would take us 2+ hours = wont happen.

[mahmoud]

Yeah the best fix we identified for WS blockage is actually #31, which actually got a start in a rewrite by @xabriel this year: https://github.com/xabriel/listen-to-wikipedia/tree/vue-rewrite

A warning would be good in the meantime, if you'd like to submit a PR I'm happy to review. As far as the state of issues goes, I'd like to know more about what you're proposing, as so far L2W issue management hasn't been much trouble.