I have Traccar running on a backend server without a fixed ip so it is set up to use dyndns (lets say https://example.dyndns.org:12345)
This is proxied to a frotend server I have at https://gps.example.com
Everything was working fine untill yesterday. Then all of a sudden I sometimes started getting remote procedure call error popups, a 404 page (jetty returns it cant find 502.shtml) or a server not responding popup.
If I refresh the page after an error most of the time Traccar loads normally and throws no error, but the error reappears after a while upon further interaction.
The errors appear only when accessing traccar via the frontend server. If I go directly to https://example.dyndns.org:12345 traccar works fine and throws no errors.
excerpt of error_log on frontend:
[Tue Feb 06 10:48:07.409655 2018] [proxy:error] [pid 18267] [client xxx.xxx.xxx.xxx:49658] AH00898: DNS lookup failure for: example.dyndns.org returned by /traccar/dataService, referer: https://gps.example.com/
[Tue Feb 06 10:50:52.783576 2018] [proxy:error] [pid 18593] [client xxx.xxx.xxx.xxx:49686] AH00898: DNS lookup failure for: example.dyndns.org returned by /traccar/report/Op\xc4\x87e informacije.html, referer: https://gps.example.com/
[Tue Feb 06 10:51:09.327454 2018] [proxy:error] [pid 18595] [client xxx.xxx.xxx.xxx:49687] AH00898: DNS lookup failure for: example.dyndns.org returned by /traccar/report/Op\xc4\x87e informacije.html, referer: https://gps.example.com/
[Tue Feb 06 10:52:13.423244 2018] [proxy:error] [pid 18537] [client xxx.xxx.xxx.xxx:49692] AH00898: DNS lookup failure for: example.dyndns.org returned by /traccar/dataService, referer: https://gps.example.com/
On the backend there is nothing of note in the service wrapper log, or the error_log.
Proxy configuration on frontend:
SSLProxyEngine on
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
ProxyPass "/" https://example.dyndns.org:12345/
ProxyPassReverse "/" https://example.dyndns.org:12345/
# I tried adding these two lines yesterday after the error started to appear but it did not help
#ProxyPass "/api/socket" ws://example.dyndns.org:12345/api/socket
#ProxyPassReverse "/api/socket" ws://example.dyndns.org:12345/api/socket
Also worth noting is that if I put the backend IP directly in the frontend ProxyPass directive instead of example.dyndns.org, the frontend works and throws no errors. But this is not an option for me since the backend IP changes every day.
It sounds like you are not using official version of Traccar.
We are using Traccar 3.11 and Traccar Web UI 3.9. You are saying the problem is with traccar-web?
Possibly. It's very different from official version and seems like you are trying to use official proxy config with it, which most likely incompatible.
Next time you should clearly mention that you are NOT using official version of Traccar.
I am sorry for not mentioning this in the original post.
The issue was resolved by a script that periodically pings the dyndns address for the ip address and then sets the ip directly in the proxy config instead of the dyndns address.
I have Traccar running on a backend server without a fixed ip so it is set up to use dyndns (lets say https://example.dyndns.org:12345)
This is proxied to a frotend server I have at https://gps.example.com
Everything was working fine untill yesterday. Then all of a sudden I sometimes started getting remote procedure call error popups, a 404 page (jetty returns it cant find 502.shtml) or a server not responding popup.
If I refresh the page after an error most of the time Traccar loads normally and throws no error, but the error reappears after a while upon further interaction.
The errors appear only when accessing traccar via the frontend server. If I go directly to https://example.dyndns.org:12345 traccar works fine and throws no errors.
excerpt of error_log on frontend:
On the backend there is nothing of note in the service wrapper log, or the error_log.
Proxy configuration on frontend:
Also worth noting is that if I put the backend IP directly in the frontend ProxyPass directive instead of example.dyndns.org, the frontend works and throws no errors. But this is not an option for me since the backend IP changes every day.