Author Topic: Dedicated Server - Mission won't run/ Server won't auth.  (Read 2726 times)

however, if we can ever figure out a file to check that might be our culprit, i can check that file and do a few things
1: diff it between my personal user and root, save everything that is THE SAME
2: diff the first diff between not-working users, locate differences

this will tell us precisely the differences in config between a working user and a not working user


whenever you and i are simultaneously online and have time (voice vastly preferable), we can get this sucker solved
i've got time tomorrow, you?

whenever you and i are simultaneously online and have time (voice vastly preferable), we can get this sucker solved
i've got time tomorrow, you?

I'm available every day between 4 and 5:30 PM CST and then after 11. Not a lot of time, I know.

got it working

> ssh -X user@host
password/key login
> xterm

this will open xterm on your local computer (only for unix clients, I don't have a solution for windows clients - look into "x server for windows" or something) or alternately try VNC
inside xterm, cd to your blockland directory, then run the following:
wineconsole --backend=curses Blockland.exe [the key everyone knows] -dedicated
enter your key or whatever neccesary in that xterm window, it should authenticate successfully. then type quit(); in
back in the original SSH window that's still open, run the same command (from the right directory) and everything should work fantastically

i would ask if there are questions, but what we really need is people to try this with varying setups so we can condense this a bit

I did the above with VNC and xterm, and my server worked. However, it still didn't work without xterm.

Then I told Lugnut to try it with xterm (his steps are above), and his now works without xterm.

I decided to try building a docker image for this for the sake of being able to build off a common base instead of troubleshooting the same thing on loads of different computers. So far it can build an image with the latest rev of Blockland, which knows how to execute itself, with the console working flawlessly (from what I can tell).
Github
Docker Index

I got auth to work without forwarding X or running xterm! The solution was to simply wrap the wine call in xvfb-run.

I got auth to work without forwarding X or running xterm! The solution was to simply wrap the wine call in xvfb-run.

Yes, we've known that. We were trying to avoid it though.

noedit: Although we were using xvfb to launch xterm which launched wineconsole. I'm sure there was a reason we made it so convoluted... Oh well, thanks for the tip.

I tried xvfb again and remembered the reason we didn't use it in the first place: there's no input and output.

This command gives us i/o:
Code: [Select]
wineconsole Blockland.exe args hereUsing this, i/o always works, but the auth is seemingly random.

This:
Code: [Select]
xvfb-run --auto-servernum --server-num=1 wineconsole Blockland.exe args hereCauses auth to work every time but we have no i/o.

Give --backend=curses to wineconsole. My guess is that it defaults to graphical, but falls back to curses when there is no X server available.

Give --backend=curses to wineconsole. My guess is that it defaults to graphical, but falls back to curses when there is no X server available.

I tried that a while ago and it didn't work.

Noedit: Anyway, wineconsole defaults to that.

but it works
xvfb-run wineconsole --backend=curses Blockland.exe
it works - seriously, i'll get you a working server on my dedicated in a pm, the stuff seriously works