Silly user nearly got phished because she was using bing and clicking on the first link without reading it.
She only stopped because the login page got flagged by our system as not secure.
When I backed out to the search results and made her read them she couldn't tell which one was real, so I had to search her emails for the original link she got sent.
Did I mention this was for a secure Dropbox for financial auditing?
And she doesn't actually know where shes meant to send our sensitive financial information...
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality
Anya is LIVE right now
FREE
Free to watch • No registration required • HD streaming
I just solved a mystery! For weeks, my authenticator app wasn't working. It turned out that I had somehow fatfingered my phone's time settings so that it wasn't automatically trueing up its clock with NTP, and was gradually losing a few seconds every week. Yesterday, I noticed that my phone was 3 minutes fast (when I tried to check in for a Southwest flight 24h in advance to get a good seat, and the system wouldn't let me check in). Later, I dug into the time settings and noticed that NTP was off. That meant that my phone was generating OTPs based on a timestamp that was 3 minutes off, which means that my OTPs were three minutes in the future and were failing at 2FA challenges. Now that my clock is back to accurate, Authenticator is working again.
Some of the things clients complain about are so bizarre. Like buddy, the length of time it takes for a credit card authorization to drop off your account is not controlled by me--please contact your fucking bank.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality
Anya is LIVE right now
FREE
Free to watch • No registration required • HD streaming
Tailscale will expire your devices' keys every few months by default, and I didn't realize my home server had expired until I couldn't connect to it from outside the house and saw on the admin console that it was offline and expired. I turned off key expiry and it was still offline. Okay, gotta log back in on the server itself. Fine.
When I got home, I TTYed into the server and I believe this is the order of events: I ran "tailscale up" to log back in. I checked my torrent client which is bound to the tailscale tunnel since I've only been able to get Mullvad to work on that device through Tailscale, and it still wasn't active. While I was trying to diagnose that, I ran "tailscale update" to update the version. I believe this is where the harder to solve problem happened.
While TS was updating itself, I realized the issue with the torrent client was that I had only joined the TS VPN but I hadn't connected to the Mullvad exit node. This is where the stupider problem happened, because you have to specify that you want to leave LAN access open when you connect to an exit node every time, and I forgot to do this when I used TTY over LAN to tell my headless server to connect to the exit node. Fortunately I got access back by removing the server from my VPN group and rebooting.
When the server was back up, responding to commands, and reauthorized on my TS VPN, I gave the appropriate command to connect to the Mullvad exit node and it gave an error. I thought I had selected the wrong address and told it to list available exit nodes, and it said no nodes found. This was the harder problem to solve. Rebooting didn't do it, it was already the most recent version. I had to leave it for a few days.
While I was trying to find a post online explaining why I couldn't find Mullvad exit nodes even though the device was authorized in my account to use Mullvad, I remembered that the last time it worked might have been before I updated the version. While I was wondering how to go about it back, I noticed that the update command in TS was flagged as "beta" and had a warning that it might not work correctly. I had Apt uninstall and reinstall Tailscale and everything worked correctly and I was finally back to normal.
