hollaex.network
I’m not able to see the Argo Smart Routing analytics.
I activated the Argo 4 days ago (Jan 10) but cannot see the analytics data. I thought I gave enough time to collect the data, but it’s not showing anything. Should I give it some more time?
Here are some additional info:
I got almost 2 million reqs in the last 24 hours, so I don’t think this is about the lack of user-requests issues.
All of my subdomains are Cloudflare proxy enabled (the orange cloud icon), but 99% of the calls are dynamic APIs and Websocket calls, so can’t really be cached.
Any help will be appreciated.
Why does nobody from Cloudflare ever answer this?
I can see this problem is quite common. Which I am facing now too.
@yechan: I’ve escalated this topic to Cloudflare, thanks for flagging this.
@sorowerhossan01 are you able to share which website this is happening on for you, and/or what you see on the dashboard for argo and request analytics?
Is this domain active or just written as an example? 
Or you’re using on sub-domain(s)?
Are those sub-domain(s) 1st level a.hollaex.network or deep-level e.g. a.b.hollaex.network?
For quite bunch of them I get SSL_ERROR_NO_CYPHER_OVERLAP error, as they’re deep-level sub-domain(s), and to use as proxied 
Cloudflare for those hostname(s) you’d have to enable Advanced Certificate Manager (ACM) to cover them with an SSL certificate (due to the Universal SSL certificate covering only 1st level sub-domains):
May I ask if you are using Free or Paid Cloudflare plan?
Can Cloudflare reach your origin host without issue and error for your sub-domain(s)? (if deep-level and no ACM, I am afraid there are errors to the origin despite the hostname(s) are covered with a valid SSL certificate)
Websocket requests should be counted towards Argo billing as far as I’ve used it.
What’s your billing state about Argo usage?
Does that work fine and is correct despite the missing Analytics “time response or pie chart”?
May I ask if this behaviour is already for a longer period of time for you as well?
Hi @yechan
Apologies for the trouble you experienced. I checked and noticed that Argo is currently disabled on your domain so I’m unable to provide further insights at this time.
For further troubleshooting, you would need to re-enable Argo.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
Hi @MariG
I just enabled the Argo routing back. I’ve disabled it for a while since I wasn’t sure whether it was really boosting our server.
Could you please help me troubleshoot further?
