To host Traccar server your computer must have public IP address. Most ISPs provide such feature for extra fee. To select correct port find your device in the list of supported devices, or see the image as below. Port column of corresponding row contains default port number for your device. Powered by Traccar GPS Tracking System. Language: Email. Powered by Traccar GPS Tracking System. Powered by Traccar GPS Tracking System. Powered by Traccar GPS Tracking SystemTraccar GPS Tracking System.

• Traccar Map
• Open Source Gps Tracking Software
• Traccar Devices
• Traccar Server

Traccar

Traccar is a free and open source GPS tracking system for which there exists an OwnTracks protocol decoder (called owntracks) which is, by default, configured on TCP port 5144 on the Traccar server:

Thus you need to configure OwnTracks clients in HTTP mode to connect to your Traccar server at this port, using a URL such as

To make Traccar accept a connection from an owntracks client, you need to set a matching identifier. This identifier is per default the tid of your device. If you have configured a topic for your device, owntracks will identify using the topic instead of the tid (currently iOS only).

An example of a configuration using a topic of owntracks/jane/phone to identify against the Traccar server.

Notes

• Neither encryption nor friends are supported in Traccar.
• If you see a 400 error in the Traccar log, this means the identifier you configured for the Traccar device doesn't match the one sent by the OwnTracks app; try the other one, tid or topic.

HTTP Payloads

HTTP POST payloads shall contain at least the elements lat, lon, _type:location, tst, and either or both of tid and topic. If topic is contained in the payload, that will be used as Traccar's identifier (in which case tid will be added to attributes), else tid.

The following JSON elements, if they're contained in the HTTP payload, will be added to Traccar's position attributes: vel, alt, cog, acc, t, batt, so with an HTTP payload that an OwnTracks app produces like

a query on the Traccar API could produce something like this:

Introduction

In this guide, I’m going to show you how to secure your Traccar installation with SSL, so that it can be reached over https instead of http. Traccar is a free and open source modern GPS tracking system.
Since Traccar has no native support for encrypted connections, we’ll do so by setting up a Reverse Proxy using IIS (which is the recommended method by the developer). We’ll be using Let’s Encrypt to generate a free valid certificate for your Traccar installation.

Prerequisites

• A working Traccar instance, reachable over http (by default http://localhost:8082), installed on Windows Server 2012 R2 or Windows Server 2016.
• A Fully Qualified Domain Name (FQDN), for example ‘yourdomain.com’, with an A record pointing to the IP of your Traccar server:
  (Of course, in the screenshot above, change the variables to meet your environment, i.e. replace ‘123.123.123.123’ with the IP of your Traccar server and ‘traccar.yourdomain.com’ with your own (sub)domain.
  Please note that it can take up to 24 hours, but usually no more than 1-2 hours, for your DNS servers to ‘propagate’, i.e. sync your update with the rest of the world.)

Getting Started

First, install the URL Rewrite add-on module. From Windows Server 2012 R2 and up, you can use the Microsoft Web Platform Installer (WebPI) to download and install the URL Rewrite Module. Just search for ‘URL Rewrite’ in the search options and click ‘Add’.

After installing, do the same for the Application Request Routing 3.0 add-on module:

Next, open IIS and add a new website:

In the window that opens, fill in the following details:
Change the variables to meet your environment.

Close IIS for now and download and install ‘Certify the web’, a free (up to 5 websites) SSL Certificate Manager for Windows (powered by Let’s Encrypt). Certify will automatically renew your certificates before they expire, so it pretty much takes care of itself.

After installing, open Certify. Before we can request a new certificate, we first need to setup a new contact. This is mandatory. So, first, go to ‘Settings’ and set a ‘New Contact’:

Next, click on ‘New Certificate’:

Select the website you created in IIS, in my case named ‘Traccar’:

The rest of the information should now autofill, based on the details you entered in IIS.

Next, go to the Advanced tab and click ‘Test’ to verify if everything is setup correctly

If all goes well, you should get this popup:

Click OK and click ‘Save’.

Evernote productivity system. Next, click ‘Request Certificate’ to request your free valid SSL certificate from Let’s Encrypt for your Traccar installation:

If all goes well, you should get ‘Success’

Next, close Certify and open IIS again. Go to the website you created (in my example Traccar) and click on URL Rewrite

Click on ‘Add Rule(s)’ in the top right corner:

In the window that opens, click on ‘Reverse Proxy’ and click ‘Ok’

In the window that opens, enter ‘localhost:8082’ in the Inbound Rules text field,
select ‘Enable SSL Offloading’,
select ‘Rewrite the domain names of the links in the HTTP responses’ from ‘localhost:8082’
and select your Traccar domain from the dropdown menu, i.e. ‘traccar.yourdomain.com’ and click OK.

Next, go to your website in IIS again and click on Compression:

Traccar Map

Outbound rewriting can only be applied on un-compressed responses. If the response is already compressed then URL Rewrite Module will report an error if any of the outbound rules is evaluated against that response. Therefore, we need to disable Compression in order to get Traccar to play nicely with IIS. Uncheck both options and click Apply:

That’s it! We’re done! Your Traccar installation should now be reachable over HTTPS and have a valid SSL certificate:

If the website is not opening (times out), check if port 443 inbound is open in your firewall:

Open Source Gps Tracking Software

Optional

Traccar Devices

Since your website is now reachable over https, you can change the Challenge Type to tls-sni-01 in Certify:

This way, you can remove the port 80 binding in IIS if you want, to force all traffic to your Traccar installation over https:

Traccar Server

Have fun! Any questions or comments, let me know down below.