Traccar Secure Connection

Anton Tananaev6 months ago

I would probably just remove AAAA to avoid any confusion.

neaktivni6 months ago

ok, AAAA records, removed completely

control taken6 months ago

Checking the colleague I see that he has very simple problems that are easy to solve.

  1. Verify in your firewall that port 80 is enabled for web connection, remember that on the same server there cannot be 2 web services hosted on port 80 just in case you have another web service used, (I'll clarify it just in case)

  2. taking the risk of checking if the colleague wants to place the custom url with the custom subdomain, I have it but I do it with nginx it works very well, although the other colleagues are helping him with Apache which is also another option but in my case for practicality I use nginx that's why I chose it although Apache does the same

  3. In your provider that you used to propagate your DNS or the provider from which you bought the domain must have an option where the proxy is normally activated, in my case I use CLOUDFLARE for greater protection against DDoS attacks or some other harmful event.

https://prnt.sc/Qu2sKUi7zYVD
The previous link is a clear example of how it should look, remember that the domain in your case is C and the IP is that of the vps where you have the traccar instance installed.

It is very important to check in your provider's DNS configuration for an option where you can disable proxy to the subdomain so that you can enter without problem.

I hope it helps you, I have it as I explained it to you and it works wonderfully for me.

neaktivni6 months ago

Thanks guys, the Firewall was the problem. The Ports 80 and 443 are now accessible. Now everything works.