Skip to content
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

20240715 ERROR:OpenSSL3: Failed to load Legacy provider #1319

Open
vnasing opened this issue Jul 16, 2024 · 4 comments
Open

20240715 ERROR:OpenSSL3: Failed to load Legacy provider #1319

vnasing opened this issue Jul 16, 2024 · 4 comments

Comments

@vnasing
Copy link

vnasing commented Jul 16, 2024

2024-07-15 21:23:28 [CMaNGOS Auth server v0.18] port(3724)
2024-07-15 21:23:28

   _____     __  __       _   _  _____  ____   _____ 
  / ____|   |  \/  |     | \ | |/ ____|/ __ \ / ____|
 | |        | \  / |     |  \| | |  __  |  | | (___  
 | |ontinued| |\/| | __ _| . ` | | |_ | |  | |\___ \ 
 | |____    | |  | |/ _` | |\  | |__| | |__| |____) |
  \_____|   |_|  |_| (_| |_| \_|\_____|\____/ \____/ 
  http://cmangos.net\__,_|     Doing emulation right!

2024-07-15 21:23:28 Built on Jul 15 2024 at 06:27:39
2024-07-15 21:23:28 Built for Win64 (little-endian)
2024-07-15 21:23:28 Using commit hash(651d6a66134695c5e7a7a4762db2702e7a9ea9de) committed on 2024-07-15T05:42:16+03:00
2024-07-15 21:23:28 Using configuration file realmd.conf.
2024-07-15 21:23:28 ERROR:OpenSSL3: Failed to load Legacy provider


Windows version 0715 encountered an error while running, but in the same environment, version 0714 does not have this error

@Niam5
Copy link

Niam5 commented Jul 16, 2024

Update your repo, rebuild and try again. There is an update after the one you built that fixes this.

@Niam5
Copy link

Niam5 commented Jul 16, 2024

If your using the prebuilt ones from GitHub you will need to wait for it to build in about another hour or so.

@vnasing
Copy link
Author

vnasing commented Jul 16, 2024

If your using the prebuilt ones from GitHub you will need to wait for it to build in about another hour or so.

The pre built version of 20240716 has already resolved this issue.
I thought this mistake would continue indefinitely. I didn't expect it to be resolved so quickly.
Thank you very much for your reply.

@al3xc1985
Copy link
Contributor

Close the issue if fixed @vnasing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants