TAKX Failed to Query Contact List #115
Comments
|
I'm glad to hear that TAKX is mostly working with OTS. Unfortunately I won't have access to it until it's public. I added a section about supporting this project at the bottom of the README. Can you set That should show what API call it's making. My guess is that it's making a call to an endpoint in the Marti API that I haven't implemented yet. If so, that will be an easy fix. |
|
I did actually try running it with debug, but none of the log messages looked particularly informative about what it was trying to do. Still, here you go. This is a fresh session with OTS just restarted, and no other clients connected. I launched TAKX, let it connect, got the error message, then closed it. |
|
That's strange, in debug mode I expected it to add each HTTP request to the log. But we should also be able to see that in the nginx logs too. Can you post |
|
This captures me re-doing certificate enrollment, connecting, getting the error message. An interesting note as well: I'm getting this on TAKX version 5.2 (the current release version). I tried uninstalling that and installing TAKX 5.1 and it does not give the error message. So possibly related to a new feature in TAKX hitting an unimplemented endpoint in OTS (presumably that oauth one?), or maybe just a bug in TAKX. |
|
Capturing the same log but using TAKX 5.1, it's slightly different but I think only because I clicked on the map in OTS web while gathering the previous log. I guess the oauth call is what's making it angry, but maybe TAXK 5.1 just ignores it. |
|
Aha, TAKX 5.1 seems to show an error in its own log when 5.2 does not for whatever reason. It's looking for that oauth endpoint: It also is complaining about hitting a similar endpoint when fetching missions |
|
Thanks, those logs are helpful. I'll review them and let you know when a fix is ready. |
|
I actually added location /oauth {
proxy_pass http://127.0.0.1:8081;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}Then run |
|
Modified nginx config, log now shows status 200 for the oauth requests but throwing an error about the contact list and/or fetching missions, presumably if you only added support for that recently I may have not pulled that update. I'm on 1.4.1 (commit ga792eaa) despite having installed this particular one just a couple weeks ago... not sure why it didn't at least pull 1.4.2, which I see mentions CloudTAK support in the release notes. Actually hmm, I ran the ubuntu updater script, but the webui is still showing being on 1.4.1.
buuuuuut:
Also worth noting, I've had trouble with WinTAK not being able to subscribe to missions on OTS, and by "trouble" I mean it receives and accepts the invitation then just fails to subscribe. Possibly related? |
|
What does |
So I guess that's ok. The access log shows nothing else, just over and over. Note that it's now status 200 after editing the nginx config, but I'm guessing the backend isn't answering. I also tried turning DEBUG back on in OTS under the thought that maybe it was never hitting the endpoint in the backend with the old nginx config, but I don't see any new or relevant messages in the ots logs either. |
|
Do you have an account on the public server or could you make one? Then I could watch the logs and traffic while you use TAKX to reproduce the issue. |
|
Sure thing, just made an account and connected TAKX. Same error message, though I note that the webui on the public server does say version 1.4.1, hmm. I'll leave TAKX connected, lemme know if you need any info. |
|
Thanks, I'm checking the logs now. Though it's strange that you're seeing version 1.4.1 on the public server. It's showing as 1.4.2 for me |
|
I was seeing 1.4.2 on the public server, versus mine (that is seemingly up to date) shows 1.4.1. HOWEVER now my OTS is saying 1.4.2 for OTS and 1.42 for the UI in the webui version block. Might have just been browser cache or something that it was still saying 1.4.1, so disregard. |
|
I looked through the public server logs but I can't see TAKX making any requests for missions or contacts. Could you post the TAKX error it's throwing now? Before it was caused by the 404 error for /oauth/token but that's returning 200 now. |
|
Also:
|
My guess is that this means that OTS isn't returning the token in the format that TAKX expects. Unfortunately the only way to figure out that format is to reverse engineer how it works with the tak.gov server, but I don't have access to TAKX. I think figuring out that format will probably fix the other errors you're getting |
|
Makes sense, I figured it was something along those lines. I'll try to take a look look through the TAK developer documentation and see if I can find anything, otherwise I guess just leave this until TAKX is public. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, first off big fan of OTS it's been a big help to me working with TAK and is a pleasure to use, especially compared to some of the other options for servers. Please add a donation link so I can buy you a beer.
Recently I started playing with TAKX from tak.gov, which I think is not publicly available yet so the tl;dr is it's a merging of WinTAK and RaptorX that is seemingly going to eventually replace those two products on desktop (it supports Windows and Linux). I assume it'll be made available to non-government users at some point.
Anyway, it seems to mostly work with OTS. I was able to auto-enroll with my OTS server and it connects successfully etc, except that it give me the error message "Failed to Query Contact List" on connection and periodically, presumably whenever it is pinging the server. There are no error messages about this in the TAKX console, nor do I get any errors in the OTS logs. I'm not sure what the impact is, either, as I seem to at least have basic functionality to see other devices on the map, send them chat messages/markers/etc, but clearly something is wrong.
I'm not sure how to proceed with debugging, but I can do whatever you suggest that might be helpful to figure out what the issue actually is.
The text was updated successfully, but these errors were encountered: