WordPress.com failed to start
-
Hi there,
basically, right after sending my first blog post to my newly created blog, my WordPress.com desktop app stopped working and froze, with the following error messages:
WordPress.com failed to start.
WordPress.com ran into an error (code NaN).
Here is a screenshot:
Before trying to post to this blog, everything seemed to work normally, I was able to follow / read news / discuss on other blogs.
I am running almost fresh installation on Ubuntu 16.04 LTS and the blog was supposed to be about my experiences with Ubuntu.
The blog I need help with is: (visible only to logged in users)
-
Hi there,
Does this error occur immediately when the app opens, or when you click on any particular option?
Have you tried using a different internet connection to see if that makes any difference?
And have you tried doing a complete re-install of the app?
-
Hi Herman… everything worked until I sent my first post to my first blog. After that, the desktop client became unusable.
I tried to do the same via the browser, got the same result, with a different error:
Reducers may not dispatch action.
and the warning about an unresponsive script. Then browser stops to respond (Firefox 50.1.0, pre-installed with the OS).
Blogging via /wp-admin still works, but Calypso looked more convenient and on Windows 10, I didn’t have this issue.
-
If it happens in both the app and a browser it points to a connection issue as the most likely cause. Were you able to try a different internet connection?
Also please try clearing the browser cache and cookies as well as your computer’s and your router/modem’s DNS cache.
Please confirm if you’ve tried that and it doesn’t make any difference.
-
No opportunity to try different connection soon, but on both mobile devices in my home (Android 5.0.2/5.1.1 Lollipop), clicking the post title takes me to https://wordpress.com/posts/luboauswien.wordpress.com and clicking “Edit” to https://wordpress.com/posts/luboauswien.wordpress.com/3 where I am able to edit my post.
Doing the same crashes the Desktop App and freezes Firefox on Ubuntu, even after a deep system clean so really can’t continue blogging. -
Can you please take a screen shot for me of any errors in your browser console? You can upload them directly to your media library, here:
https://luboauswien.wordpress.com/wp-admin/media-new.php
https://en.support.wordpress.com/browser-issues/advanced-browser-troubleshooting/# javascript-errors-in-mozilla-firefox
If possible, can you also check Chrome for me? If it happens in one browser and not another that might give us a useful clue.
-
Hi Herman,
both Chrome and Chromium seem to work so can/can’t blogging with Calypso is no longer an issue.
On Firefox, I took a couple of screenshots and uploaded it to my media library via the link that you provided. The order in which I took them was:
1. Warning: Unresponsive Script
2. What I’ve seen in the Debugger
3. The only way to unfreeze FirefoxPlease let me know if there’s further help required, or in any case, just keep me informed how it went further :)
-
Thank you for the screen shots. However, we need to see any errors in the JavaScript console, not the debugger, so can you please specifically take a screen shot of that for me?
Also please make sure that you get everything that appears in the console so that it’s not getting cut off.
Thanks for checking in Chrome. Does it make any difference at all if you run Firefox in safe mode?
-
Unfortunately, I’m not able to get to the console, the debugger is the last thing I am able to see before the thing freezes.
Starting Firefox in safe mode brings exactly the same result.
-
Thanks. I’ve reported this to our developers to look into. I’ll let you know if they need any more information, or if they need you to try anything else.
-
Thank you very much! Hope that this will get solved soon as I very much prefer Firefox to Chrome. Looks better on Ubuntu, and is completely Open Source :)
-
I prefer FF as well, and we definitely don’t want a browser and the app to be unusable on Ubuntu :)
- The topic ‘WordPress.com failed to start’ is closed to new replies.

