Goodcloud always goes through VPN when WG-VPN is on, regardless of the setting

I tested on Opal with firmware 4.3.6 RC2.

The setting “Services from GL.iNet use VPN” has no effect.

The router IP as shown in Goodcloud is always that of the VPN while the VPN is active. This causes issues with web access to the router through Goodcloud, presumably because the VPN interferes with the rtty protocol you use for this purpose. The web access login links already look abnormal to begin with, like so:<device_id>/

This results in displaying a blank web page.

Please look into how to make the setting to bypass VPN for GL services work as described.

Confirmed that bug, only happens on Opal, now fixing it

Cool, I would appreciate a heads-up when the fix becomes available in the form of a nightly snapshot.

1 Like

Any luck with the fix yet?

Yes, the code has been merged into the master. I hope a snapshot will be available soon. If that’s too long I can compile a test firmware for you.

I would appreciate that if you think it the next snapshot might take more than one or two weeks.

Any update with the fix?

Is there already a firmware with this problem fixed?

I would say no because there have been no new releases since Aug 24.

Sorry for missing this, I uploaded the RC firmware for testing:
@bmatos @danielg

I updated to Version: 4.3.7 release1 and I have problems.

With the Wireguard client activated I cannot access the panel through GoodCloud.

The real IP is also leaked instead of displaying the VPN IP.

I tested and found a bug:
It needs to toggle “Services from GL.iNet Use VPN” after turning on goodcloud. We’ll fix it soon.

But I didn’t reproduce the leak real IP issue, and I can access the panel through GoodCloud.
It will take some time for the cloud to reconnect, is that “leak” staying forever?

I have already activated Services from GL.iNet Use VPN and the problem remains.

The leaked IP is permanent.