Hello everyone,
I upgraded XWiki from version 17.3 to 17.5. Now, when I try to edit a page, the pointer turns and I get stuck and can’t write anything.
Do you have any idea where I should look for this issue?
Weird. No idea. Maybe hard fresh your browser cache just in case?
My college has the same issue on his browser and it works again if i go back to the old backup with 17.3 version. Could it be something to do with the XWiki configuration file? When I updated it, I did a 3way merge.
Could you check the javascript console of your browser? There might be an error displayed there explaining why it gets stuck.
We’re experiencing the exact same issue. Will check for errors and post them.
@Raphael_L Temporarily deactivating the xwiki-realtime Plugin solved the issue for us at least for the time being. However, this obviously also deactivates the ability to work in a realtime editor session.
This is what I get as error in the console:
Firefox can’t establish a connection to the server at wss://xwiki.anonymous.de/websocket/xwiki/netflux.
netflux-client.js:438:66
It used to work with previous versions of XWiki.
I first noticed this error - as far as I remember - in XWiki 17.4.0
Hello! We face the same issue, but only in Firefox 128.12 esr we cannot edit anything in 17.5.0. Just a spinning wheel.
To be precise, the visual editor does not work, source code would work, but our users cannot use source code editor.
In chromium 138 it works fine with visual editing.
Have you tried with the latest Firefox standard version? I’m using v140.0.2 for instance. We don’t run our automated tests with the ESR version of Firefox, so if there is a problem there it isn’t caught, unfortunately. See https://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy/BrowserSupportStrategy .
Both standalone and in-place WYSIWYG editing works for me on a clean XWiki 17.5.0 with Firefox 140.0.2. Given that you say it works for you with the latest Chrome version (138), I suspect this is an issue with the ESR Firefox version.
I use Firefox with V140.0.4 and it doesn’t work with Chrome and the Edge browser either.
And i get aswell the wss://xwiki.anonymous.local/xwiki/websocket/xwiki/netflux.
If i deactivating the xwiki-realtime it works.
We are using the non-ESR version of Firefox. I can reproduce the issue in Chrome non-ESR as well.
From my POV something important related to the xwiki-realtime feature seems to have changed somewhere between versions 16.10.2 and 17.4.0
Thank you very much, deactivating the plugin in the wysiwig-editor settings did the job! We can now edit it in Firefox ESR.
This is what I found in our logs.
2025-07-10 09:13:40,960 [qtp1800659519-10647] DEBUG .x.w.i.XWikiEndpointDispatcher - WebSocket connection error.
java.nio.channels.ClosedChannelException: null
at org.eclipse.jetty.websocket.core.internal.WebSocketSessionState.onEof(WebSocketSessionState.java:168)
at org.eclipse.jetty.websocket.core.WebSocketCoreSession.onEof(WebSocketCoreSession.java:229)
at org.eclipse.jetty.websocket.core.WebSocketConnection.onClose(WebSocketConnection.java:209)
at org.eclipse.jetty.io.ssl.SslConnection.onClose(SslConnection.java:358)
at org.eclipse.jetty.io.SelectorManager.connectionClosed(SelectorManager.java:347)
at org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint.run(ManagedSelector.java:1094)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:979)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1209)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1164)
at java.base/java.lang.Thread.run(Thread.java:840)
You’re using the secure (SSL) WebSocket connection (wss://), because you’re accessing XWiki through HTTPS. Could you check if it fails also when using the non-secure connection (ws://), i.e. when accessing XWiki with HTTP?
Also, it would be great if you could try with a clean XWiki 17.5 version, to see if the problem was caused by the upgrade or not. On my side I can’t reproduce with a clean 17.5 version, but I only tested with HTTP, not HTTPS.
Thanks,
Marius
What puzzles me is that:
- @cseeg mentioned it works for him with Chromium 138; do you have Chrome available as well to try?
- both @Raphael_L and @Pako mentioned it doesn’t work for them on Chrome; do you have Chromium available to try?
@cseeg are you using secure (SSL) connection as well (https:// and wss://) ?
Thanks,
Marius
I tested it on a non-SSL connection. It works as intended. So the issue seems to be related to SSL.
1 Like
Thanks a lot for checking. I need to set up SSL connection locally to test. Unfortunately our automated tests don’t run with SSL.
Yes, we are using https/SSL. wss i could not find, in the logs there is only ProtocolHandler [“https-openssl-nio-443”]
How can i check if wss is on?
In Google chrome 138 it works like in chromium too, it is just firefox esr 128.
Greetings, Nina
1 Like
Im facing the same problem when accessing xwiki over a nginx proxy with http. We can’t enter the editing mode and there are no safe buttons when creating a new page.
There is no problem when accessing directly over ip:port.
The console error message is identical to Pako:
netflux-client.js:438 WebSocket connection to ‘ws://wiki.subdomain.domain.local/websocket/xwiki/netflux’ failed:
c @ netflux-client.js:438
We are running XWiki 17.5.0. Im using Google Chrome Version 138.0.7204.100 (64-Bit)
I have the same on my personal wiki and the work wiki. I access them via Vivaldi browser and Edge browser, same issue.
We run the wikis in Docker.