@steff94 Thank you for your feedback and apologies for the lack of response from Netskope!
To troubleshoot individual tests we implemented unique identifiers. Please hover the mouse over the steering confirmation and copy the code showing up.
I see you have raised a support ticket on this, please submit the code in the ticket. That would be helpful. Thank you in advance.
Hi @rkessler,
thanks for your reply. I just atted the code of one of my last failed speedtests to the support ticket.
Best regards
We found the problem: The config of our Netskope Tenant itself blocked the speedtest download files because of “Unknown File Header.”
So we needed to expand the exceptions for all the speedtest urls (ie. speedtest-dus1.goskope.com.har, speedtest-muc1.goskope.com etc.) for Websockets and the Unknown File Header Error ..
Hi @steff94 thank you! Very interesting.
Might be another use case for RegEx-URL lists… ;-)
Glad it works now.
@mbouthors FYI
Yeah - and also it would be a good idea for netskope team to implement a default allow rule for its very own speedtest service in all (new) tenants :)
Is it possible to run these test without netskope steering to see the difference with netskope agent? It shows invalid token
Is it possible to run these test without netskope steering to see the difference with netskope agent? It shows invalid token
Hi @shivam397 - Yes, it is. Get the token(s) from your customer Success Team (TAM/CSM) or Support (use existing tickets for requests). Such tokens are valid for 10 runs / 1 week.
