This means you have some issues with WebSocket connection.
So is the problem on the server side or the client/browser side
Could this be because I'm using a reverse proxy on the QNAP where Traccar is installed?
If you're using proxy, most likely it's misconfigured proxy.
I foud the problem. If I use original port in local network it works fine. But when I connect by reverse proxy I have 60 delay during refreshing position on map. Have You got any idea how to configure reverse proxy to work with web sockets in QNAP. I dont see any option for this.
Not sure about QNAP, but you need to make sure you enable web socket proxy.
OK, I've done some work with ChatGPT and now I know that the reverse proxy built into the QNAP GUI doesn't support websockets, or I don't know how to do it. I decided to install TAX Reverse Proxy on the QNAP, configured it, and it seems to be working because I see a status of 101 for websockets, which means it should be working.
@Anton Tananaev -
As usual you led me to the solution, you are a master
Hi, I've been using Traccar for several years now, but I've recently noticed that the position in the live view is refreshed quite infrequently, about every 60 seconds. This definitely wasn't the case before, and the data was displayed immediately after the GPS tracker sent it. I'm not sure which version this started happening with. I'm currently using 5.6. However, the GPS data is sent to the server because when I choose to show the route history on the map, the number of points is large (significantly higher than what's shown in the live view). Is there a parameter responsible for the position refresh rate in the web browser?
Live View

Route history view
