I’ve got Traccar installed on my MB sympl server…
I was all working well when I used it April 24… vague recollection of having to add my IP to the whitelist, but that has no impact now.
I can see I have a rule to allow incoming connections from the traccar app so that data can be collected port 5055 (70-5055).
However I can’t access traccar - this should be via http://mydomain.com:8082
I cant see any rule in my firewall to permit this so have added 70-8082 and put my ip address in.
When I run sudo iptables -L INPUT -vn there is no output relating to 8082 or my IP. is there a command i need to run to get this pulled in or have I got this completely wrong?
If you run sympl-firewall it will do an immediate update of the configuration, and you should be able to see the firewall rule then.
Firstly, I’m not so sure I’d do it that way.
What I do is to have a dedicated subdomain for traccar, and add a config snippet in /srv/traccar.redacted.com/config/apache.d called traccar-apache.conf
It consists of
#added traccar bits
# Don’t rewrite .well-known directory
RewriteCond %{REQUEST_URI} !^/.well-known/ [NC]
DocumentRoot /var/www/html
ProxyPass /api/socket ws://localhost:8082/api/socket
ProxyPassReverse /api/socket ws://localhost:8082/api/socket
ProxyPass / http://localhost:8082/
ProxyPassReverse / http://localhost:8082/
Doing it that way means there is no need to poke an extra hole in the firewall. However, you do need to add an apache2 module.
sudo a2enmod proxy_http
that will sort it, Otherwise, so you’d get a 500 error.
Anton is generally too grumpy to ask for help unless a last resort.
Failing that, you ought to be able to (as user sympl)
touch /etc/sympl/firewall/incoming.d/22-8082
and it ought to work OK.
You then get to use https://traccar.redacted.com as the web ui address - far better for very little extra setting up.