Does not redirect to port 8082
You probably need to setup a proxy:
In what situations does this happen?
I've had another Traccar platform at digitalocean for a few years and I don't remember this ever happening.
Don't know what you mean. We never had any redirects in Traccar. Maybe what you did before is set the web port to the default one?
So, I meant that when the old platform was installed, it simply worked, both through the public IP and the domain address. And it is still without ssl
I don't remember exactly how it was done
Thanks for your attention Anton
What do you mean by redirect exactly? I feel like you're not using the right terminology.
It would be to enter the domain name in the address bar and access the platform.
For example:
My two platformshttp://trackinkernel.com
It ishttp://159.203.92.153
in the second you need to insert :8082 manually after the IP
it couldn't even locate the new associated domain, despite the DNS being available.
Your domain is pointing to a completely different IP address:
You need to add redirect to that 8082 port. Or setup traccar to use port 80, then it work without any redirection. If you use just http://159.203.92.153 it tries to open port 80 (and you have apache server listen to that port, so you need to change apache port to something else first), that is reason you need to add port 8082 after the ip.
I don't even know how I did it. I made several adaptations when I installed it at the time.
And the worst thing about this domain is that I lost the root password. I only have access to the platform's administrative panel.
I just installed Apache2 and managed to run the Ubuntu index via public IP http://159.203.92.153 which previously gave an error. The page asks to replace the index. I believe that if you create a page redirecting to http://159.203.92.153:8082 it should work using the public IP number.
Already associating the domain, I'm not sure you'll find it.
The domain is still not configured, as you can see from the link. It seems like the issue has nothing to do with Traccar and it's just a problem with your DNS configuration.
I associated the domain with the droplet and the digitalocean DNS on hostinger hosting pointing the way.
the A Record has been found and appears in DNS propagation. The domain is http://atrack.live and at least for me, the error continues to appear.
Unable to access this siteConnection to atrack.live has been refused.
Try:
Check the connection
Check proxy and firewall
ERR_CONNECTION_REFUSED
I am translating from Brazilian Portuguese to English. I don't know exactly how you can understand. Portuguese seems to be full of grammatical complications compared to English
What is the real server address? The domain is pointing to 104.248.2.153 from what I can see:
https://dnschecker.org/#A/atrack.live
And it's consistent from all locations, so seems like DNS is not configured correctly.
The public IP generated when creating the droplet was 159.203.92.153
In the options I inserted the domain atrack.live and put the digitalocean DNS in the original hosting of the domain, in this case hostinger.com.
The DNS was found as soon as I created the A Record in digitalocean
It seems like you're completely ignoring the independent domain verification that I keep providing, so I don't think anybody would be able to help you.
New installation at DigitalOcean, new droplet, domain with dns pointing. everything as indicated in the installation manual.
When trying to access the domain, it doesn't find it. If you only use the public IP it also gives an error, I can only access it by manually inserting the port path: 8082 after the IP, then I can access normally.
Am I forgetting any details?
I've been reading about some possibilities for two days but it all seems a bit vague to me, as the installation is done from scratch and following the steps indicated.