Step 1: Open TRONSCAN and click LINK WALLET, then click IMPORT A WALLET.
Step 2: Enter your private key and click SIGN IN
Step 3: You'll see the Login Success notification at the bottom right corner.
Step 4: Click WALLET > Account to enter your account page.
Step 5: You'll see the details of your account.
Comments
14 comments
Tanku
Tankyu
Hi, I am trying to access my wallet via private Key (The Link Wallet functionality) at the moment this option has been removed.
My TRX are frozen, so I cannot access them on a wallet and I need to unfreeze them on TronScan.
Can you please advise ASAP?
Hello in new version tronscan have no option IMPORT WALLET, have only Tronlink and Ledger, so i cant download my file wallet from my computer and get access to my TRX!!!
WHAT i need to do?
Having same problem as the two comments above me. There is no option LINK WALLET - IMPORT A WALLET anymore, so I am not able to sign in using my private key. Please advise.
Having same problem as the three comments above me.
There is no option LINK WALLET - IMPORT A WALLET anymore, so I am not able to sign in using my private key. Please advise. Plz~
Like the comments above, I have also submitted a ticket with no answer until today. I thought we were moving to a decentralised system where no one can lock us out of our funds. So far, I am really worried that Tronscan has just done that. We need to access our funds and we have our private key. The Tronlink wallet does not even support us putting our private key.
Having same problem as the three comments above me.
There is no option LINK WALLET - IMPORT A WALLET anymore, so I am not able to sign in using my private key.
I am concerned, as they are all my savings. What do I need to do?
Please advise. Plz~
Guys, I was stuck like you all and have two comments above and ticket open for more than a month. All I can say, thank goodness, there a solution and we do not need any of Tronscan team help!!!
Download your tronlink on mobile (Not Chrome Ad On) and on the mobile app you can access your tokens via your private key.
Good luck
Thanks for the tip! In the app talk about enter the key offline, how did you do? I'm in doubt!1
Feb '20
On 2020-02-29 UTC, Let’s Encrypt found a bug in our CAA code. Our CA software, Boulder, checks for CAA records at the same time it validates a subscriber’s control of a domain name. Most subscribers issue a certificate immediately after domain control validation, but we consider a validation good for 30 days. That means in some cases we need to check CAA records a second time, just before issuance. Specifically, we have to check CAA within 8 hours prior to issuance (per BRs §3.2.2.8), so any domain name that was validated more than 8 hours ago requires rechecking.
The bug: when a certificate request contained N domain names that needed CAA rechecking, Boulder would pick one domain name and check it N times. What this means in practice is that if a subscriber validated a domain name at time X, and the CAA records for that domain at time X allowed Let’s Encrypt issuance, that subscriber would be able to issue a certificate containing that domain name until X+30 days, even if someone later installed CAA records on that domain name that prohibit issuance by Let’s Encrypt.
We confirmed the bug at 2020-02-29 03:08 UTC, and halted issuance at 03:10. We deployed a fix at 05:22 UTC and then re-enabled issuance.
Our preliminary investigation suggests the bug was introduced on 2019-07-25. We will conduct a more detailed investigation and provide a postmortem when it is complete.
32
Revoking certain certificates on March 4
4593
Revoking only affected certificates
830
DNS failures (SERVFAIL, timeout) for domains using Network Solutions/Web.com/worldnic.com nameservers
198
Force renewing of certificates with cert-manager
178
Help to force new certificat not work?
125
5 more
created
Feb '20
last reply
Mar '20
3
replies
Phil
Let's Encrypt staff
1
Mar '20
Per the FAQ at Revoking certain certificates on March 4 1.3k :
In order to complete revocations before the deadline of 2020-03-05 03:00 UTC, we are planning to begin revoking affected certificates at 2020-03-04 20:00 UTC (3:00pm US EST). Please continue to renew and replace affected certificates in the meantime. If there are any changes to this start time, updates will be provided in this thread. Thank you all very much for your patience, understanding, and help as we work through this issue.
11
josh
ISRG Executive Director
Mar '20
After learning about and remediating a bug in our CAA checking code [1] on 2020-02-29 UTC (the evening of Friday February 28, U.S. Eastern time), we announced that we would be revoking approximately 2.6% of our active certificates that were potentially affected by the bug, totalling approximately 3 million certificates [2].
We announced the plan to revoke because even though the vast majority of the certificates in question do not pose a security risk, industry rules require that we revoke certificates not issued in full compliance with specific standards. These rules exist for good reasons. We work hard to comply with them and have an excellent track record for doing so.
Since that announcement we have worked with subscribers around the world to replace affected certificates as quickly as possible. More than 1.7 million affected certificates have been replaced in less than 48 hours. We’d like to thank everyone who helped with the effort. Our focus on automation has allowed us, and our subscribers, to make great progress in a short amount of time. We’ve also learned a lot about how we can do even better in the future.
Unfortunately, we believe it’s likely that more than 1 million certificates will not be replaced before the compliance deadline for revocation is upon us at 2020-03-05 03:00 UTC (9pm U.S. ET tonight). Rather than potentially break so many sites and cause concern for their visitors, we have determined that it is in the best interest of the health of the Internet for us to not revoke those certificates by the deadline.
Let’s Encrypt only offers certificates with 90 day lifetimes, so potentially affected certificates that we may not revoke will leave the ecosystem relatively quickly.
The following certificates have been, or will be, revoked prior to the compliance deadline at 2020-03-05 03:00 UTC (9pm U.S. ET tonight):
1,706,505 certificates that we are confident were replaced during the incident period
445 certificates that we treated as highest priority for revocation because, at the time we found the bug, they had CAA records that forbid issuance by Let’s Encrypt.
We plan to revoke more certificates as we become confident that doing so will not be needlessly disruptive to Web users.
I would like to thank the Let’s Encrypt team for tirelessly working to resolve this situation in the best way possible. It involved incredible effort and I couldn’t be more proud of what we have been able to get done in such a short amount of time.
[1] 2020.02.29 CAA Rechecking Bug
[2] Revoking certain certificates on March 4 498
14
...and the opportunists don't wait
126
Revoking certain certificates on March 4
52
Sometimes it's required to break the rules - and to change these
45
jsha
Let's Encrypt engineer
Mar '20
We’ve posted another response at https://bugzilla.mozilla.org/show_bug.cgi?id=1619179#c7 915 with more detail as to the number of currently-revoked certificates and the timeline for expirations of affected certificates.
8
Sometimes it's required to break the rules - and to change these
53
Revoking certain certificates on March 4
11
SSL Not Working for Old or New Domains
3
Reply
Suggested Topics
2020.06.08 Delegated OCSP Signer Expiration for Alternate Chains
0
Incidents
Jun '20
2020.09.08 Failure to renew OCSP responses within acceptable timelines
0
Incidents
Sep '20
2020.12.22 Failure to audit log subscriber certificate OCSP updates
0
Incidents
Dec '20
Questions re: OpenSSL Client Compatibility Changes for Let’s Encrypt Certificates
31
Issuance Tech
23d
Certbot error on windows server 2008 R2 sp1
5
Help
18d
Want to read more? Browse other topics in
Incidents
or view latest topics.
hey~wissam
Can you tell me the details?
Be very careful with the nick name tronlink officials It seems to be a scam to steal your TRONSIf anyone have any problem please contact with our Tron help support. We will contact with you within 10 minutes . Our Help support link below. thanks
https://forms.gle/SvmQPW5tZh77KX1j6
Please sign in to leave a comment.