Pylon is always disconnected

[john-light]

I updated to 0.6.8 using frame_0.6.8_amd64.deb on Linux Mint and I cannot get Pylon to connect to Ethereum mainnet. This is what it shows whenever I try to get it to connect:

Worth noting that the same thing happens for all other chains that use Pylon. However when I connect to Rootstock via the custom RPC URL that I have added, it connects as expected. So the issue seems to be with Pylon, specifically.

[mholtzman]

thanks for reporting this. are you still seeing this behavior? I'm able to connect to Pylon with no issues but there might be something about your setup so want to check if you're still seeing it before attempting to reproduce it

[john-light]

@mholtzman thanks for following up. this is still happening. is pylon possibly blocking vpn ip addresses? (I'm not in a position to test without a vpn right now, will check and report back later)

[mholtzman]

@mholtzman thanks for following up. this is still happening. is pylon possibly blocking vpn ip addresses? (I'm not in a position to test without a vpn right now, will check and report back later)

no, it shouldn't be blocking any addresses. I'm not seeing any issues on the server side or with individual connections -- can you let me know when you try without a VPN just for another data point?

[platschi]

Noticing the same when running Frame on a laptop, after waking up from sleep all networks are disconnected. Restarting Frame does not solve the issue, only a full system reboot helps. On latest macOS and Frame version.

[john-light]

can you let me know when you try without a VPN just for another data point?

@mholtzman I tried two different scenarios, here are my results:

Scenario 1: Opened Frame with no VPN on. Pylon connected without issue. I turned on VPN while Frame was still open, and turned Pylon off then back on again. Pylon showed Disconnected for a few seconds, then Connected. I turned Pylon off and on again a few times to check behavior, got the same result.

Scenario 2: After getting Pylon to connect with VPN on in Scenario 1, I closed Frame and put laptop to sleep. After waking the laptop, I made sure VPN was still on and started Frame. Now Pylon shows Discoonnected and will not connect.

So it seems like the VPN being on has something to do with the connection issues. But the exact behavior is inconsistent.

[mholtzman]

@platschi are you using a VPN as well?

[platschi]

@platschi are you using a VPN as well?

No VPN, just normal connection.

/edit: Actually noticed I have iCloud Private Relay turned on. Will test it without being on.

[3cl1ps]

got the issue here, not poosible to connect to any chain (except xdai?!), pylon or public rpc same result.
rebooting did the trick.
I'm on ubuntu last version, last version of frame.
connected by default with tailscale.