• 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 Autoconfig works not with Wordpress

Huskynarr

Huskynarr

Basic Pleskian
Server operating system version
Debian 11 (bullseye)
Plesk version and microupdate number
18.0.60
I am currently working on getting autodiscover and autoconfig to work.

After numerous hours with Cloudflare, ISP and Plesk I am now at the point:

Webserver without NGINX/Htaccess rules work on the /mail/config....
I tested this with:
curl https://domain.tld/mail/[email protected]

However, if I try an alternative domain on the same server, on which Wordpress runs with htacces/nginx rules, the response is then the HTML code of the website.

However, this only works with Autoconfig, not with Autodiscover. Nothing appears with this.

Are there possibly KB entries for this that I can't find? I suspect that there are two independent problems.
 
You must log in or register to reply here.

Similar threads

A
Resolved Mail autodiscover request generate an http 400 error
Replies
6
Views
917
Sebahat.hadzhi
Sebahat.hadzhi
D
Issue Plesk Premium Mail Autodiscover
Replies
8
Views
7K
Elompenta
Elompenta
Lenny
Resolved Seeking Assistance with API Communication Issues via SSL on Plesk
Replies
4
Views
3K
Lenny
Lenny
O
Resolved [PPP-54866] Cannot change autodiscover to port 587
Replies
1
Views
1K
Nik G
N
TimReeves
Issue Mail AutoConfig not working, returns 400 Bad Request
Replies
4
Views
3K
ducktales
D
Back
Top