Search results

I have the same issue. This seems happen only with Firefox, not with Edge. If I open a Windows Sandbox and install Firefox the issue is not present. Strange issue. It happens if I login normally of with Plesk login one time link. It never happen only on Plesk Dashboard. I tried to reset...

Thanks for your question @Muhammad ali Muhammad . If you try to install and use Live Helper Chat with Plesk you need special configuration on Plesk as Live Helper Chat cannot work correctly because Plesk use HTTP 2 using Apache and Nginx so this cause CORS issue if you don't add special server...

@Peter Debik can I ask last thing in this topic? I was able to set the custom hostname and edit the DMARC to make Delivery Status Notification not rejected just do you know how I can customize the plesk bounce email address that appear on the Delivery Email?

Seems Ubuntu need a particular manual network configuration to avoid the dynamic IP even if the server has just one static IP. More info can be found at my post here.

Seems Ubuntu need a particular manual network configuration to avoid the dynamic IP even if the server has just one static IP. More info can be found at my post here.

I use IONOS provider with Plesk and Ubuntu 22 With the Plesk team the issue seems to be related to the server IP that for the hosting provider they say are static but that in the Ubuntu config file they seems to be dynamic. root@peopleinside:~# ip a | grep 82.XXX.77.57 inet 82.XXX.77.57/32...

Hum now seems changing the DMARC has delivered the Delivery Status Notification in the spam folder. The email alert me that I send an email to a inexistent Gmail account. Interesting so seems to be an issue with the DMARC. Good to know so seems I cannot have reject in the DMARC

In my server i configured SPF, DKIM and DMARC. Those record are checked by me sending a test email from my domain to for example Gmail then checking email headers confirm all records are passed. Recently I discovered that if I use the default myhostname in the file /etc/postfix/main.cf I am...

This are my logs: My downtime started at 12:05 I think so seems related to named service stopped.

Hi, I want inform you that I was able to activate a Plesk ticket subscription and I can say for now, the second day, about two issue reported I'm not resolving. I will continue to try to investigate but currently... currently I dont see any solution. It's a good news read developers checked and...

I have the same issue, seems. Currently I'm not understanding why this happening. I think when named service not listening I have a big downtime: server and domains are no more reachable and I need reboot the server by the IONOS hosting panel so from the provider. I'm trying since yesterday...

Thank you! From the guide I understand I need some code in the /usr/local/psa/admin/conf/panel.ini The strings that I need to add can be like this: [named] Service.RestartSec = 7 Service.Restart = always

Consider my free month ended so I cant. I'm trying to understand why this named service create issue and how I could solve it. Looks to be something inside Plesk.

May 30 12:05:47 peopleinside named[1006]: no longer listening on 82.XXX.77.57#53 Issue with downtime happen again, seems create a script with a code that check if named service are running never works. #!/bin/bash string1=`/usr/bin/systemctl is-failed named` string2="failed" if [ "$string1"...

May 30 12:05:47 peopleinside named[1006]: no longer listening on 82.XXX.77.XX#53 I think this is the log that cause the downtime. Seems I am unable to find how to resolve this issue that happen often

Hi, today I got a new downtime that require to restart the server from IONOS panel. From the Plesk log I see: Could be this errors the cause of the dowtime started at 12:14?

The test: https://talk.plesk.com/threads/cors-stop-to-working-using-http-2-plesk-plesk-obsidian-version-18-0-52.369871/post-928058 The resolution: https://talk.plesk.com/threads/cors-stop-to-working-using-http-2-plesk-plesk-obsidian-version-18-0-52.369871/post-928059

@Kaspar you helped in the final resolution. Comparing Apache & Nigix settings page I found that on my not test domain the option Smart static files processing was checked. I really don't remind to have checked this by muself, also the description on this option say to disable only for test so...

I tried and on new subdomain test.peopleinside.it it works. Now I have to understand why is not working on my side, on the original live chat that I use...

For today I think I will stop. I'm too much stressed, this HTTP 2 is really not working was all ok and a day after all broken without touching nothing. Also I'm surprised there is no way to understand why is not working :D I need relax.