• 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.

Question (VPS) Cloudflare, Gmail and Other Plesk Panel 8443 (2 minutes - slow read)

kaw.one

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.57 Update #4
Hi everyone, brothers, sisters, gurus, masters and sifus...

I've searched for solution since a few days ago but found nothing so I had to register acc to start posting.
Here's some question and answer (that I found with reading + trial and error while writing this post).

1. (Question) Cloudflare DNS Proxy issue:
After on CloudFlare's, I can't access my server.domainname.ext Plesk panel.
It keeps redirecting to Plesk panel login page, right after I pressed 'enter / login'.
Error for server.domainname.ext or server.domainname.ext:8443 or server.domainname.ext/login_up.php.

On CloudFlare:-
- Most DNSes are Proxied (Orange cloud)
- CloudFlare's SSL is set to Full (Strict)

On Plesk:-
- VPS was renamed under server.domainname.ext
- The 'domainname.ext' has its own DNS zone
- The 'domainname.ext' is not in use. Dedicatedly meant for VPS only
- Domain Setting: <domainname.ext> forward to <server.domainname.ext>
- Let's Encrypt (Wildcard) is actively running for domainname.ext
- All CloudFlare's iPv4 and iPv6 have been whitelisted
- NGINX is actively running
- Plesk's CloudFlare DNS extension is actively sync

On Device System:
- Cleared browser's caches and cookies
- Tried 3 different WiFis

Temporary solution:
- I've changed most DNSes to 'DNS only' (Grey cloud) and everything working fine like it used to be.
- If I change most DNSes to 'Proxied' (Orange cloud), the Plesk panel login page redirect happens again.

// How do I fix and overcome this issue?
// Should I delete / remove '<domainname.ext> forward to <server.domainname.ext>'
// Should I create a subdomain for <server.domainname.ext> and Let's Encrypt it?
// Should I stop using Let's Encrypt on <domainname.ext> and generate one from CloudFlare?

.
.

2. (Question but SOLVED) Gmail POP3 error:
For 'Check mail from other accounts' in Gmail's setting.
It shows 'Connection timed out: There may be a problem with the settings you added.' on 995.
- Default_DomainKey DKIM, DomainKey and DMARC added to both CloudFlare & Plesk DNS record
- 'A : mail' on CloudFlare's DNS Record changed to 'DNS only' (Grey cloud)
- Email Routing to Gmail account (on CloudFlare's Email setting) - Optional
// All working fine now.

.
.

3. (Question but SOLVED) <otherdomainname.ext>:8443 issue:
Always not secured and need to press 'Advanced' then 'Continue to <otherdomainname.ext> (unsafe)'
- Let's Encrypt (Wildcard) is activated on <otherdomainname.ext>
- Good Answer: https://support.plesk.com/hc/en-us/articles/12388004435607
- Best Answer: https://support.plesk.com/hc/en-us/articles/12377772259223
// I accept it but please help to vote HERE. Thank you!
 
// Should I create a subdomain for <server.domainname.ext> and Let's Encrypt it?

Definitely not a good option hahaha I had wasted half an hour just to recover back.
 
Back
Top