Recent content by emilyy3

Thanks for the clarification. That actually helps narrow things down. My setup does have IPv6 enabled, so it makes sense now why Anonymous FTP is failing while normal FTPS logins through WinSCP continue to work correctly. I wasn’t aware that Anonymous FTP over IPv6 is currently unsupported, so I...

I also have the same question because I’m facing a very similar issue on my setup. Everything works fine with FTPS connections through WinSCP using normal user credentials, but clicking on Anonymous FTP immediately throws a 500 Type Error. I already tried running the Diagnosis & Repair tools and...

IS there anyone who can guide?

I actually have the same issue, and I’m seeing very similar symptoms with the 502 bad gateway when trying to access the admin panel. In my case too, it looks like the login page only offers the repair kit option, and even that doesn’t work properly, which basically locks me out entirely. What’s...

Good to know it’s already been identified (PPP-71520). I’ll stick with the browser zoom workaround for now and keep an eye out for Plesk Obsidian 17.0.78. Hopefully the fix resolves the layout regression across all localized views, since it’s been quite disruptive when managing multiple domains...

I actually have the same issue and I’ve noticed similar layout problems in the Plesk interface when switching away from English. In my case as well, the domain view breaks in the admin panel and everything gets stacked vertically instead of staying in a proper row layout. It makes the interface...

Thank you for your reply and for pointing that out. It turned out the issue was related to the customer account context I was working with. After reviewing the account type more carefully and repeating the process correctly, the password change worked as expected. Everything is fixed now...

I’m actually dealing with the exact same issue right now and it’s been really confusing. I also get the confirmation message saying the password was changed successfully, but when I try to log in with the new password it doesn’t work only the old one does. I even tried repeating the process and...

Thanks for clarifying that makes sense now So if I understand correctly, the key point is that Postfix only allows a single transport_maps definition, and Plesk already manages one by default. Instead of redefining it, the correct approach is to extend the existing transport_maps line and...

I’m actually running into the same issue and seeing that exact warning about transport_maps being overridden. It looks like Postfix (or Plesk, in my case) already defines a transport_maps entry earlier, and when we add another one at the bottom, Postfix just warns that it’s replacing the...

I hadn’t realized that the missing A and MX records would prevent PHPMailer from connecting reliably. I’ll review the DNS settings in Cloudflare and either create the proper A record for the mail subdomain and update SPF accordingly, or follow your suggestion and configure PHPMailer to use the...

I’m encountering the same issue as well. I’m also trying to send emails from a website using PHPMailer with Plesk’s SMTP settings, and nothing seems to go through. Sometimes I get SMTP connect() failed, but other times there’s no error at all. I’ve double-checked that SMTP is enabled in Plesk...

Thanks for the suggestion. Yes, I’ve already tried running the command with the --no-truncate flag, but the output still appears to be truncated at around 34 characters for the domain name or password. That’s why it feels more like a UI or formatting issue rather than a command-line limitation...

I have the same question and I’m also noticing this behavior. It does look like a bug to me, especially since longer domain names or passwords are getting truncated with .... I’m running into this as well and would like to know if this is a known issue or if there’s a workaround.

Is there anyone who can guide me?