I found that it was caused by an old application. After I deleting all of them and creating a new application, the issue no longer occurs.
Discussion
Is there a way to not lose my local relay?
And by application, do you mean aegis or applications in the signer? Because I created new ones multiple times when we were troubleshooting issues
I mean the applications created on the home page
Yeah I already created multiple new ones when we were troubleshooting issues. On this build
And I still have the other issue of the signer being offline…
That’s so strange — does your relay log show any OS errors?
I didn’t try it since the other time since I just get the offline message. Let me try with another npub
nostr:npub179e5zckwq9vqsenc8ha9qv7p9vxwq20cq526ac67prts8kc4khmqu50zj8 is the other npub is already signed in to Nostur, should I sign out before signing in with the signer or it doesn’t matter? I have no idea but just thinking of things I’m doing, maybe it creates an error?
I logged into it. Tried to create a note. Got the error right away. I sent the logs via DMs
Thanks, it seems the relay is working normally and there are no errors. 🤔
I’m connecting through a vpn and with Nostur. Error has to be created by one of those 2 things
I just checked the vpn, it’s connected. This is what I see. Pfp and follow list aren’t populating either
In this case, does the local relay work normally?
Ah I forget it messes with my relays when I add/delete a new account 🥴
Yes local relay working fine now that I setup the relays again
Thank you, I will look into the signer issue
I was paying attention to the signer these past few hours. It seems I’m getting many connection closed messages in the log. I have to restart to fix it. (And then the notes get broadcasted to aegis)
nostr:npub179e5zckwq9vqsenc8ha9qv7p9vxwq20cq526ac67prts8kc4khmqu50zj8 sent you an example of connection closed log just now. Maybe it has something to do with what I see with the signer too. If connection is closed, can’t sign events
I saw an IO error in your logs. It seems to happen more frequently when the VPN is enabled. I’m still looking for a way to resolve this.