-
lyza
hey y'all. I've been having intermittent issues with the GUI not connecting to monerod since the last network upgrade. The 0.15.0.2 update didn't really fix it. looks to me like monerod is running without errors, but the Monero GUI still can't connect to it. The issue is intermittent -- it sometimes works, and I can often get it working after it
-
lyza
stops by rebooting. This is (or is supposed to be) a 24/7 p2p node
-
lyza
anyway, I'm happy to pass along anything that might be useful. logs, etc
-
selsta
lyza: Are you using simple mode?
-
lyza
no
-
selsta
Can you go to Settings -> Node and check if you have something entered in the bootstrap address / bootstrap port textbox?
-
lyza
they are oth blank
-
lyza
both*
-
selsta
ok, you are starting the daemon separately?
-
lyza
well I've tried letting the GUI do it, and I've also tried doing it separately in its own console window
-
selsta
Can you try the CLI wallet and see if it has the same issue?
-
lyza
the log in the GUI prints a lot of "Error: Couldn't connect to daemon: 127.0.0.1:18081" despite the fact that the daemon is running seemingly without errors
-
lyza
I tried the CLI wallet awhile ago but sure I'll give it another spin
-
selsta
I haven’t read any similar reports so I wonder if it is something on your system, anti virus or something similar.
-
lyza
CLI doesn't connect to daemon either. I suppose it could be my system, but the issue certainly seems to have corresponded with the upgrade. I haven't changed much of anything else
-
lyza
aaaaand the GUI just connected
-
selsta
can you try to use a remote node?
-
selsta
e.g. node.xmr.to:18081
-
lyza
sure one moment
-
lyza
weird how creating a TX sometimes takes 10s of seconds, other times it's almost instant.....
-
lyza
+selsta: xmr.to timed out but I was able to connect to the remote node at opennode.xmr-tw.org:18089
-
selsta
no connection problems?
-
lyza
nope. I think I may have figured out the issue, though. It seems to not be working specifically when the ProtonVPN app is running
-
lyza
but two things. first, I have ProtonVPN on Split Tunneling mode, so it should only be impacted two apps, neither of which are Monero. And second, I should still be able to connect to the local node even if I'm on a VPN? I've tried opening / closing ProtonVPN a few times now though and it seems to be what's causing the issue
-
lyza
If I connect to the VPN AFTER the wallet is open and connected to the daemon, that's fine, but it stops it from establishing a new connection if the VPN is running when I try to open a wallet
-
selsta
sorry I don’t know what the ProtonVPN is doing exactly.
-
lyza
that's fine, I wouldn't necessarily expect you to. and I was more looking to provide hopefully useful feedback than to get particular help.
-
lyza
seems like this could be an issue with the OS or ProtonVPN, but I don't know enough to say. I can say that Monero seems to be the only app that's been adversely affected.