I can't seem to access the Executive Dashboard from any server except the server where it is installed even if I use the IP of that server. The configuration form for it only allows the port to be configured while the one for the scheduling server allows an URL to be configured.
Is this intended? It doesn't seem very useful to limit it to the server. Is it just binding to the NETBIOS name (staging) because we aren't on a domain? Is there a way to configure the bindings of the web server so that it can be public (within our intranet)?
Does not work: http://192.168.0.30:8085/results/dashboard;projectId=6dbbe3cd-2932-4382-ab5a-f51663416d99;projectName=Efficio%20Main%20Application
-Bad Request - Invalid Hostname
5 Answers, 1 is accepted
The Executive Dashboard is a new feature, which we introduced in our latest release 2019.3.1002 and we are happy to hear your feedback and suggestions for improvements. As you have already discovered, the server bindings are by localhost, IP:127.0.0.1 and by the NETBIOS name and currently there is no way to configure the bindings as of now. This is a valid request and I created a public feature request from your behalf for our team to investigate and plan for future releases.
My experience with this feature shows that I can access the Executive Dashboard, hosted on another machne, by its NETBIOS name without any troubles. For this to work, though, the machines need to be in the same network and "see" each other. Also, you need to make sure that the configured port is open.
Please check the above details and conditions and let me know if there is still an issue with accessing the Executive Dashboard from another machine in the network. I will do my best to help you find a solution, if you can share more details about the environment and network specifics.
We have different networks linked together using VPNs. If I want to make this accessible to someone on their home computer they would access it over their VPN connection using the internal IP. Their computer isn't aware of "staging". The port is open since in my testing I can connect and get the bad request error. I did test it from another computer within the same network and the URL works in that scenario.
It isn't critical to have this at this time, but it would be nice to have in the future for people to view test results without having to have access to Test Studio.
I understand that the current implementation has limitation, as you described. Our engineering team evaluated those and is working towards improvements in the next main release or service pack. So, please keep an eye for updates and follow the public feature request.
I am sorry for the caused inconvenience regarding this feature and thank you for your valuable feedback.
Hi Plamen - was this ever delivered, to allow access from other machines, with a URL or VPN? I'm sure that I was in fact able to do this before, but I am unable now (probably because of a server upgrade etc). Do you have some instructions on how to open this up for VPN access from other machines? I'm trying with the address: http://telerikservernameorIP:8085/
I am happy to tell you that we quickly provided a solution in the following release back in October 2019 and fix the way IP address and host name are resolved. That fix should have helped you access the Executive Dashboard in your environment.
As you mentioned, it worked until recently and I assume that there might be some changes in your network or in some of the servers. Please check your firewall and network settings and ensure that all machines can see each other and communicate freely. You can try using the IP address of the machine instead of the name. Maybe the IT team on your end can assist you with that and share more knowledge about any recent changes.
If you continue to experience any troubles and can't seem to figure out what is changed, please share more details regarding the network setup and environment you have. Also, what were any recent changes from the time you noticed the issue.