You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/common/storage-explorer-troubleshooting.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ There are several built-in RBAC roles which can provide the permissions needed t
71
71
Certificate errors typically occur in one of the following situations:
72
72
73
73
- The app is connected through a _transparent proxy_, which means a server (such as your company server) is intercepting HTTPS traffic, decrypting it, and then encrypting it by using a self-signed certificate.
74
-
- You're running an application that's injecting a self-signed SSL certificate into the HTTPS messages that you receive. Examples of applications that inject certificates include antivirus and network traffic inspection software.
74
+
- You're running an application that's injecting a self-signed TLS/SSL certificate into the HTTPS messages that you receive. Examples of applications that inject certificates include antivirus and network traffic inspection software.
75
75
76
76
When Storage Explorer sees a self-signed or untrusted certificate, it no longer knows whether the received HTTPS message has been altered. If you have a copy of the self-signed certificate, you can instruct Storage Explorer to trust it by following these steps:
Copy file name to clipboardExpand all lines: articles/virtual-machines/troubleshooting/event-id-troubleshoot-vm-rdp-connecton.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ wevtutil qe system /c:1 /f:text /q:"Event[System[Provider[@Name='Microsoft-Windo
61
61
**User:** N/A <br />
62
62
**Computer:***computer* <br />
63
63
**Description:**
64
-
The RD Session Host Server has failed to replace the expired self signed certificate used for RD Session Host Server authentication on SSL connections. The relevant status code was Access is denied.
64
+
The RD Session Host Server has failed to replace the expired self signed certificate used for RD Session Host Server authentication on TLS connections. The relevant status code was Access is denied.
@@ -73,7 +73,7 @@ The RD Session Host Server has failed to replace the expired self signed certifi
73
73
**User:** N/A <br />
74
74
**Computer:***computer* <br />
75
75
**Description:**
76
-
RD Session host server has failed to create a new self-signed certificate to be used for RD Session host server authentication on SSL connections, the relevant status code was object already exists.
76
+
RD Session host server has failed to create a new self-signed certificate to be used for RD Session host server authentication on TLS connections, the relevant status code was object already exists.
@@ -85,7 +85,7 @@ RD Session host server has failed to create a new self-signed certificate to be
85
85
**User:** N/A <br />
86
86
**Computer:***computer* <br />
87
87
**Description:**
88
-
The RD Session Host Server has failed to create a new self signed certificate to be used for RD Session Host Server authentication on SSL connections. The relevant status code was Keyset does not exist
88
+
The RD Session Host Server has failed to create a new self signed certificate to be used for RD Session Host Server authentication on TLS connections. The relevant status code was Keyset does not exist
89
89
90
90
You can also check for SCHANNEL error events 36872 and 36870 by running the following commands:
91
91
@@ -103,7 +103,7 @@ wevtutil qe system /c:1 /f:text /q:"Event[System[Provider[@Name='Schannel'] and
103
103
**Keywords:** <br />
104
104
**User:** SYSTEM <br />
105
105
**Computer:***computer* <br />
106
-
**Description:** A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x8009030D. <br />
106
+
**Description:** A fatal error occurred when attempting to access the TLS server credential private key. The error code returned from the cryptographic module is 0x8009030D. <br />
107
107
The internal error state is 10001.
108
108
109
109
### Cause
@@ -186,9 +186,9 @@ If you can't renew the certificate, follow these steps to try to delete the cert
If you set up the VM to use an SSL certificate, run the following command to get the thumbprint. Then check whether it's the same as the certificate's thumbprint:
191
+
If you set up the VM to use a TLS/SSL certificate, run the following command to get the thumbprint. Then check whether it's the same as the certificate's thumbprint:
0 commit comments