I suspect it's some network issue. Traccar doesn't really care if you connect locally or remotely.
I agree that Traccar shouldn't care, but the fact remains that it can and is. My first thought was also that it could be a network issue, but what network issue would cause that error to be thrown? I did have a CentOS 6.8 VM running an earlier version, no trouble at all; now there's a Mint 18 VM doing the work, same IP as the now decomissioned CentOS server.
What makes you so confident that it's Traccar and not something else?
Apache works and NextCloud works, so does Owncloud (we're migrating away from Owncloud). The only one that does not work is Traccar.
Now I ask you, what makes you so confident it isn't Traccar and how can you instill that confidence in me. I'm not intimate with the code, If you are then you can help by looking to see under what conditions that error gets thrown.
What I really need to know is what conditions can throw that error on login and how can I adjust those conditions to eliminate the problem. I really don't care what is causing it, Obviously it is an environmental problem of some kind, yes it is perhaps the network, but exactly WHAT in the network does it not like?
From Traccar point of view there is absolutely no difference if it's a local or remote connection. If you think it's Traccar issue and want some help I would need to see some evidence of that.
What would you like to see in the way of evidence?
Anything that definitively proves it.
I remember having something "popping" up also at one time not sure what it was about might be related IDK.
I remember it was saying something about API and I just closed it out.
I have not seen it after the upgrade to the latest version--my two cents keep up good work Anton!
I still don't know WHY the error was being thrown, but I do know that it has to do with the Internet Service Provider. If I throw up a VPN tunnel and take either the entire network or just the workstation that is trying to connect to Traccar out of the ISP's view I can log in. Take down the tunnel and try to log in and it throws the "HTTP 401 Unauthorized error", login fails, and you get put right back at the login page.
Hi, I'm with the same problem, Traccar is working perfectly, but all the users that use the Nextel 3G / 4G operator report this error, in any other it works perfectly the commands and the login, but when using the Nextel 3G / 4G informs first "connection error with websocket" and then "HTTP 401 Unauthorized error". I'm using EC2 VPS.
It probably means that your ISP messes up with HTTP requests. I would recommend enabling HTTPS to avoid it.
Tranks for reply.
The subject line pretty much says it all. Any attempt to browse to the server on port 8082 from anywhere EXCEPT the LAN, results in the following error;
popping up in a window and promptly vanishing, only to promptly be replaced with the login page. It all happens so fast that I had to record the screen in order to read it.
Yes I've searched the web.
Yes I've looked through the logs.
Yes I know it means that something is "Unauthorized" and that it is an Application Exception and it appears to be related to the Positioning API.
What has me scratching my head is "Why throw the error only when coming in from outside the LAN"? This smells like it's some kind of permissions issue, but if so what is the mechanism at work and how is it "adjusted"?
Any and all help is appreciated.