Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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.
Thats strange. Try running the # plesk bin admin --disable-access-domain command over SSH. Does change the {{ get_password_link }} link to the server hostname?
The # plesk bin admin --disable-access-domain command sets the control panel to be accessed on port 8443. Looking at the output from the SQL query you posted your control panel URL already contains the 8443 port (pl1.<domain>.<tld>:8443). So it should not change much for you. However my hope is that, somehow, it does change the {{ get_password_link }} url for you. No guarantees. But it's worth a shot I think and should not break anything.
If I am not mistaken the password reset email template also uses the {{ get_password_link }} tag. So you could do a "forgot my password" for testing purposes. No need to create another customer I think.
If you're not feeling comfortable changing or testing things on your server you can always contact Plesk support to have them investigate the issue.
that link already used the hostname. So created a new user, set it to self-activate. Good news and bad news.
The good news: something changed and {{ get_password_link }} is now properly filled in.
The bad news: {{ hostname }} still gets filled in, but is no longer a hotlink like it was before