trouble connecting to the server

[alabastardeuce]

So I ran the following SQL script to create an account (as I have not the slightest concept what the wiki is referring to when it says "use the mangos command prompt") - both the daemons (realmd & mangosd) do not allow any input themselves.

insert into realmd.account (id,username,sha_pass_hash,gmlevel,expansion)

Values ('47','testuser2','password3','3','1');

Anyhow; with both of the daemons running (and not showing any fatal errors); all ports used forwarded; firewall shut off; I attempt to login from the wow client and get disconnected virtually instantly.

There are numerous columns within the account table that I don't understand their function and have thus not entered values for: (sessionkey,v,s) ; however from my own browsing these forums and looking at "account creation html macros" people have made for websites; I doubt not filling in values outside of the ones in the script matters.

I've left the bind IP config option to default (0.0.0.0)-

my client is 1.12.1 -

I'm trying to log in on the same computer as the server for whats its worth.

There is such a vast amount of potential reasons behind this problem that I really needed to ask here before my "no degree" havin-ass attempts to fix this from the ground up.... from the core of the earth up, rather.

[Hikari]

The sha_pass_hash field is, as the name already suggests, a hash field. It won't work if you insert your password in plain text.

The easiest way is probably to activate the console, so that you can create your account with the mangosd console window.

For this set Console.Enable to 1 in your mangosd.conf file.

[alabastardeuce]

Yaaa, that made short work of that <3 (also just found the command list in the DB too)... however; now I'm stuck with the ever common "logging into game server" hang - I've been reading the various other threads on this forum relating to It and hope to fix that on my own as there are a million and 1 reasons to be stuck there when hosting the server/connecting via client on the same machine.

... I'll probly drop this zero server attempt anyhow so as to attempt fixes for a more popular core; however the SQL teeth cutting/IP infuriation from this has been worthwhile all the same. call the thread solved!