You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Loaded anchor.toml configuration. You can use `--skip-config` to ignore this file.
# Signin to Anchor.dev `anchor auth signin`
| Please sign up or sign in with your Anchor account.
|
| Once authenticated, we can provision your personalized Anchor resources to
| power HTTPS in your local development environment.
- Copied your user code XFDX-KNDW to your clipboard.
- Opened https://anchor.dev/users/sign_in/cli?signup_src=lclhost in your browser.
- Signed in as sardarwkm@gmail.com.
| Let's set up fast and totally free lcl.host HTTPS!
# Setup lcl.host HTTPS Local Development Environment `anchor lcl`
| We'll set you up to use HTTPS locally in your browsers and other programs.
# Audit lcl.host HTTPS Local Development Environment `anchor lcl audit`
| We'll compare your local development CA certificates from Anchor and your local trust stores.
- Compared local and expected CA certificates: need to install 2 missing certificates.
# Initial System Configuration for lcl.host Local HTTPS Development `anchor lcl bootstrap`
| We'll configure your browsers and OS to trust your local development certificates.
- Checked diagnostic service on Anchor.dev: need to provision service.
- Entered hi-sardarwkm.lcl.host domain for lcl.host diagnostic certificate.
- Resolved hi-sardarwkm.lcl.host domain: success!
| Now we'll provision Anchor.dev resources and HTTPS certificates for you.
- Creating hi-sardarwkm [hi-sardarwkm.lcl.host, hi-sardarwkm.localhost] diagnostic resources on Anchor.dev… ⠋
The text was updated successfully, but these errors were encountered:
@Sardarwkm Sorry to hear you had problems with this. This type of error reflects a larger skew between the clock time on the local machine and our servers. If you check your machine and ensure the system clock is up to date before trying again, you should have better luck. Definitely let us know if that doesn't appear to be the case though.
Are there any additional details you would like to share?
Command:
anchor lcl
Executable:
C:\Program Files\Anchor CLI\anchor.exe
Version:
0.1.2 (windows/amd64) Commit: 021bf29c9ba180eb6ad62ae8438867c8d0dcd26b BuildDate: 2024-09-17T12:45:38Z
Arguments:
[]
Flags:
[]
Timestamp:
2024-09-22T11:58:32.6657939Z
Stdout:
The text was updated successfully, but these errors were encountered: