Issue URL Alias Login Plesk

[xx1Andy1xxx]

Server operating system version

Ubuntu 20.04

Plesk version and microupdate number

Obsidian

How can I prevent any url alias from pointing to the Plesk login page or enabling a redirect

Example:

If I then enter micha.example.com instead of www.example.com, I can be forwarded to the Plesk login page without specifying the port (8443).

How can this be stopped???

 

[Kaspar]

Remove the wildcard DNS entry for example.com?

 

[xx1Andy1xxx]

There is no Wildcard DNS configured only the Domain Name with www and without www.

Nevertheless, I can call up any imaginary domain alias and get to the Plesk login page. That is not sure !!!

 

[Kaspar]

Perhaps I am misunderstanding your issue. However if you can access Plesk via any random sub domain (ie foo.example.com, bar.example.com or my-name-is-kaspar.example.com) than there must be a wildcard DNS record configured for that domain. Otherwise traffic/requests could not be routed.

 

[xx1Andy1xxx]

I have now set up the server again and only the host name of the provider is configured, but I can still set any host name, but not with "https" but only with "http". Here only the DNS configuration of the provider takes effect.

 

[xx1Andy1xxx]

I'll paste the URL I'm talking about.

Here some examples:
Web Server's Default Page or https://google.h2988430.stratoserver.net/login_up.php
Web Server's Default Page or https://amazon.h2988430.stratoserver.net/login_up.php
Web Server's Default Page or https://daddy.h2988430.stratoserver.net/login_up.php

Every Name you TAKES WORK. I think thats a Bug by the Provider ?

 

[Kaspar]

Ah, I see, it's and URL provided by Strato. It's a bit of strange setup, but I would not call it a bug.

So as a possible solution, how about setting a hostname from a domain you own?

 

[Bitpalast]

Every Name you TAKES WORK. I think thats a Bug by the Provider ?

It's not a bug, it's a feature. You get a domain, and they have a wildcard on the subdomains of that domain. Choose @Kaspar 's suggestion to avoid this issue. You might extend it so that you don't use your main domain name for the host name, but your own subdomain of it, e.g. do what your provider does, but do your own configuration better to match your requirements.