M
Mek
After installing SSL, everything appears to be working, except one thing --
no Web project in a virtual directory that requires SSL will open in Visual
Studio. It raises the error:
"Unable to open Web Project 'Admin'. Unable to validate that the file path
'[path]\Admin' matches the URL path 'https://Localhost:/Admin'. A connection
with the server could not be established" (where [path] is a placeholder for
the project location, and yes, it is correct)
Now, originally I was getting the above error because it was trying to
connect to 'http://[IP Address]/Admin'. To fix the problem, I went into the
..webinfo file and changed 'http' to 'https'. That got it to access the
project using SSL, which was great, but for no apparent reason it immediately
stopped using [IP address] and instead used Localhost:.
Now, the reason it can't find these files is no mystery. The Admin project
is not on Localhost. The IP address it is located at does not correspond to
Localhost. If Visual Studio could find the project at Localhost, that would
mean something was seriously wrong. The problem is that nowhere at no time
have I ever set it to look for the project at https://Localhost: and it never
has. So why did it suddenly decide that's where the project is even though
every configuration file tells it to look in https://[IP address]? Anybody
got any ideas?
no Web project in a virtual directory that requires SSL will open in Visual
Studio. It raises the error:
"Unable to open Web Project 'Admin'. Unable to validate that the file path
'[path]\Admin' matches the URL path 'https://Localhost:/Admin'. A connection
with the server could not be established" (where [path] is a placeholder for
the project location, and yes, it is correct)
Now, originally I was getting the above error because it was trying to
connect to 'http://[IP Address]/Admin'. To fix the problem, I went into the
..webinfo file and changed 'http' to 'https'. That got it to access the
project using SSL, which was great, but for no apparent reason it immediately
stopped using [IP address] and instead used Localhost:.
Now, the reason it can't find these files is no mystery. The Admin project
is not on Localhost. The IP address it is located at does not correspond to
Localhost. If Visual Studio could find the project at Localhost, that would
mean something was seriously wrong. The problem is that nowhere at no time
have I ever set it to look for the project at https://Localhost: and it never
has. So why did it suddenly decide that's where the project is even though
every configuration file tells it to look in https://[IP address]? Anybody
got any ideas?