Since the AoW guy working with me doesn't seem to know how to kill the process (they've done it before so I know they can do it), so he changed the port. This is the internal port only, so it doesn't make a difference to you.
Going to set up/fix now.
Edit: Server is going up NOW!
Last edited by meowmeow55 (2011-08-03 17:36:52)
Offline
I just noticed! YAY
EDIT: When will it be up?
EDIT 2 :
Just letting everyone know, the console is now fully functional, and the server is up and running.
One problem. The IP keeps redirecting us to another server, which is why we are getting the whitelist issue. Skirm is trying to get that fixed as soon as possible.
Last edited by Nexstudent (2011-08-03 18:16:38)

Offline
There is no whitelist. THE SERVER IS REDIRECTING US TO ANOTHER SERVER.
Last edited by Scratchthatguys (2011-08-04 08:15:19)
Offline
Skirm told AoW, so it will be fixed soon.(i hope)

Offline
Because, soft, THEY ARE REDIRECTING US TO ANOTHER PORT. Even if the port changes, the IP stays the same. The reason we are being redirected is because of the ghost process, unless that has been fixed.

Offline
The ghost process has been fixed, but its still redirecting us.

Offline
I wonder why it's taking so long for AoW to stop the redirection. If they set up a huge server hosting service, they can't be complete idiots, probably far from it. So why is it taking so long...?

Offline
These people do NOT know what they are doing. Clearing a ghost process is easy...
Offline
wmays wrote:
I repeat, how can it take them this long to shut down a ghost process? They SET UP A HUGE HOSTING SERVICE, FOR HEAVEN'S SAKE!
+9001
If they run a huge hosting service, they should be able to kill a ghost process.
Offline