Search results

It is always somehow tricky to help with customized configuration if nginx -t does not show an error now, then you should be able to rebuild all, also the certs for the domain.

just a guess, comment out (#) line 41 and run nginx -t to see if the error is gone and if yes try to rebuild the config files

how looks your /etc/nginx/nginx.conf arround line 41?

Do you have any custom directives set in Nginx or are you not using the default Nginx setup provided by Plesk in any way? you can try to login to your plesk panel and use the extension "Webserver Configurations Troubleshooter" and rebuild configuration files or via cli Plesk Repair Utility: Web

if it works for a domain, additionally there are several knowledgebase articles how to enable it for all domains at once How to enable DKIM signing for all domains on Plesk for Linux How to add SPF record for all domains on Plesk server? and How to check which domains have DKIM signing enabled...

there are global settings server wide and you can do this also on Domain level in Plesk. Usually you would carefully enable this settings step by step and check each step afterwards. There are a lot of online tools arround which tests spf, dkim & dmarc settings if everything is setup correctly...

well I am not an Cloudlinux Server User, but based on this documentation it is supported if your Key is valid for it Software Requirements for Plesk & Important Facts About and How to Update to Plesk Obsidian

thats all I found about it yet in the changelogs: As a workaround until you figured out the real issue: you can try to set in the panel.ini the [ext-notifier] unavailableMailPorts true to false, this should hide the message. But in general thats helpful to get such an warning if...

ok seems to work at least with IPv4, perhaps it has to do with see: IPv6 traffic doesn't work anymore after set System policy for outgoing traffic to Deny: No route to host.

whats the output when you do this from your System # telnet smtp.gmail.com 587 get it connected?

Honestly, I assume this has nothing to do with Plesk but with your local infrastructure. So I can't help you much more here. Maybe this will help: IP Addresses Management & Running Plesk Behind a Router with NAT

Unfortunately there is no detailed documentation about this. But I think Plesk is using smtp.gmail.com to test if the defined ports 25 & 587 are open to the outside world. So you should test from your system if you can reach it via telnet on port 587, alternatively they can probably be...

perhaps you have a different plesk edition as I I just checked it with the extension Panel.ini Editor and on my Systems it looks like:

please check via panel.ini extension or CLI /usr/local/psa/admin/conf/panel.ini what is configured for unavailableMailPorts, unavailableMailPortsHost , unavailableMailPortsList and so on... and test if you can reach it

based on the changelog I realy wonder if this microupdate will fix the issue here, because it refers to servers without installed DNS server

Come on guys, this is just gonna end up in endless discussions where no one really gets anywhere. Everybody has brought more or less valid arguments for pro and con. It is the current decision of Plesk not to release php 7.4 for Onyx. Looking around the forums, there are lots of requests for new...

will plesk for your domain the master or slave? if master is the BIND DNS server component installed and the service running? how looks like you dns & soa for your domain and even it seems the namserver ip does not answer any dns query and timed out.

since you can reproduce it, please fill out an report

you might add your OS to the report, to show it also happens on Debian 9 systems

seems to be this issue see: Forwarded to devs - [PPP-47160][Plesk 18.0.23 on CentOS 7] Internal error on Server-Wide Mail Settings page