Still works here. Using version 3.5.1 (haven't updated it for years).
Comment has been collapsed.
Works for me on 3.6.2 (BETA). I get that error when I put up a lot of items to confirm. It takes a while to "Confirm All" and if you are impatient and close that window the error will pop up.
Comment has been collapsed.
Having this issue currently. Was using version 3.5.1, tried updating to 3.6.2 Beta.
If i have zero items on the market, it wont popup the error. If i have 1 (or more) item on the market, or 1 pending trade request i will get that error when i try to view the confirmation screen. If i have no items on the market, open the confirmation page, list the items, and then hit refresh on the confirmation screen, it will also pop up the error.
Errors by version:
WinAuth 3.5.1 - "The Request was aborted: Could not create SSL/TLS secure channel."
WinAuth 3.6.2 - "Object reference not set to an instance of an object"
Tested on two different computers with a direct copy of the program and same xml profile, both copies of 3.5.1 fail in the same manner. Both computers were Windows 7. Testing was done with .net 4.8 and 4.5.2 installed / uninstalled / reinstalled on one of the PCs. Tried rebooting. Tried turning off windows firewall. Im just about out of ideas.. only thing left to test is to maybe change IP addresses.
Were you ever able to resolve this issue? Have a few summer sale cards to get rid of before they expire, and dont think theres enough time to setup a new authenticator since I think steam might impose a trade ban of 7-14 days upon setting up a new device / authenticator?
Comment has been collapsed.
You mention you are using Windows 7, it works for me on Windows 10. Maybe that is the problem?
Comment has been collapsed.
I might be able to borrow a laptop with windows 10 on that to test with perhaps. Will have to try that and an IP change tomorrow if possible. Thanks for offering a bit of insight with regard to the platforms it does seem to be working on currently. The only thing i can think of is that some sort of security certificate expired in Win7 to cause a program that had been working just fine, to suddenly lose some functionality if still operating fine under a different OS.
Comment has been collapsed.
That's how it goes... things break for older OS forcing you to upgrade and move on to the new one. I don't think this is related to an IP change at all. When version 3.5.1 stopped working, I moved on to version 3.6.2 Beta and it's been working ever since. Good luck and hopefully it's as simple as needing Windows 10.
Comment has been collapsed.
Do you recall if you simply just copied the old winauth.xml from the old version to the new version, or did you fully setup the new authenticator from scratch and deal with a lockout? It was suggested that maybe the old authenticator's profile was corrupted in some fashion. Looking at it in a text viewer didnt reveal anything immediately obvious in that regard though. Just dont want to lock myself out if theres still a few things left to test.
Comment has been collapsed.
I used the gear icon -> Export to create a txt file inside a zip file (protected with password) on the older version that I later imported through the "Add" button in the newer version to have it working without locking myself out.
Comment has been collapsed.
I moved my install of 3.5.1 over to a Win10 computer, was able to access the confirmations page first try. Confirming them was slow and kept giving me 'cant confirm' errors. (Was also having trouble listing items this morning too so maybe theres a temporary Steam issue going on as well.) Seems that the issue with Winauth is probably a windows / encryption / certificate related issue. Fails to work on both Win7 computers, but 'fine' on Win10 despite no changes on the Win7 computers that would have caused it to stop functioning. Thanks for the feedback, probably wouldnt have thought to try it on Win10 without the OS comparison. May have to try SDA in a week and see if thats an alternative that will work in the place Winauth for Win7.
Comment has been collapsed.
Yes, it's slow sometimes due to Steam servers, but the smartphone app is way slower/clunkier. Nice that you got it working and a confirmed information where now we know for sure Win7 was the problem.
Comment has been collapsed.
I was kind of worried that removing and re-adding it would cause a 2 week timeout to trigger. Thanks for confirming. Do you know if its the removal of the authenticator that causes the lockout, or was it the addition of the new one? Id guess any change would cause it. But being able to drop back to email auth, wait a day for a trade to go through, and then re-add a mobile/software replacement auth method and sit on a 2 week trade lockout might at least make sure the summer sale cards dont go to waste. Thats a last ditch effort though, cant go back once ya start on that path im guessing.
Comment has been collapsed.
15,333 Comments - Last post 10 minutes ago by kolja300314
16 Comments - Last post 25 minutes ago by PhilBlank
8,416 Comments - Last post 1 hour ago by FranckCastle
58 Comments - Last post 1 hour ago by Tristar
46,801 Comments - Last post 2 hours ago by Megamind9
108 Comments - Last post 5 hours ago by sonatamyasa
345 Comments - Last post 16 hours ago by chillplay
25 Comments - Last post 1 minute ago by antidaz
15,079 Comments - Last post 1 minute ago by Operations
114 Comments - Last post 10 minutes ago by LastM
413 Comments - Last post 10 minutes ago by Gwynevere
598 Comments - Last post 21 minutes ago by adam1224
177 Comments - Last post 42 minutes ago by LuckyLana
10,343 Comments - Last post 48 minutes ago by JMM72
Comment has been collapsed.