Can't connect to mqtt server

Modifications
, , ,
1

Hello..

When we try to connect to mqtt42.victronenergy.com:8883 using InstallationId=61346 and Token, connection doesn’t return NotAuthorized error but immiadiately is disconnecting. Change of Token dosn’t help.

We can connect to VRM using the same Email and Token .

Could you check why mqtt server disconnect immidiately?

2

Assuming you enabled MQQT on VenusOS and uploaded the correct CA Certificate ‘Venus-CA’, should you not use login: ‘e-mail address’ and password ‘Token self-generated-token-in-vrm’ ? And for the subscribtions use your VRM Portal ID (as in ‘N/portal_ID/….). Did this work before?

3
  1. I don’t connect to VenusOS Mqtt, but to mqtt in cloud: https://github.com/victronenergy/dbus-flashmq
  2. I worked a lot of years. It stopped work yesterday at 18 (CET).
  3. For other users (including me, I also use Token) it is work very well
  4. It is not working for 2 users: InstalatioId=61346 and 166736
4

Strange. I was aware of only two ways to connect to the external broker farm:

  1. To port 443 with the cerbogx internal credentials that are used to get the W msgs directly (for instance DESS schedule writes to the dbus)
  2. To port 8883 with email/token to get N msgs by proxy, msgs that originate from the cerbogx with its own mqqt broker enabled (also accessible without credentials on localhost).

Never knew there is, or was, another way. I do know things are being worked on at the cloud end, for a week there were strangely regular missing DESS updates, that seem to have returned by normal yesterday afternoon. I could not get anybody to have look at the logs for me though. Chances are both your and our experience is related to the same thing.

Sorry cant be more helpful than suggest you try other credentials sets or ports until somebody picks up the phone so to say.

Looking at GitHub there is some activity noticeable, I bet you a beer it is all connected. Deprecate VRM username and password authentication · victronenergy/dbus-flashmq@f40cdc5 · GitHub

5

We noticed the first failure of your token at ‘2026-03-18 17:46:25.057 CET (+0100)’. The token in question (named ‘GbbVictronWeb’) was deleted a day earlier, at ‘17/Mar/2026:17:28:19 +0100’.

Providing your clients with new tokens will fix it.

6

Thanks. This message helped a lot

7

So you deleted your own token? Was that before you accidentally published that token here on the forum or after? Otherwise said, was that cause or effect?

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.