• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

SSL is not configured, yet sites are forwarderd using SSL.

R

rknabben

Guest
Strange problem:

I have a server running Windows 2003 with PLESK 7.5 for windows.

On this server is one domain name (lets refer to it as domain-a.com) which is a (frame-)forwarder to an external site.

There are several other sites configured on the server on the SAME IP.

NONE of the sites has SSL enabled.

However when the client types: https://www.hissite.nl
he will be forwarded to the external site configured for domain-a.com.

domain-a.com has NO SSL properties configured (Which in fact is impossible to configure during frame-forward congfiguration).

Why is PLESK forwarding all the https:// users to the remote host of domain-a.com ?

And more important: how do I stop it.

Even when I completely disable domain-a.com, I STILL get forwarded.
 
Back
Top