• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Adding new IP -> Server crashed!! -> BLUESCREEN!

MiBMiB

New Pleskian
Hi!

I have a very Big Problem and I need your help!
I have a Windows Server 2008 R2 running Plesk 11.0.9

In Plesk i have added an IP Adress. I have typed it in, like it was requested:
87.106.12.XX/255.255.255.255

With clicking "OK" the panel froze, I lost my RDP connection and the server crashed!
When trying a reboot I get a bluescreen. I only have Access to the system with the 1and1 rescue-tool

Screenshot Plesk:
screenpleskh07ng3owy5.jpg


screen_blue.jpg

What went wrong?
Please help me to restore my server!

BLUESCREEN TEXT:
"A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe"

Greetings!
MiB
 

Attachments

  • screen_plesk.jpg
    screen_plesk.jpg
    98.5 KB · Views: 5
Back
Top