• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Subdomain alias not working after todays update

Z

zarza

New Pleskian
Hello guys,

Today our Plesk updated to:

OS: ‪CentOS Linux 7.7.1908 (Core)‬
Product: Plesk Obsidian 18.0.21 Update #4 , last updated at Dec 14, 2019 11:15 AM

And all our subdomain alias stared redirecting to Plesk login page.

We followed 4 months ago the KB How to add alias for subdomain in Plesk for Linux?

I have confirmed and rules are still there but not matter if plesk restart or plesk fix, subdomain alias are redirecting to Plesk login page.

Help!!!
 
Hello, I could not reproduce the issue with the steps from the KB article.
Plesk login page opens for a virtual host, which did not match any server name, and what is important SSL only. Make sure you added ServerAlias for HTTPS Apache.
 
Hello Eugene,

Yes, it is on both http/https and i have the rules in nginx part too.

It is working with same rules in servers that we stopped upgrade to obsidian and I even install a fresh obsidian to check and looks like there is no issue if is it is fresh installed, but happens after update from last obsydian to last update.

Most probably we will move those domains this weekend to onyx back.

Same settings on onyx works without issues. And plesk repair all -y does not fix it. It does not detect any error on it.
 
The only known difference between a new installation of Obsidian and an update from Onyx is that the feature of access to Plesk with 443 port should be disabled for backward compatibility after the update.
I would recommend trying to switch on / off with CLI.
More info in the docs: Customizing Plesk URL
 
You must log in or register to reply here.

Similar threads

Heinrich
Resolved node.js configuration in PLESK Obsidian 18.0.67 Update Nr. 3
Replies
3
Views
443
alvarezcruz
alvarezcruz
wakabayashi
Resolved Fail2Ban - Postfix not working for SASL (bug?)
Replies
4
Views
1K
mizar
mizar
weareimpulse
Resolved AbuseIPDB - spurious network activity from our server to third-party networks
Replies
3
Views
719
weareimpulse
weareimpulse
Dmytro
Forwarded to devs additional zone for subdomains after update
Replies
16
Views
3K
Dmytro
Dmytro
B
Issue High latency, unreliable performance & 522 errors on a Plesk server that ran fine for 6+ months
Replies
8
Views
2K
HHawk
HHawk
Back
Top