-
January 13th, 2015, 09:31 PM
#1
Thank you for your response.
To close the loop, this ended up being an issue with inbound firewall rules on the server. When we removed IIS it removed the inbound rule for 80/443. The dead giveaway was that we could navigate to https://localhost:443/monitor and the monitor displayed properly.
Additionally (and this was news to me), I had copied down a directory from the demos which (I thought) contained the monitor. This was causing issues by having the same name as the internal monitor. I simply deleted the directory and all was well with the internal web server.
Thanks again.
Similar Threads
-
By ernivan in forum Client SDKs
Replies: 1
Last Post: March 11th, 2011, 09:35 AM
-
By Alessandro in forum Client SDKs
Replies: 2
Last Post: July 19th, 2010, 09:01 AM
-
By riaanj in forum General
Replies: 7
Last Post: May 30th, 2007, 01:12 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 05:24 AM.
Bookmarks