@pauljohansson, since Argo is tunneling the traffic that should be your starting point. This could be a problem in the tunneling itself and not being able to transfer the data between server/client and/or with the Argo client not being able to encapsulate the request. You can try also run a comparison with the used browser's developer tools, and check Network requests and Console logs in there which may help drawing further conclusions. You can also obtain simultaneous network captures(e.g using wireshark) from both endpoints (server and client) for when using Argo and when accessing the Hub directly on the server in order to run a comparison. This may not be useful however since the http2 tunneling may prevent any sort of straightforward raw network traffic interpretation.
Dev tools resource: https://support.qlik.com/articles/000016292
Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up! 🙂
