Community
Participate
Eclipse IDE
Currently the iot.eclipse.org website and a demo MQTT service are provided by a vserver managed by Benjamin who is going to be leaving in January. Our plan is to separate these services by leaving the website at iot.eclipse.org, but serving it from Github pages. The MQTT service could then move to either mqtt.eclipse.org or mosquitto.eclipse.org However we need people from the community to manage the MQTT service, and who will do so in agreement with our hosted services policy[1]. If nobody from the community has volunteered to take on the management of the MQTT service by January 15th, 2019, I will presume the service is not wanted and shut it down. -M. [1] https://www.eclipse.org/org/documents/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy.pdf
+1
As part of the migration of the MQTT sandbox to a new server, it would be a good opportunity to address IPV6 support. See bug 539886.
We've had IPv6 on our to-do list for about 10 years now :/
Ok so here is the plan: next week we will assign an extra hostname to iot.eclipse.org and update the MQTT service to respond on that host name as well. Once that's done we'll notify the community so they can start transitioning, and then in a couple of weeks the website will be moved, and iot.eclipse.org will stop responding to MQTT requests. -M.
I assume from the lack of responses that no new owner for the iot.eclipse.org MQTT service was found? Paho already has a vserver which I use to host an MQTT service (paho8181.cloudapp.net), so perhaps that could be used instead. Where will the notification to the community take place? I don't want to miss it.
(In reply to Ian Craggs from comment #5) > I assume from the lack of responses that no new owner for the > iot.eclipse.org MQTT service was found? That is true, however I'm holding off for right now due to an internal request. > Where will the notification to the community take place? I don't want to > miss it. Well if we get the messaging right you won't, but it hasn't happened yet. -M.
hi, Is the service is moved to other website? I have 3 devices working on mqtt.eclipse.org:1883. Is the service closed or moved? Currently cannot access the service.
(In reply to Alihuseyn Gulmammadov from comment #7) > hi, Is the service is moved to other website? I have 3 devices working on > mqtt.eclipse.org:1883. Is the service closed or moved? Currently cannot > access the service. As far as I know, the website hasn't move yet. @webmster, could you take a look and see if the service is running?
(In reply to Christopher Guindon from comment #8) > > mqtt.eclipse.org:1883. Is the service closed or moved? Actually it never opened on mqtt.eclipse.org, it is still simply iot.eclipse.org. I've added a DNS record for mqtt.eclipse.org that points at iot.eclipse.org to allow us to start separating these services. -M.
@webmster thanks for support. You are right. But with iot.eclipse.org return connection refuse. İ tried the following command for subscribing $ mosquitto_sub -h iot.eclipse.org -p 1883 -t test $ Error: Connection refused Did i make anything wrong?
*** Bug 545251 has been marked as a duplicate of this bug. ***
(In reply to Alihuseyn Gulmammadov from comment #10) > @webmster thanks for support. You are right. But with iot.eclipse.org return > connection refuse. It looks like the MQTT service had crashed. I've restarted it and it seems to be responding. > $ mosquitto_sub -h iot.eclipse.org -p 1883 -t test I think that port should be 8883. -M.
Thanks for the support @webmster. The service is active now and accepts connections. Also as seen from comments, group want to give the responsibility of service to other volunteers or close the service in the near future. Is there any exact date the service will close? I mean will this service will be open for 2 months?
(In reply to Alihuseyn Gulmammadov from comment #13) > Is there any exact date the service will close? I mean will this service will > be open for 2 months? We don't have a specific shutdown date right now. @Ian Are you comfortable with us directing everyone that needs a test instance at the service running on Pahos vserver? If so Frederic and I will start working on a messaging plan to notify the community. -M.
I'm going to pick June 5th 2019 as the date where we will shutdown the mqtt service and move the iot.eclipse.org website to a new host. -M.
the broker at iot.eclipse.org appears to be offline... could someone poke it, please?
I have 6 cars trying to connect to iot.eclipse.org:1883. I will have to reinstall each device in the car to change to another broker. What will generate expenses.
I've restarted the mqtt broker. -M.
(In reply to Eclipse Webmaster from comment #18) > I've restarted the mqtt broker. > > -M. Thanks. I am planning to reinstall the connected equipment in the cars, as they point to iot.eclipse.org and you will change it. There will no longer be suspensions until you make the change? and, when will you make the change?
> There will no longer be > suspensions until you make the change? and, when will you make the change? The mqtt service is not actively maintained or monitored, so I can't guaranty that it won't fall over again. If it does posting on this bug is probably the best way to let us know the service is offline. As noted in comment #15 I'm planning to stop the service permanently on June 5th 2019. -M.
I had the opportunity to discuss this at length with members of our community. In the end, we agreed that the service must be transferred to a community-managed server. Ian Craggs and Roger Light, respectively project leads for Eclipse Paho (MQTT clients) and Eclipse Mosquitto (MQTT broker), have accepted to work on the solution together. Going forward, Roger will maintain a server running the latest stable version of Mosquitto on infrastructure provided by Ian. This new server will have a new DNS name: mqtt.eclipse.org. Usage of iot.eclipse.org for MQTT connections will be discontinued. To prevent service disruptions, we will keep the current Foundation-managed server around for the time being. This means it will likely run past the initial June 5 cutoff date However, the intent is for the transition to happen as soon as possible. As of today, mqtt.eclipse.org points to the current server. This simplifies the transition. Below is our intented transition plan: 1. I will start communicating about the new DNS name for the server immediately. Specifically, I will send emails to the IoT working group, Paho and Mosquitto mailing lists. I will post on social media. I will also update iot.eclipse.org. Roger and Ian will update the Paho and Mosquitto docs if needed. 2. In the meantime, Roger will setup the new server and will ensure it is stable. 3. Once Roger is ready, we switch the DNS record to the new server. I will update this bug once we have a target date for the server switch. Thank you to Ian and Roger for stepping up to preserve a valuable service for our community to enjoy!
I still need to change the address to a new broker on some of my devices, however, iot.eclipse.org is down. Can you activate it even if it is until June 5 as scheduled?
I've restarted the MQTT service. -M.
(In reply to Eclipse Webmaster from comment #23) > I've restarted the MQTT service. > > -M. Thanks a lot, about that...
I'm trying to connect to the new server in javascript. I have: app_global.mqtt = new Paho.MQTT.Client("wss://mqtt.eclipse.org/ws", someClientID); And it gives me this error: WebSocket connection to 'wss://mqtt.eclipse.org/ws' failed: Error in connection establishment: net::ERR_CERT_COMMON_NAME_INVALID This piece of code used to work with "wss://iot.eclipse.org/ws". What am I doing wrong? Thanks for your help!
(In reply to Lucile Callebert from comment #25) As noted in comment #9 the MQTT service never started on mqtt.eclipse.org, so for right now you will need to keep using iot.eclipse.org. However per comment 21 there will be service at mqtt.eclipse.org at some point in the future once the project team has set it up, so don't hard code anything :) -M.
Well since mqtt.eclipse.org resolved to the same IP as iot.eclipse.org there is effectively as service 'running' on the former :-) Webmaster would need to update the SSL certificate for mqtt.eclipse.org to work over SSL since right now the certificate is only valid for iot.eclipse.org commonn name. But my guess is this will have to wait for the service to *effectively* move to mqtt.eclipse.org, Lucille. Benjamin. (In reply to Eclipse Webmaster from comment #26) > (In reply to Lucile Callebert from comment #25) > > As noted in comment #9 the MQTT service never started on mqtt.eclipse.org, > so for right now you will need to keep using iot.eclipse.org. > > However per comment 21 there will be service at mqtt.eclipse.org at some > point in the future once the project team has set it up, so don't hard code > anything :) > > -M.
The team responsible for the new server has indicated that they are ready, so I've updated the DNS records for mqtt.eclipse.org to start the separation process. Once DNS has propagated(48h or so) I'll shutdown the mqtt service on iot.eclipse.org and I think we'll be done. -M.
(In reply to Eclipse Webmaster from comment #28) > The team responsible for the new server has indicated that they are ready, > so I've updated the DNS records for mqtt.eclipse.org to start the separation > process. Is there any plan to migrate this service to mqtt.eclipseprojects.io? Once DNS has propagated(48h or so) I'll shutdown the mqtt service > on iot.eclipse.org and I think we'll be done. > > -M. I think we should consider this done once iot.eclipse.org is hosted on our new cluster.
I've now shutdown the mqtt service on iot.eclipse.org, so people should now be using mqtt.eclipse.org. Frederic if people need support where should they file a bug? (In reply to Christopher Guindon from comment #29) > Is there any plan to migrate this service to mqtt.eclipseprojects.io? Yes, but that will happen via a separate bug. > I think we should consider this done once iot.eclipse.org is hosted on our > new cluster. Fair enough. We can begin moving the website whenever your team is ready. -M.
I have been able to connect to iot.eclipse.org with a MQTT client this morning. Can you turn off the service off and ensure it is gone for good, please? Thanks!
(In reply to Frédéric Desbiens from comment #31) > I have been able to connect to iot.eclipse.org with a MQTT client this > morning. Can you turn off the service off and ensure it is gone for good, > please? Thanks! Uh can we NOT turn it off? Still using it as I'm unable to connect to mqtt.eclipse.org in js. Not sure why as it works in python. Anyway, still using iot.eclipse.org.
Does test.mosquitto.org work for you? Also, I suggest you post about your problem on the Mosquitto mailing list to attract Roger Light's attention to it.
I created Host IoT on EF k8s cluser #173 https://github.com/EclipseFdn/iot.eclipse.org/issues/173 to address our hosting problem. I think we can close this bug since we now have a bug for this hosting request.
