As of a few minutes ago, when I open anki on desktop or ios, it fails to sync with the following error:error sending request for url (): error trying to connect: tcp connect error: Connection refused (os error 61)<U+2069>
This morning I had full functionality of one of my Anki profiles as I reviewed the description I wrote for a deck I shared. When writing an email to share the link to the shared deck’s webpage, the webpage didn’t load and gave me this error:
When opening the Anki app on my computer, I can see, browse, and edit the deck, but when I tried to sync it I got: (os error 10061) [I didn’t take a screen shot]. I first tried to see if the Anki app was malfunctioning on my computer so I checked if I could sync my cards on my phone — which was successful, but my phone is connected to my other account. I switched profiles on my computer and I could still sync cards from that account. I switched back and the problem remained. I then switched accounts on my phone and got an error like the computer. I then looked up (os error 10061) and updated my Anki and checked and temporarily turned off my default Microsoft Defender firewall when trying to sync. But it didn’t help. Now I’m worried something is wrong with this account. I admit I’m not the most knowledgeable about fixing issues like these, but as a test, I changed the password on the malfunctioning account. I relogged in on my computer, but now I get (os error 10060) when trying to sync.
One of AnkiWeb’s servers suddenly went offline, and won’t restart. I have reported the issue to the data center, and I’m waiting for them to investigate.
I am also having the same problem. I tried using my phone’s hot spot, uninstalling and reinstalling anki app on my laptop and that did not work.
Today I also created a second profile and when I went to AnkiWeb it surprisingly did not have any issues or error messages when loading the second profile. I am able to access this second profile and it seems like it makes some progress synching but much slower than normal. But there was always a connection error for the first profile.