Aokromes

1st law update your core before trying to report a bug.

use dns instead external ip and edit hosts for your lan ip to the dns.

you can compile only tools, witch includes connection patcher.

Anywhere.

yes plz, you are the 2nd person having this issue on the last months.

the 1st, also you don't need gui to run tools.

put wow client on linux, extract, anyway, generated files are platform independent.

Try to import the debian 9 install on ESXi to see if it works properly or it crashes, if it works it must be something on your hosting side, maybe custom kernel.

pull your sources, the core don't must try to apply again that sqls because they marqued archived. P.s. clone the repository and compile it yourself.

master branch is on alpha status and i really doubt you can use them properly.

Don't manually import sql files, leave core to do the job.

Don't manually import sql files, leave core to do the job.

there is no fix for what's not a bug.

known issue. ignore.

It's how it must work, nothing to fix there.

Delete all dbc/db2/maps/vmaps/mmaps directories and re-run extractors again.

and it's a thing. https://git.io/vA8RB

7.3.5.25996

There is no difference between TDB 63+all post TDB 63 updates and a TDB 64 release if it's released now.

I only can say before 01-01-2099.

soon(TM)

ignore, they are known bugs.