• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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

M

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
You must log in or register to reply here.

Similar threads

D
Question Service Unavailable port 8443 Plesk Not Working
Replies
1
Views
9K
Kaspar@Plesk
Kaspar@Plesk
H
Question Windows server2019 Plesk - hangs the screen Please Wait
Replies
1
Views
3K
Peter Debik
P
S
Issue After changing IP of a server, slave DNS manager stop to work
Replies
11
Views
5K
jsextl
J
G
Resolved after migration - move the ip to the new server
Replies
2
Views
5K
Goodfred
G
G
Issue Plesk (or maybe CentOS) using the wrong IP address for outgoing traffic
Replies
1
Views
3K
gregconway
G
Back
Top