Hey folks,
Anyone got any experience of running traccar in AWS?
I have a GT06 tracker that connects perfectly to the demo server on port 5023. I have traccar running in AWS and can connect to is from home as I have an allow all rule from my home IP. I then setup a rule to allow all inbound from any IP on TCP & UDP but the tracker doesnt show up when I configure it for the AWS IP.
I ran nmap from home and get: 5023/tcp open htuilsrv
However, if I remove my allow all rule for my home IP I get: 5023/tcp open htuilsrv
It seems to be that if I have a rule that allows inbound TCP from a specific IP it shows as open but if I have an inbound TCP rule for any source IP I get filtered.
Has anyone else seen this behaviour?
Thanks
To further test this, I just installed the iphone app and it shows up with a rule specifically allowing its source IP (Home wifi) on port 5055 but with allow any IPv4 address as the source the phone is offline.
And it now works. Removed all rules, re-added them and problem solved!
Hey folks,
Anyone got any experience of running traccar in AWS?
I have a GT06 tracker that connects perfectly to the demo server on port 5023. I have traccar running in AWS and can connect to is from home as I have an allow all rule from my home IP. I then setup a rule to allow all inbound from any IP on TCP & UDP but the tracker doesnt show up when I configure it for the AWS IP.
I ran nmap from home and get: 5023/tcp open htuilsrv
However, if I remove my allow all rule for my home IP I get: 5023/tcp open htuilsrv
It seems to be that if I have a rule that allows inbound TCP from a specific IP it shows as open but if I have an inbound TCP rule for any source IP I get filtered.
Has anyone else seen this behaviour?
Thanks