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

Resolved Assistance Needed: Domain Issues with Plesk on Ubuntu 22.04 x64

MMM

New Pleskian
Hello everybody,

I hope this email finds you well. I am currently using a Plesk (Web Admin SE) on Ubuntu 22.04 x64 vultr platform and have been experiencing some issues since adding a new domain, digitalspikes.com.au, to my platform. Previously, I had no problems with the first domain added in Plesk, but now the new domain is not working properly on WordPress.

Here are the real-time logs I receive from Plesk when attempting to browse the site:

2023-08-06 00:46:06Access162.158.2.55301GET / HTTP/1.1
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
162nginx access2023-08-06 00:46:06Access162.158.2.55301GET / HTTP/1.1
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
162nginx access2023-08-06 00:46:06Access162.158.2.55301GET / HTTP/1.1
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
162nginx access2023-08-06 00:46:06Access162.158.2.55301GET / HTTP/1.1
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
162nginx access2023-08-06 00:46:06Access162.158.2.171301GET / HTTP/1.1
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
162nginx access2023-08-06 00:46:06Access162.158.2.55301GET / HTTP/1.1
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
162nginx access2023-08-06 00:46:06Access162.158.2.171301GET / HTTP/1.1
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
162nginx access2023-08-06 00:46:06Access162.158.2.55301GET / HTTP/1.1
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
162nginx access

I would greatly appreciate it if someone could provide some guidance or assistance in resolving this issue. Your expertise will be invaluable in getting my new domain up and running smoothly.

Thank you in advance for your help and support. I look forward to hearing from you soon.

Best regards,

MM
 
Hi @MMM, when I try to open your domain, it ends up in a redirect loop. Such loops can exist when the www/non-www preference settings between web server and website do not match or when the SSL/non-SSL settings do not match. For example when you set a URL preference in "Hosting settings" to "www", but in your website settings you define the site's URL with non-www, the website redirects to non-www, then the webserver redirects to www, then the website redirects to non-www again and so on. To fix this: It is best to let the website decide and to set no preferences in "Hosting Settings".
 
Thank you, Peter, Is there troubleshooting steps available to trace the scenario. I have removed and added new certificate with no luck.
 
Please verify that you have these settings in "Hosting Settings" of your domain:

1691336123181.png

In most cases that will already be ally ou need, because this way you leave control over forwarding to your website.
 
Thank you Peter, It resolve the issue. I can browse the website.
I have the same setup on the first website and it perfectly works.
Do I have to disable the settings on the first domain I added?
If I disable the setting how can I force the URL to force http to https?
 
You do not have to change the settings on the existing website if it works there. The reason why it works there is that both, web server and website configuration are in sync. For example if the base URL in a Wordpress website matches the preferred URL in Hosting Settings, no redirect takes place. The redirect loop is only entered when both settings contradict each other.
 
  • Like
Reactions: MMM
Back
Top