That sounds excellent - I’ll definitely give it a try!
1 Like
Interesting enough, I just tried to ping the IP 52.49.107.93 which is used by some of you guys to resolve the issue - all pakets are lost. I am situated in Germany. Guess redirecting the DNS will be no solution for me.
Add:
Even ping pakets to the IP are lost, rerouting the DNS does work here in Germany as well. Used the HA Dnsmasq suggestion of tesamu2 above. Thank you for that!
1 Like
Not all services are configured to respond to ICMP (ping) requests. It’s not a way to be certain if a service is up or not.
4 Likes
Hello, here “Portugal” also stops working…
2 Likes
My Heatpump / Melcloud also stopped working here in Ireland last week. Like everyone else I was initially stressing and resetting etc. Just about to call the installation company when I found this thread. I rang the local Mitsubishi office this morning and they have no knowledge of the issue. She said they had no issues with Melcloud. She started to ask me if I had changed ISP etc … So I have sent her the link, and she said the engineer will call me back after he came out of a meeting. I am still waiting. They appear to be managing it very poorly.
2 Likes
Just got this message in my MELCloud. So maybe we soon are up running normal again 
Unfortunately that doesn’t mean anything. They have been putting it at various interval since the 18th
2 Likes
So I just got a callback from Mitsubishi Ireland and he was quite helpful. He acknowledged that there has been an issue, but he hoped that it would be would be back online this afternoon. He did not promise, and he is not directly involved with the work for sure, and I am not sure if it would be potentially up for all geographies.He mentioned that part of the work was migrating a large number of devices onto a newer platform and there may have been issues there. So, although there are no guarantees, it is a little hopeful.
2 Likes
Well, I honnestly think he has no insight whatsoever and was just trying to get rid of you. But I guess we’ll see
3 Likes
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.