"port" option fixed

The check for specifying both run_dir and port was made after run_dir var was
populated by the client so specifying the port always triggered this error.
This check is now moved.