www.www.gpmaicloud.chat.gitlab.rubber-chem.ru Open in urlscan Pro
81.177.24.42  Public Scan

URL: https://www.www.gpmaicloud.chat.gitlab.rubber-chem.ru/
Submission: On July 21 via api from US — Scanned from US

Form analysis 0 forms found in the DOM

Text Content

HTTP ERROR 500.0 - INTERNAL SERVER ERROR

THE PAGE CANNOT BE DISPLAYED BECAUSE AN INTERNAL SERVER ERROR HAS OCCURRED.

MOST LIKELY CAUSES:

 * IIS received the request; however, an internal error occurred during the
   processing of the request. The root cause of this error depends on which
   module handles the request and what was happening in the worker process when
   this error occurred.
 * IIS was not able to access the web.config file for the Web site or
   application. This can occur if the NTFS permissions are set incorrectly.
 * IIS was not able to process configuration for the Web site or application.
 * The authenticated user does not have permission to use this DLL.
 * The request is mapped to a managed handler but the .NET Extensibility Feature
   is not installed.

THINGS YOU CAN TRY:

 * Ensure that the NTFS permissions for the web.config file are correct and
   allow access to the Web server's machine account.
 * Check the event logs to see if any additional information was logged.
 * Verify the permissions for the DLL.
 * Install the .NET Extensibility feature if the request is mapped to a managed
   handler.
 * Create a tracing rule to track failed requests for this HTTP status code. For
   more information about creating a tracing rule for failed requests, click
   here.

DETAILED ERROR INFORMATION:

Module   IIS Web Core Notification   AuthenticateRequest Handler   StaticFile
Error Code   0x80070542

Requested URL   http://www.www.gpmaicloud.chat.gitlab.rubber-chem.ru:80/
Physical Path   C:\inetpub\wwwroot Logon Method   Anonymous Logon
User   Anonymous



MORE INFORMATION:

This error means that there was a problem while processing the request. The
request was received by the Web server, but during processing a fatal error
occurred, causing the 500 error.

View more information »

Microsoft Knowledge Base Articles:

 * 294807