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
{{ message }}
This repository has been archived by the owner on Nov 30, 2024. It is now read-only.
Remove all placeholder texts including this message here.
Describe the bug
Launcher started
Base path: "R:\EL-WoW"
GitHub API Address: https://api.github.com/
Launching...
---------- Selected Server Config ----------
Name: Everlook (Europe)
Realmlist: logon.everlook.org
Game Directory: ./winterspring-data/WoW 1.14.2 Everlook
Game Version: 1.14.2.42597
Checking WoW installation
Checking HermesProxy status
ModernBuild: 42597
19:56:57 | Server | Server | Starting Hermes Proxy...
19:56:57 | Server | Server | Version 2023-10-19 official 3.10.0
19:56:57 | Server | Server | Modern (Client) Build: V1_14_2_42597
19:56:57 | Server | Server | Legacy (Server) Build: V1_12_1_5875
19:56:57 | Storage | GameData | Loading data files...
19:56:57 | Server | VersionChecker | Loaded 833 legacy opcodes.
19:56:57 | Server | VersionChecker | Loaded 1727 modern opcodes.
19:56:59 | Storage | GameData | Finished loading data.
19:56:59 | Network | Server | External IP: 127.0.0.1
19:56:59 | Server | Server | Starting BnetTcpSession service on 127.0.0.1:1119...
19:56:59 | Error | AsyncAcceptor | System.Net.Sockets.SocketException (10013): 以一种访问权限不允许的方式做了一个访问套接字的尝试。
at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError , String )
at System.Net.Sockets.Socket.DoBind(EndPoint , SocketAddress )
at System.Net.Sockets.Socket.Bind(EndPoint )
at System.Net.Sockets.TcpListener.Start(Int32 )
at System.Net.Sockets.TcpListener.Start()
at Framework.Networking.AsyncAcceptor.Start(String ip, Int32 port) in D:\a\HermesProxy\Framework\Networking\AsyncAcceptor.cs:line 46
19:56:59 | Network | SocketManager | StartNetwork failed to Start AsyncAcceptor
HERMES PROXY HAS CLOSED! Status: 1
Game Server
WoW Everlook Euro. 1.14.2
Hermes Proxy Version
3.10
————
can anybody solve this?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Remove all placeholder texts including this message here.
Describe the bug
Launcher started
Base path: "R:\EL-WoW"
GitHub API Address: https://api.github.com/
Launching...
---------- Selected Server Config ----------
Name: Everlook (Europe)
Realmlist: logon.everlook.org
Game Directory: ./winterspring-data/WoW 1.14.2 Everlook
Game Version: 1.14.2.42597
Checking WoW installation
Checking HermesProxy status
ModernBuild: 42597
19:56:57 | Server | Server | Starting Hermes Proxy...
19:56:57 | Server | Server | Version 2023-10-19 official 3.10.0
19:56:57 | Server | Server | Modern (Client) Build: V1_14_2_42597
19:56:57 | Server | Server | Legacy (Server) Build: V1_12_1_5875
19:56:57 | Storage | GameData | Loading data files...
19:56:57 | Server | VersionChecker | Loaded 833 legacy opcodes.
19:56:57 | Server | VersionChecker | Loaded 1727 modern opcodes.
19:56:59 | Storage | GameData | Finished loading data.
19:56:59 | Network | Server | External IP: 127.0.0.1
19:56:59 | Server | Server | Starting BnetTcpSession service on 127.0.0.1:1119...
19:56:59 | Error | AsyncAcceptor | System.Net.Sockets.SocketException (10013): 以一种访问权限不允许的方式做了一个访问套接字的尝试。
at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError , String )
at System.Net.Sockets.Socket.DoBind(EndPoint , SocketAddress )
at System.Net.Sockets.Socket.Bind(EndPoint )
at System.Net.Sockets.TcpListener.Start(Int32 )
at System.Net.Sockets.TcpListener.Start()
at Framework.Networking.AsyncAcceptor.Start(String ip, Int32 port) in D:\a\HermesProxy\Framework\Networking\AsyncAcceptor.cs:line 46
19:56:59 | Network | SocketManager | StartNetwork failed to Start AsyncAcceptor
HERMES PROXY HAS CLOSED! Status: 1
Game Server
WoW Everlook Euro. 1.14.2
Hermes Proxy Version
3.10
————
can anybody solve this?
The text was updated successfully, but these errors were encountered: