Does not redirect to port 8082
I see some servers resolve the domain name correctly. So maybe the problem was that the update is not propagated yet. How long was TTL on your domain and name servers? Have you waited enough?
The error was in the A record
I had created a droplet for testing before this and used the same domain.
Conclusion: I deleted the droplet but did not change the IP when I created the new one. That's why the IP was showing different in DNS propagation.
You were right Anton, the A Record address was pointing to the IP of the destroyed droplet and the propagated DNS corresponded to it.
I hope that's all, I spent the day burning neurons due to lack of attention
I will wait for the DNS to fully propagate and do a redirect in the index
Thanks for now, as soon as it works I'll post here to close the topic
We are live > http://atrack.live/
Now I'm going to provide the SSL and configure everything.
Thank you very much, I learned a lot today thanks to the forum.
See, I don't think I understand (independent domain verification) . The name servers that are propagated were inserted into the atrack.live domain server as indicated by digitalocean.
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com
That's the error, everything seems fine, but it doesn't allow direct connection via the address, only via the public IP number.
I'm going to make a few more attempts now with Apache installed, if I manage to solve it I'll come back here and try to explain what was happening.