This is a list of our most frequently asked questions. For more information about CloudMQTT, or if you need any support, please visit our support page.
CloudMQTT are managed Mosquitto servers in the cloud which provides lightweight methods of carrying out messaging using a publish/subscribe message queueing model.
Message queues provide an asynchronous communications protocol, the sender and receiver of the message do not need to interact with the message queue at the same time. Messages placed onto the queue are stored until the recipient retrieves them or until the messages times out. MQTT and Mosquitto are good to use with bandwidth sensitive applications.
Mosquitto implements the MQ Telemetry Transport protocol, MQTT, which provides lightweight methods of messaging using a publish/subscribe message queueing model.
With shared plans the version is based on when that particular server was created and the server selection is based on where space is available. On a dedicated plan, you can choose your Mosquitto version - currently versions 1.5 through 1.5.8 are available.
Your ports can be found in the control panel for your instance. On dedicated plans it's possible to change ports. Available ports are
| Instance type | Plain MQTT | MQTT over TLS | MQTT over Websockets |
|---|---|---|---|
| Shared | 1XXXX | 2XXXX | 3XXXX |
| Dedicated | 1883 | 8883 | 443 |
Yes websockets are supported. The port for websockets can be found in the console page for your instance. Websockets were enabled in April 2015, instances created before that might need to be recreated before websockets can be used.
Connect to the TLS/SSL port specified for your instance in the control panel.
If you connect by TLS/SSL, add --capath or --cafile and point it to a cert
store.
Our server certificate is always issued with a trusted root available in common trust stores, for details see
see the below section about CloudMQTT certificates.
Most OSes comes with it by default, so can you point to your default
trust/CA store. (example: --cafile=/etc/ssl/certs/ca-certificates.crt)
More information can be found at mosquitto.org, under Certificate based SSL/TLS Support. You also need to use the port for MQTT over TLS (see above).
Our server certificate is currently issued by
Thawte TLS RSA CA G1
with
DigiCert Global Root G2
as the root.
Previously, from 2022-09-30 until 2023-09-11, our server certificate was issued by
Thawte RSA CA 2018
with
DigiCert Global Root CA
as the root.
Heads up The signing root CA may change in the future. Please do not hard code the root CA in devices you cannot easily update. We recommend you to use custom domain and certificate for any device where you need to embed the signing root CA.
If you don't have the required root certificates in your CA trust store you can download them from the above
crt.sh
links.
History of certificate changes
All paid plans support custom certificates. With a custom domain pointing to the instance you have the ability to acquire and upload your own certificates. This ensures you control the renewal process.
This is especially important if you deploy devices without a trust store as our certificate can be rotated in the future.
All plans are billed by the second, you can try out even the largest instance types for mere pennies. As soon as you delete the instance you won't be charged for it anymore, i.e. if you had a Loud Leopard (for $99/month) running for 15 days, then you will only be charged $49,5.
Billing occurs at the end of each month, and you are only charged for the time an instance has been available to you.
A connection is an active TCP connection from your application/device to the Mosquitto broker. If two devices connected to the broker, they will consume two connections.
The ClientId is an identifier of the MQTT client connecting to a MQTT broker. The value could be any generated ID, and the ClientID should stay unique for the client.
Only one client with a given ClientId can be connected at one time. If one client is already connected, that client will be disconnected and the new client will get a connection.
The ClientId is chosen by the client. Preferrably something that is readable and identifies the devices e.g. my-phone, temperature-sensor-pool.
Does CloudMQTT support persistent clients?Yes, we support persistent clients. However, persistant messages are kept in RAM, so you cant have to many. Memory is dumped to disk as a backup, but RAM is still what sets the limit for persistant messages.
No, we do not support MQTT-SN.
No. We don’t provide any reseller discounts at this moment.
No. There is no shipping cost since the service is shipped electronically.
No. The service is non-returnable.
You can choose to pay through credit card (due on charge date) or via wire transfers (NET15). If you would like us to enable manual invoicing via wire transfer - send us an email once you have added all information and we will enable it for you. Please note that we don’t accept checks.
The service will be provided off-premise in a data center and region chosen on behalf of the customer. The data centers and regions currently provided can be found at the bottom of this page: https://www.cloudmqtt.com/plans.html.
Our billing is pro-rated, which means that our customers only pay for the time the service has been available to them and that the payment is done the month after delivery. Thus, you won’t receive your first invoice when the account has been created, you will receive it in the beginning of the upcoming month.
No. It’s very common that our customers change their plan while they are using our service, therefore it’s not convenient to pay for a year upfront.
No. We don’t need any documents with signatures from you.
No. Our active subscriptions are running until they are deleted. The reason for this is that we don’t want to delete our customer’s data when they have an active subscription. So for example, if you’re a reseller and has provided us with a PO that concerns two months usage of our Happy Hippo plan, then you’re responsible for deleting the plan after the two months have passed. Otherwise, we will charge you for the upcoming months.
We have a customer using your service with an active subscription and PO. Now it wants to create one more subscription. Should we extend the current PO or issue a new one?
It’s best to extend the current PO. If you need to have two separate PO’s for the subscriptions, you need to open a new account in order to make the subscriptions be billed separately.
Go to https://customer.cloudmqtt.com/login and enter your email address. Fill out all your information in the billing section, such as billing address etc, billing email etc. Please note that it’s important that we have your billing information registered and not the end-customers information, since you are our direct customer and not the end-customer.
The PO number can be specified in the billing section under “billing notes”. Or send it to us, and we will add it for you.
You are free to create and delete instances once the billing information is set up. It’s up to you and the end-customer to decide who of you that will create the subscription specified in the PO.
Invite the end-customer to the account via https://customer.cloudmqtt.com/team so that he/she can start using the service.
Change the role of the person that created your account to “Billing Manager”. By doing so, you can access all invoices of the account and update the billing information. But you will not be able to edit the customer's subscription. See more information here: https://www.cloudmqtt.com/blog/manage_cloudmqtt_instance_access_permissions_with_acl.html.
Yes. You can read more here.
No separate agreement is required. Our Data Processing Agreement (DPA) for GDPR is an exhibit to our Terms of Service. Thus, our business relationship is automatically covered by a DPA when signing up for an account.
You have the right to see what personal information 84codes AB holds about you. You are entitled to be given a description of the information, what we use it for, who we might pass it onto, and any information we might have about the source of the information.
A subject access requests should be made via email to compliance@84codes.com
You as data controller decide for yourself where you want to host your data by choosing data center and region of the data center. The data will not leave that region, unless you choose to move it. In CloudMQTT’s role as data controller, we may collect and store contact information, such as email address, and physical address, when customers sign up for our services or seek support help.
We are proud to be compliant with SOC 2 by AICPA. We have been audited against the Security (common criteria) and Availability Trust Services Criteria.
Our SOC 2 Type 2 report can be obtained under an NDA per request. Please send an email to compliance@cloudmqtt.com.