For security and internet availability I run my Traccar server via a reverse proxy (Apache webserver).
When I'm on my own network, I use a token to login as admin (like https://fake.traccar.public/?token=very_long_and_secret).
That worked fine until version 6.15: When I now login as admin with my token and want to change something that needs admin rights (like change the icon of a device), I get a popup that says 'HTTP 401 Unauthorized | More Details'.
The weird thing is that I get admin rights when I login with my username and password (via the reverse proxy https://fake.traccar.public) or when I login with my token directly via the local IP address (like http://192.168.0.1:8080/?token=very_long_and_secret).
Is this change in behavior in 6.15.2 (using a token on reverse proxy) one of the security fixes that are mentioned in the blog?
And do I need to change something in the Traccar (or the Apache) configuration to be able to login as admin with a token via the reverse proxy?
For security and internet availability I run my Traccar server via a reverse proxy (Apache webserver).
When I'm on my own network, I use a token to login as admin (like
https://fake.traccar.public/?token=very_long_and_secret).That worked fine until version 6.15: When I now login as admin with my token and want to change something that needs admin rights (like change the icon of a device), I get a popup that says 'HTTP 401 Unauthorized | More Details'.
The weird thing is that I get admin rights when I login with my username and password (via the reverse proxy
https://fake.traccar.public) or when I login with my token directly via the local IP address (likehttp://192.168.0.1:8080/?token=very_long_and_secret).Is this change in behavior in 6.15.2 (using a token on reverse proxy) one of the security fixes that are mentioned in the blog?
And do I need to change something in the Traccar (or the Apache) configuration to be able to login as admin with a token via the reverse proxy?