Tried to switch to WiFi, restore factory setting from gateway, disabled firewalls,…
Enphase just turned off port 502 is mine conclusion.
And they don’t respond on several tickets made,…
Very frustrating and time consuming!
Enphase did reactivate port 502 in a 1h chat, mine system is back!
That’s great. I will try to contact them via chat then. Did they have an explanation for why it stopped working?
Here same issue. How did you contact Enphase? Through the Enlighten app?
Last vieuw days i also had this problem twice. I turnd the power off, and restarted Enphase. That workd. I also live in the Netherlands.
I had already restarted my Envoy, but it didn’t help me. I sent an email to Enphase.
Don’t send a mail, go to support and start a chat.
Explain the problem and refer to this document.
https://enphase.com/nl-nl/download/ac-coupling-victron-battery-inverters-using-modbus-tcpip
Hi,
I am located in Spain and I am experiencing the same issue. On 27/05/2026 (at approximately 19:00), my Envoy stopped working via Modbus TCP.
A few months ago, I experienced a similar problem and, on that occasion, restarting the Envoy resolved it completely. However, this time I have performed several restarts and have not been able to get it working again.
On 28/05/2026, I opened a support ticket with Enphase describing the issue, but as of today I have not received any response.
As a temporary workaround, I created a virtual PV inverter using Node-RED on my Cerbo GX in order to provide Victron with the PV production data.
The firmware version was 8.3.5289, but this morning (02/06/2026) I noticed that it had been updated to version 8.3.5528. Despite the update, the problem still persists.
When I scan port 502, it does not appear to be accessible. However, when I run:
nmap -sV -p 502 192.168.0.60
the port does not show as “closed”, but instead as:
502/tcp filtered mbap
For this reason, I believe the service is not closed but rather being blocked or filtered. It appears that some kind of filtering is preventing access to port 502, although at this point I cannot determine whether this is an intentional configuration change by Enphase or a system malfunction.
Hopefully, Enphase technical support will be able to clarify the situation.
Contacted Enphase support via chat. They said somehow the enphase system had reverted the modbus settings. It was applied again and I would see the data back again in the Victron system. Unfortunately no solar data yet.
Did see mine Enphase system directly after the “Find PV inverters” scan.
So I’m afraid you have to plan a new chat.
Ask to open port 502.
Figured out something.
After disconnecting the UTP cable and reconnect it the angry IP Scanner tool does see port 502.
Port 502 disappears at the moment Venus OS reconnects.
It is possible that, since the Enphase Gateway only allows a single Modbus TCP connection at a time, when another device is already connected it does not respond to port scans as if the port were open.
In that case, the port may appear as filtered or may not respond as expected during the scan.
You can try running the following command: nmap -sV -p 502 192.168.178.173
to see whether it returns any response or additional information about the service.
I can see that there is a response, since Nmap reports the state as filtered rather than closed. In my opinion, this suggests that the Modbus TCP service is still active, but it is not accepting new connections or is not responding to additional connection attempts.
If the device is limited to a single simultaneous Modbus TCP connection, this behavior would be consistent with an already established session.
And for this you should disconnect the UTP cable so port 502 shows up again and after reconnecting Venus OS is able to see the PV system.
I believe there is indeed an issue with Enphase, and that for some reason it is not releasing the connection in certain cases, continuing to show that a device is connected when in reality this is not the case.
I have tried disconnecting the UTP cable and plugging it back in, but the issue persists. I have also restarted the Gateway/Envoy, but that did not resolve the problem either. For this reason, I believe the only solution is for Enphase support to reset it remotely.
Maybe WiFi is still active and occupies the connection?
I don’t have WiFi enabled; I only use Ethernet. The fact that it failed a few months ago and was fixed with a reset, and that now several of you are experiencing the same issue, leads me to believe it is an Enphase problem. However, I still hope that support will get in touch to see if they can provide any explanation about it.