-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
X509 Certificate #11
Labels
bug
Something isn't working
Comments
it’s a temporary issue with haxelib certificates, sometimes this happens
but as far as I know, it’s only temporary
…On Mon, Sep 9, 2024 at 4:51 PM Qwertcool54 ***@***.***> wrote:
Describe your bug here.
i trying to install haxe libs i got this:
Command Prompt/Terminal logs (if existing)
X509 - Certificate verification failed, e.g. CRL, CA or signature check failed
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your
changes.
no
—
Reply to this email directly, view it on GitHub
<#11>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5VHQKUMRG524JQYR7C22E3ZVYC33AVCNFSM6AAAAABN5KV6PSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYTIOBZGQ4DAOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
ok |
if it doesn't fix itself, do the following https://files.catbox.moe/a6mfto.crt
|
it didn't work |
but I decided to download the libraries through Git, but it still doesn't work. |
Doesn't matter, it's already fixed itself. |
okay I was wrong, it's a bug with Neko (that's been dead for years now) HaxeFoundation/neko#196 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe your bug here.
i trying to install haxe libs i got this:
Command Prompt/Terminal logs (if existing)
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no
The text was updated successfully, but these errors were encountered: