ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
Cheyenne Isa ₿8d ago
Hi @Tim Bouma #safebox, I'm writing to report an issue that I deliberately tested to assess the wallet's reliability. For over a week now, I've been seeing the 502 Bad Gateway error (nginx/1.24.0) on both Wi-Fi and 4G/5G. I purposely didn't notify you right away, to see if the service would recover on its own or if someone else would report it. Instead, it's still down. This makes me think that: · The server I'm on (or where the wallet is hosted) lacks auto-restart mechanisms or monitoring. · I'm probably the only one (or among the few) actively using the wallet, otherwise someone else would have already opened a report. I appreciate your past willingness to restart the server, but this test made me realize that the wallet isn't truly reliable: if you were unreachable tomorrow, the funds would remain stuck. I wanted to give you this feedback, also because I have about 4000 sats stuck there and, beyond the monetary value, it's a matter of trust. Do you have any plans to make the system more resilient (e.g., auto-restart, monitoring), or is this a project you only maintain "on call"?
💬 1 replies

Replies (9)

Tim Bouma8d ago
Is that the getsafebox instance?
0000 sats
.8d ago
Hey, yes my getsafebox dot app wallet doesn't allow me to log in with my key at this time either. I too have some 4,000 sats there that I want to send you.
0000 sats
Tim Bouma8d ago
Try now. You should be live. You will need to log back in with your access key, your funds are still there. If you have forgotten your access key, pleas dm me. P.s be prepared for a very different experience
0000 sats
Tim Bouma8d ago
Try with your old access key, balance should be restored
0000 sats
.8d ago
Looks like it works, still doing a few tests. Thank you sir!
0000 sats
SSage8d ago
Glad it's working again mate. Did the old key do the trick or was it something else?
0000 sats
Cheyenne Isa ₿7d ago
🤔 instance? I don't know 🤷🏻‍♀️ but the positive thing is that he has now changed the message to: "Internal Server Error"
0000 sats
Tim Bouma7d ago
Fix coming… thx.
0000 sats
Tim Bouma7d ago
It should be fixed now. System was choking on browser cookie from old instance. Upon error, it will force a logout instead of throwing an error. Thanks for catching this!
0000 sats