• Mo chevron_right

    ejabberd 17.09 is out

    Timothée Jaussoin – pubsub.movim.eu / Movim – Friday, 29 September, 2017 - 14:51

ejabberd 17.09 is the first version of #ejabberd recommended for the upcoming #Movim 0.12 #release. We worked closely with the ProcessOne team, especially on the #Pubsub implementation, to improve the integration between Movim and ejabberd. Thanks to them!

  • ejabberd 17.09

    ejabberd 17.09 is out! This release mostly contains bugfix and adds few improvements.

  • chevron_right

    Contact publication

    Timothée Jaussoin – Wednesday, 16 August, 2017 - 12:55 edit

The migration of the #XMPP #Movim server from #Metronome to #ejabberd is close to be done and most of the services are up again, sorry for the connectivity issues that you had those pas few days.

I'll write a longer post about that #migration in the upcomign days on the official Movim blog.
  • Migration

    The honking of Canadian geese overhead caught my attention just long enough for my to snap this shot. Too bad I couldn't get a good photo of their V-formation, as they're quite disorganized in this...

  • Mo chevron_right

    XMPP server hands-on comparison: ejabberd vs. Prosody

    Timothée Jaussoin – pubsub.movim.eu / Movim – Sunday, 6 August, 2017 - 21:18

A really nice new article of Netfuture.ch with a small comparison between #ejabberd and #prosody :)

  • XMPP server hands-on comparison: ejabberd vs. Prosody

    Having been involved in testing an open-source XMPP web client (JSXC) against ejabberd and Prosody, I have noticed the following differences that I would like to share, to make it easier for you to decide. Please note that I have done more with ejabberd, so there will naturally be more nitpicking th

  • Mo chevron_right

    Downtime on the movim.eu XMPP service

    Timothée Jaussoin – pubsub.movim.eu / Movim – Wednesday, 26 July, 2017 - 21:52

We are currently experiencing downtimes of the movim.eu XMPP server (and related services like Pubsub or Conferences) for several weeks now. This is having a serious impact on the availability of the platform (and, by extension, Movim related instances) for many of our users. We are deeply sorry about that.

The exact reason of those downtimes is not known for now (it seems to be related to the Pubsub module of the server). The movim.eu XMPP services are running on top of the Metronome XMPP server that is not maintained anymore since 2016.

We are currently working closely with the ejabberd XMPP server team to migrate the whole XMPP infrastructure in the upcoming weeks to this new server. This migration will also bring more stable and new features (especially regarding the Pubsub part) to the existing platform.

Thanks for your comprehension. #movim #downtime #xmpp #metronome #ejabberd #migration

  • chevron_right

    Trying to get Movim running at home...

    Roelof Pieter – Tuesday, 16 May, 2017 - 20:22 edit

This is a description of the problems I encountered when trying to install a Movim "compatible" XMPP server. This is mainly a reminder to myself, in case I want to try again in some time. I have written this in afterwards, and some of the details have blurred. Be skeptical of everything you read here :-)

#movim #ejabberd #prosody

So, I've been trying to get a complete Movim "suite" running on my Raspberry Pi @ home. For me this means running the following components:

  1. Movim itself
  2. A web server for presenting the Movim interface (Nginx)
  3. A database server for storing Movim "stuff" (MySQL/MariaDB )
  4. A XMPP server for the actual transportation of messages and storage of "content"

I did already have Nginx and MySQL running. Installing Movim was quite straightforward, thanks to the instructions in the wiki. Also, I had already implemented things like DNS (a .nl domain through Yourhosting) and encryption using Letsencrypt. The tough nut to crack here is the XMPP server. I haven't been able to get this running in a way that I can fully enjoy Movim.

First up: Prosody.

I already had Prosody running as an alternative to the evil "Whatsapp". I use it mainly for chatting with my wife, who of course also has a Whatsapp account. She always looks a bit weary of me when we use Conversations. So, since it was already there, I tried this first. Despite the warnings that it has some drawbacks. Well, it works fine as a chat client, but the "news" section is disabled. The configuration section tells me that Movim is working in a "degraded" mode. Trying to get it running has at least had me configure http_upload (XEP-0363) so file uploading works better now.

Next Ejabberd (Version 15.X)

So, use my Raspberry Pi for many things. It's main purpose however is running as a media-center running Kodi. For this reason I have installed OSMC as it's operating system. It is basically Raspbian, optimized for playing media. Being based on Raspbian it means there are a lot of packages available. Amongst them Ejabberd, albeit in an old version (14.07) . I installed Ejabberd and disabled prosody. After plowing through the terrible configuration file* (in Yaml, which was new for me) in the end I finally had it running. Chat works and Movim appears in it's full glory (with "News"). The only thing missing is the ability to upload files/photo's to it. But hey, there is a module for that. I couldn't get it running though. A lot of scary errors, that I forgot to write down though :-( . I Googled a lot (well Duckduckgo'd) but the suggested configurations all led to an error and a crash of Ejabberd. So, this was no good either.

Finally, Ejabberd (17.04) from source

As there was no later version of Ejabberd as a package available, I decided to just download the source of more recent version of Ejabberd. After remembering how this compiling goes, I did a "./configure --enable-user ejabberd & make & make install". Installation was fine. But here also I have a problem with mod_http_upload. Gajim, which I use for testing my XMPP account, with the http-upload-plugin recognizes the possibility to upload a file. I see in the logging that the upload request reaches the server and is processed, without error by the server, but the file doesn't seem to end up anywhere on the server. Gajim just tells me there is a HTTP error. Conversations only tells me the upload has failed. I spent several hours trying different combinations of configurations, mainly trying alternating docroots, but to no avail.

So, nope... (for now)

So, by now I have given up for now. Perhaps I will try Ejabberd later again. With some more luck I might succeed. I have prosody running again, for chatting with my wife. If I understand correct, in the next version 0.10 (or the next 0.11) Pep persistence might be available in prosody, making it run better with Movim.

  • ) Yes, I know there is a web-interface but I found the screen shots not very promising. I go the impression it was mainly for day-to-day administration, and not for setting the damn thin up. And, it more easy and therefore not nearly as cool :-) .
  • chevron_right

    ejabberd CORS mini-HOWTO

    Marzanna – Wednesday, 25 January, 2017 - 16:49 edit

If you are setting up your own Movim pod and and getting errors like

Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

on uploading files you probably have Movim running on movim.yourdomain.tld and ejabberd http_upload on yourdomain.tld. You have to enable CORS for ejabberd:

   mod_http_upload:
     custom_headers:
       "Access-Control-Allow-Origin": "*"
       "Access-Control-Allow-Methods": "GET, POST, PUT, OPTIONS, DELETE"
       "Access-Control-Allow-Headers": "Content-Type, Origin, X-Requested-With"

This will allow you to use http_upload on another domain on your Movim pod.

UPD: It won't work for upload.yourdomain.tld. See https://github.com/processone/ejabberd/issues/1482