Knowledge Base

YouTrack - where, what, how

Accessing YouTrack

Once you have installed YouTrack using the Deploy4Me service you can work with it using the URL from the passwords. Commonly the URL will be:

If the cloud hosting didn't provide a public DNS name then you can use IP address to access your server and check it:


If you have defined the custom DNS alias during the deployment, then use it like:

Note that DNS record should point to the server public IP address. To prevent problems with DNS you may use Elastic IP, assign it to your instance and point your DNS record to it.

I see an error 502 Bad Gateway. What to do?

Deploy4Me installs YouTrack behind the Nginx proxy. On start of the new server it will take some time for YouTrack to start accepting the requests. So, just refresh a page couple of times and you will see the YouTrack welcome screen. If it not helping then contact Deploy4Me support.

Where YouTrack is installed?

Deploy4Me would place YouTrack files to


The start script is located at


The init.d service is located in


YouTrack is installed behind the proxy. Nginx is used as a proxy server. The configuration of Nginx server can be found at

$(which nginx)/sites-available/youtrack.conf

Where is the YouTrack logs?

The YouTrack start log produced by will be located in the YouTrack installation catalog:


How to stop/start/restart YouTrack?

YouTrack is deployed as a service, so use one of the Linux commands:

service youtrack stop
service youtrack start
service youtrack restart

YouTrack is not available after restart of the server on AWS. What to do?

Amazon Web Services EC2 do not preserve the public DNS names for servers after restart. This means that you would rather reconfigure Nginx to use a new DNS name generated by AWS or configure a permanent DNS name for your server using Elastic IP address. To configure a permanent DNS name here is the step by step instruction:

  1. Allocate an Elastic IP via AWS EC2 console
  2. Associate your address with the instance using context menu on Elastic IP
  3. Configure your DNS to point on that public IP address with a new DNS record. You would possibly wish to create a new A record in the DNS configuration.
  4. If you provided the DNS name before deployment then skip this step, else connect to the server and make sure that in Nginx configuration under
$(which nginx)/sites-available/youtrack.conf

you have a valid name of a DNS record. Change it (for example using vim) and reload the nginx

service nginx restart
  1. Make sure your YouTrack is started and access the URL in a browser
service youtrack restart