They said they fixed it, but it can take some time.. but so far not seeing much. I did get a ticket numer, so if they did manage to fix it, i will report the ticket number here. If anyone has a ticket number where they actually fixed it, then post it here for reference for others perhaps?
How can I install that nmap ?
nmap is on a mac, i assume your on windows. It does exist for windows though, Download the Free Nmap Security Scanner for Linux/Mac/Windows
Ok, thought you was running this on the GX device.
By the way, if port 502 is active but not visible, unplug the UTP cable and after reconnecting the first device polling should see port 502.
got this with nmap:
PORT STATE SERVICE REASON VERSION
80/tcp closed http reset ttl 64
443/tcp open ssl/http syn-ack ttl 64
502/tcp filtered mbap no-response
8080/tcp filtered http-proxy no-response
8888/tcp filtered sun-answerbook no-response
I contacted support again on Monday and they said, again, that port 502 was open on their end. They told me to check my firewall settings. Thing is. The Growatt modbus flow in NodeRED that I have running here, is of course also working with port 502, and that works flawless.
I am about to convert two string inverters to Victron MPPT’s but this shows me that Growatt has better support. They actively helped me to get modbus working. They even put an engineer on my ticket to verify that everything worked and that I was happy. After five (!!!) calls and emails I’m still not back with a working Enphase system.
I’m also impacted, also located in the NL. Firmware D8.3.5289.260415 (dc300). What is funny is that in the toolkit, the grid profile is selected but shows up with an orange exclamation mark like something is wrong.
D8.3.5528 here, but ofcourse after yesterday still same issue. No solar in vrm.
Mine system just miraculous got back (after scan PV inverters):
nmap gives:
PORT STATE SERVICE REASON
80/tcp closed http reset ttl 64
443/tcp open https syn-ack ttl 64
502/tcp open mbap syn-ack ttl 64
8080/tcp filtered http-proxy no-response
8888/tcp filtered sun-answerbook no-response
and gone 
PORT STATE SERVICE REASON
80/tcp closed http reset ttl 64
443/tcp open https syn-ack ttl 64
502/tcp closed mbap reset ttl 64
8080/tcp filtered http-proxy no-response
8888/tcp filtered sun-answerbook no-response
Wow this is ridiculous, I hope my system will just work as it did now for a few days already.
Hopefully Enphase will quickly fix this!
It just came back to live, hope now forever.
Port 502 now stays open!
just checked 502 has now the “filtered” state, PV system still visible.
Let see how long the data connection lasts this time
PORT STATE SERVICE REASON
80/tcp closed http reset ttl 64
443/tcp open https syn-ack ttl 64
502/tcp filtered mbap no-response
8080/tcp filtered http-proxy no-response
8888/tcp filtered sun-answerbook no-response
waited long enough, chatted twice with them, still no luck of seeing solar. Also rebooted the cerbo gx and the envoy.. there is nothing we can check ourself as it is a black box afaik. i want to be able to login and check it myself 
same issue here also Europe ( netherlands ) suddenly its gone.
I am still waiting for a response regarding this matter. The last email I received was on 06/09/2026, indicating that they were escalating the issue. My current status is as follows:
No access to Modbus TCP (502); I found that port 502 on the Enphase gateway is filtered, and there is no communication with the Cerbo GX. An important detail is that the Enphase gateway only accepts a single connection on port 502. I use the command nmap -sV -p 502 192.168.x.x (in Linux) to check the port status, and it shows: 502/tcp filtered mbap. The current firmware version of the Enphase gateway is 8.3.5528.
In my case, the idea behind using Modbus was to regulate the PV production power according to the price of grid surpluses, but after running several tests, I concluded that it is not viable. You can find more details at this link: Retour d'expérience sur intégration Enphase par Modbus TCP
Therefore, currently only PV production data is being retrieved, which I am resolving using Node-RED; it makes the request to the Enphase gateway and sends it to a virtual device. This way, it is working properly for me without Modbus TCP. It is a shame how Enphase’s implementation is performing, especially considering it is supposed to have official certification: https://sunspec.org/contributing-members/enphase-energy/
I am also affected by the Enphase Modbus TCP service access issue since June 10th. I reported the incident on June 11th. I chatted for an hour on June 16th without success. I sent another email yesterday, June 17th.
Currently, my gateway software version is D8.3.5528 (f9db90). My installation is located in France.
Still waiting for a solution.
I’m glad to see I’m not the only one affected by this issue.
Same issue here. Modbus stopped working on June 14th. The system is in the Netherlands. I started a chat on June 14th which didn’t get a response. On Monday 15th I got a mail regarding the chat and I filed my issue. On Thursday June 18th I called Enphase support and they remotely activated Modbus, they said. Couldn’t get the communication working, so checked with nmap on Friday and saw that port 502 was closed. Called Enphase support again and they informed me that this was an issue still not resolved, with many systems being impacted.
One thing I noticed while checking parameters of my system is the grid profile being used: Italy Copy of EN 50549-1:2019 RfG E02 Netherlands // Victron Extended Frequency//PEL 7kW. Why an Italian Copy of a Dutch grid code ?
Bonjour,
Je suis en France et j’ai le meme probleme que vous .
j’ai contacté enphase a plusieurs reprise pour enfin qu’ils me disent qu’ils travaillent sur le sujet.
j’ai eu une mise a jour de ma passerelle enphase hier soir ( 08.03.5422)
je fais des tests avec le scan modbus du cerbo gx
ceci dit pouvez vous me dire quelle ID avez vous , pour ceux qui ont la production qui est bien affichée , svp ?
je vous en remercie par avance
Hello,
I’m in France and I have the same problem as you.I contacted Enphase several times to finally get them to tell me that they were working on the subject.I had an update to my enphase gateway last night (08.03.5422)I am doing tests with the modbus scan of the cerbo gx .
That said, can you tell me what ID you have, for those who have the production which is clearly displayed, please?
I thank you in advance