Sandbox for Legion Beta

[Froggey]

After reinstalling the beta on Windows 10 and redoing all the sandbox steps, I still get the disconnect error.

[doityourself]

I dont know anything about C++, .NET and i dont know what else you use for creating the sandbox but im so desperate right now i started downloading decompiler to look inside your sandbox and connection patcher and try to find anything relating to ports to change it

i really want this sandbox to run my girlfriend just went out and i want to use this night to explore the broken isles

I really used ports which shouldn't be used by any other progam. It must be something different

[rovatok]

What did you change since january? The last ver in jan still worked fine.

I mean that can help to locate the source of the error.

[doityourself]

What did you change since january? The last ver in jan still worked fine.

I mean that can help to locate the source of the error.

This version includes a http(s) server on port 8001

[rovatok]

Is it necessary to include?

[doityourself]

Is it necessary to include?

yes, but it should not be a problem. if u started the sandbox u can go to 'https://127.0.0.1:8001/login/?app=wow' in your browser to see if it works
It should look like this

[rovatok]

It says:

{"inputs":[{"input_id":"account_name","label":"Battle.net email","max_length":320,"type":"text"},{"input_id":"password","label":"Password" ,"max_length":16,"type":"password"},{"input_id":"log_in_submit","label":"Log in to Battle.net","max_length":0,"type":"submit"}],"type":"LOGIN_FORM"}

Thats ok?

[rovatok]

In the earlier versions the connection patcher made changes the files in the ProgramData\Blizzard, Battlenet folder, the recent dosent. The problem is in the sandbox or in the client side what do you think?

[doityourself]

In the earlier versions the connection patcher made changes the files in the ProgramData\Blizzard, Battlenet folder, the recent dosent. The problem is in the sandbox or in the client side what do you think?

The new auth method doesn't need to make changes there.

[rovatok]

So there is no problem with the port, thats certain.

There is an agent.log perhaps it says something to you:

5/22 20:44:31.346 AgentCommunicator::Initialize(): uid = 'wow_beta'
5/22 20:44:31.346 Reading agent.dat file to determine agent port.

5/22 20:44:31.346 Reading agent.dat file to determine agent port.

5/22 20:44:31.346 Agent communicator initialized. Agent path: 'C:/ProgramData/Battle.net/Agent/Agent.exe' URL: '127.0.0.1'
5/22 20:44:50.420 Connecting to agent on port 1120
5/22 20:44:51.422 Starting agent, attempt 1
5/22 20:44:51.805 Reading agent.dat file to determine agent port.

5/22 20:44:51.805 WARNING: AgentConnection::Work() took 382.7295ms

5/22 20:44:51.828 Connecting to agent on port 1120
5/22 20:44:57.431 Starting agent, attempt 2
5/22 20:44:57.431 Reading agent.dat file to determine agent port.

5/22 20:44:57.431 WARNING: AgentConnection::Work() took 1.4533ms

5/22 20:44:57.441 Connecting to agent on port 1120
5/22 20:44:57.441 Successfully sent message 1 to agent
5/22 20:44:57.463 Received response. MSG 1, response code 200
5/22 20:44:57.463 Connecting to agent on port 1120
5/22 20:44:57.473 Successfully sent message 16 to agent
5/22 20:44:57.473 Received response. MSG 16, response code 200
5/22 20:44:57.473 Connecting to agent on port 1120
5/22 20:44:57.491 Successfully sent message 10 to agent
5/22 20:44:57.502 Received response. MSG 10, response code 200
5/22 20:44:57.502 Connecting to agent on port 1120
5/22 20:44:57.502 Successfully sent message 12 to agent
5/22 20:44:57.522 Received response. MSG 12, response code 200
5/22 20:44:57.522 Connecting to agent on port 1120
5/22 20:44:57.522 Successfully sent message 15 to agent
5/22 20:44:57.540 Received response. MSG 15, response code 200
5/22 20:44:57.540 Connecting to agent on port 1120
5/22 20:44:57.540 Successfully sent message 12 to agent
5/22 20:44:57.558 Received response. MSG 12, response code 200
5/22 20:44:57.558 Connecting to agent on port 1120
5/22 20:44:57.576 Successfully sent message 15 to agent
5/22 20:44:57.586 Received response. MSG 15, response code 200
5/22 20:44:57.586 Connecting to agent on port 1120
5/22 20:44:57.586 Successfully sent message 14 to agent
5/22 20:44:57.605 Received response. MSG 14, response code 200
5/22 20:44:57.605 Connecting to agent on port 1120
5/22 20:44:57.615 Successfully sent message 10 to agent
5/22 20:44:57.615 Received response. MSG 10, response code 200
5/22 20:44:57.615 Backfill complete, detaching from agent.
5/22 20:44:57.638 Connecting to agent on port 1120
5/22 20:44:57.647 Successfully sent message 2 to agent
5/22 20:44:57.647 Received response. MSG 2, response code 200
5/22 20:45:17.397 AgentCommunicator::Shutdown()


Have you any hint where the connection goes wrong?

[rovatok]

Perhaps Win 7 cant handle the 1120 (used by the agent) and the 8000 ports at the same time?

[woxwalt]

tried the sandbox on a win10 virtual environment (vbox) on my win7 host-system

no error, connection established on the first try. unplayable of course because there is only gpu.emulation activ.
my guess is there´s some code missing on win7 (dotnet or some library-shit).

[doityourself]

Could u try this: Zippyshare.com - Arctium WoW Legion Sandbox.exe

there should be a file created named debug.txt after your disconenct error

[rovatok]

Could u try this: Zippyshare.com - Arctium WoW Legion Sandbox.exe

there should be a file created named debug.txt after your disconenct error

I started, but no txt were created.

I searched the whole legion folder.

[doityourself]

I started, but no txt were created.

no debug.txt after you tried to login?