haha … maybe …
Theo from Germany here. Installing AdGuard in HA, re-routing melcloud.com to 52.215.226.151 and configuring FritzBox solved my problem with 4 HVACs
Thanks to the community
I’ve just done this and it works! Thanks very much for your help, much appreciated.
1 Like
Hello, same problem in France.
Does anyone know how to do this DNS configuration on a Bouygues router please?
You can’t. But let’s hope the issue is almost over, it’s benn going on for more than 4 days already…
1 Like
Lol just got a reply from Alklima BV (I think they manage MELCloud for the Netherlands?). It’s in Dutch, but it says:
We expect it to be solved within a couple of days
Zoals het er nu naar uitziet verwachten we dat het met een aantal dagen is opgelost.
They are one of the few that have an official page regarding this issue, which only got updated today
2 Likes
Germany still down
I phoned to Spanish support and they told me they were trying to resolve the melcloud problem. Unbelievable that after almost one week a so big company can not solve the problem!
It’s still not working, but the curl command yields a different result:
$ curl -v http://production.receiver.melcloud.com/
* Host production.receiver.melcloud.com:80 was resolved.
* IPv6: (none)
* IPv4: 52.211.2.220, 52.209.44.196, 54.72.127.44
* Trying 52.211.2.220:80...
* Connected to production.receiver.melcloud.com (52.211.2.220) port 80
> GET / HTTP/1.1
> Host: production.receiver.melcloud.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 301 Moved Permanently
< Server: awselb/2.0
< Date: Mon, 22 Apr 2024 15:13:55 GMT
< Content-Type: text/html
< Content-Length: 134
< Connection: keep-alive
< Location: http://production.receiver.melcloud.com:443/
<
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
</body>
</html>
* Connection #0 to host production.receiver.melcloud.com left intact
uffe@JUMPER ~ $ curl -v https://production.receiver.melcloud.com/
- Trying 54.72.113.86:443…
- Connected to production.receiver.melcloud.com (54.72.113.86) port 443 (#0)
- ALPN: offers h2,http/1.1
- TLSv1.3 (OUT), TLS handshake, Client hello (1):
- CAfile: /etc/ssl/certs/ca-certificates.crt
- CApath: /etc/ssl/certs
- TLSv1.3 (IN), TLS handshake, Server hello (2):
- TLSv1.2 (IN), TLS handshake, Certificate (11):
- TLSv1.2 (OUT), TLS alert, unknown CA (560):
- SSL certificate problem: self-signed certificate in certificate chain
- Closing connection 0
curl: (60) SSL certificate problem: self-signed certificate in certificate chain
More details here: curl - SSL CA Certificates
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Adding to curl to accept selfsigned cert gets a better response if anyone want to try…
curl -k -v https://prod…
And testing the https link and accepting thats the cert is broken you will see Melcloud greetings…
I.e.
Wonder why there is a redirect on http → same host but on 443 ( normal https )
and then have a broken cert on the 443 port normally supporting https…
will be interesting to see what they continue with…
1 Like
Same here … but when connecting to MelCloul on the computer, I got a message from Mitsubishi that they are experiencing problems since 17/04 …
And seems to be worldwide :
https://www.igen.fr/domotique/2024/04/mitsubishi-illustre-le-probleme-de-la-domotique-qui-depend-du-cloud-143091
1 Like
This forum is English speaking, please refrain from posting links in other languages. And yes, if you browse this topic, it is definitely worldwide.
1 Like
It’s definitely looking a lot like they’re struggling with TLS basics here 
MELCloud is working again here
It seems to be coming back slowly here too (in France). The app seems to behave weirdly (more than usual I mean) but I have sent commands from Home Assistant ! 
EDIT : well, it’s the case for two of my three units at least. Better than nothing, I guess…
1 Like
It does indeed work again, but damn it’s slow. They updated some stuff, now when you send a command, it says “Your changes will take effect at approximately: xx:xx”. Which is like 1 to 2 minutes in the future. Are they applying some kind of API throttling in order not to DDOS their own environment with all these units coming back online?
1 Like
Working in Portugal again
Works for me too now (France). I didn’t change anything to my WiFi or router, I just waited… Melcloud seems to respond normally. I even managed to turn on and off my unit by vocal commands with Alexa as I usually do!