• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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