First off, please note that only occasionally will these two go down - On the order of once per couple months. This is due to the server restarting itself, most likely for updates.
If both RobbieBot and the TS server are unable to be connected to, and the forum IS, then someone has to take these steps. Generally, this person is me, however this guide will show you how.
Please note that for most of you, this guide will be useless: You need a special password to do this, and only
Eugene and I have it. Unless there is some very special circumstances, only us two *should* have it, however if you are either Lordy or have been told the password, then this is what you do:
- 1. Download PuTTY
PuTTY can be gotten from http://www.putty.org/
The link there will redirect you to a cryptic looking site. Under Binaries(this means executable programs), click the link for Putty.exe
- 2. Connect to the server
PuTTY does NOT need to be installed. When you run PuTTY.exe, up will pop a window entitled PuTTY Configuration.
You need to enter the following settings:
A. Host Name(or IP address): 92.48.69.8
B. Port: 22
C. Connection Type: SSH
Now, you may want to save this information by typing a name into the saved sessions box and clicking save.
Click on the Open button at the bottom of the window to continue.
- 3. Login
When you click Open, the configuration window will disappear, and a black window titled 92.48.69.8 - PuTTY will appear.
After a minute or less, you should see "login as:" appear in the upper left hand corner.
Type wgwilde -Enter-
In a couple seconds you will see "[email protected]'s password:"
Type *the special password you have. Eugene: this is the wg.com site pasword* -Enter-
When you are typing this it will not show up. No *s, no letters, NOTHING.
- 4. Starting RobbieBot Note: You should not have to start Robbiebot anymore; it is supposed to start when the server starts up.
If you got successfully logged in, you should see two new lines(4 total lines on the screen): "Last login: *date here*" and "[wgwilde@vps2735 ~]#".
That last line is your command prompt. Just like the 'c:\>' prompt of dos, this is one for linux.
Note that as you are typing, the letters may take a second or so to show up on screen - its kind of like runescape chat and how it lags.
Type cd /home/bot -Enter-
Type ./botlaunch.sh -Enter-
You should now see nothing but the prompt again. Check IRC, robbiebot should be up in 30 seconds or less.
- 5. Starting TeamSpeak
Type cd /home/ts3 -Enter-
Type ./ts3server_startscript.sh restart -Enter-
You are now done.
- 6. Restarting the server.
If this is needed, you can:
Type reboot now -Enter-
The putty session will disconnect after a few seconds, and in a minute or so, Robbiebot should rejoin irc.
- 6. Exiting PuTTY
You may simply close putty with the red X, or press Alt+F4.
Hope that guide helps someone!
Edit:
Just in case they are needed, I've created a few SA permission keys:
token=N3FB6VfVR1dE1dF9GIGOgghO6u7RDFBiMRAql3XO
error id=0 msg=ok (24 ms)
token=u92Jl2zWoUGoCGUEGqYOkG9qT1+MNk6WNeAlN8bX
error id=0 msg=ok (88 ms)
token=r2l7QjlBFBGLCP49hj4mBMgkCeDpMX9KHly1+E2t
error id=0 msg=ok (65 ms)
token=SP4LrQxqr4kLIjtuGYe9V8p7M83qI\/i3QzCoGGuD
error id=0 msg=ok (58 ms)
token=Pkr1gxwfcxgbUP266NE+cSG5GKjr8OMQome9ycuu
error id=0 msg=ok (45 ms)
token=GN6efBtzS\/QL9d+wVwgqKwi\/XjgCrvAHmnRAMJPX
error id=0 msg=ok (24 ms)
token=bKVDq6MGfi\/pgPV5M38TxQ3GfgYRFHtr0SBUkoAK
error id=0 msg=ok (57 ms)
token=Swaf2NBnxU2803d3ylFyMwYNnsGwashrrrt5tgky
Each of these keys is
ONE USE and will grant the user SA permissions. Let me know if you have to use one.
-RobbieThe1st