Setting up Perforce Server with Digital Ocean?

Question

Hello,

I’m a indie game developer trying to set up a Perforce Server on DigitalOcean for my Unreal Engine project. I’ve been following this tutorial: https://allarsblog.com/2014/09/25/setup-perforce-digital/

Everything seems to be okay up to the point where I try to Open Connection on Perforce. I get the following error message if I try Port 1666:

Connect to server failed; check $P4PORT. TCP connect to xxx.xxx.xxx.xx:1666 failed. connect: xxx.xxx.xxx.xx:1666: WSAECONNREFUSED

And I get the following error message if I try Port 22:

RpcTransport: partner is not a Perforce client/server.

I’ve looked at the documentation on DigitalOcean, but the tutorials are over 7 years old. Any help would be appreciated!! Thanks in advance.

baraboom · Accepted Answer

Here’s a handy way to see what applications and ports are listening on your droplet by running this command in terminal or console:

netstat -tnlp

(You must SSH to your Droplet or open the “Console” in the cloud admin.)

This command will show all programs that are running and listening for connections:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      7873/sshd
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      8999/mysql
...

That’s just an example. Your droplet will probably be a little different but what we’re looking for is a line that might look like this:

tcp        0      0.0.0.0:1666              0.0.0.0:*               LISTEN      7873/perforce

The key parts are the :1666 and something that looks like perforce - I’m just guessing what the application name might be.

If you don’t have any netstat lines that are displaying port 1666 (the port from your error message), then most likely the perforce application is not running. If the app won’t start, take a look at the logs it created as 99% of the time the error is there and 50% of the time, it’s easy to fix whatever the log is complaining about.

hope this helps, and please feel free to ask more questions if you are still stuck