• 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 HTTP/3 enable for panel redirects to localhost when changing E-Mail password

andreios

Regular Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.61 #3
I tried to change the password for an E-Mail (the admin E-Mail).
But after pressing 'OK' it redirected to this:
Code:
https://localhost:8443/smb/email-address/list/domainId/3
The password was changed anyway.
I checked if HTTP/3 is enabled:
Code:
plesk bin http3_pref --status
HTTP/3 is enabled for nginx
But I was sure I had enabled it for both -nginx and -panel. So I disabled HTTP/3 for panel. After disabling, I tested it again, no problems.
Probably the HTTP_HOST variable?
 
Can't comment on the e-mail aspect, as it's not something we've needed to do but, the initial question about the results of the "status" query has been raised before / answered before in amongst this post: Resolved - http/3 supported by plesk?

However, that ^^ was before Plesk encountered issues with MFA / Cloudfare etc (see several separate threads) which, has resulted in some 'temporary changes' by Plesk. Brief details and a link to the Plesk changes is here: Resolved - http/3 supported by plesk?
 
@andreios thank you for pointing that out. After the issues with HTTP/3 we're considering it an experimental feature. HTTP/3 support is disabled by default for all new installations now. Because it's experimental I would recommend not using it for the Panel and with caution for websites.
 
I have the same issue, something is wrong enabling HTTP 3 and Plesk panel, it redirects to "localhost:8443" this happens to me when I click on extension Cloudflare to manage DNS.

Did you found a solution @andreios ?
 
I have the same issue, something is wrong enabling HTTP 3 and Plesk panel, it redirects to "localhost:8443" this happens to me when I click on extension Cloudflare to manage DNS.

Did you found a solution @andreios ?
FWIW Plesk Panel HTTP/3 was disabled by Plesk, by default in 18.0.61 mu3 > https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18061-mu3

However, it continues to be supported for all hosted sites. You can verify this via the CLI & Curl or even the Plesk Panel itself (Panel.ini Extention). We have zero issues with HTTP/3 in it's current Plesk config, works perfectly for us, but we don't use Cloudfare at all, so that might a factor in your case, maybe?
 
I have the same issue, something is wrong enabling HTTP 3 and Plesk panel, it redirects to "localhost:8443" this happens to me when I click on extension Cloudflare to manage DNS.

Did you found a solution @andreios ?
No, no change. I still happen to me too if I try to enable it for panel. Seems they don't work on currently.
 
Back
Top