Search results

There are some tips here regarding that: https://serverfault.com/questions/623036/does-postfix-reject-spoofed-senders/623219

https://support.plesk.com/hc/en-us/articles/4407400262674-Plesk-websites-secured-by-Let-s-Encrypt-certificates-show-ERR-CERT-AUTHORITY-INVALID-warning-after-September-30-2021

The DNS is ok: # host serene-sutherland.3-1-194-247.plesk.page serene-sutherland.3-1-194-247.plesk.page has address 3.1.194.247 You issue is that on AWS you need to allow the incomming traffic for the Webserver ports: # nmap -p80,443 3.1.194.247 ... Note: Host seems down. If it is really up...

A VM you can get anywhere you want to. For openWRT you can find the documentation here: Documentation I personally use it on my dedicated server that I virtualized to forward the trafic from IP x Port x to IP y Port y As example: Maybe try to google for something like "create failover switch"

I did it with Plesk Email Security installed and worked for me. Just make sure to do it according to: https://support.plesk.com/hc/en-us/articles/213410369

Since you dont manage the DNS for plesk.page, you cannot use wildcard certificates. Generate one with only the domain, no wildcard/subdomains etc

Many hosting providers do offer a "failover" IP service for such scenario that can do such. If you want to do such on your own you probably need a small VM with that 1st IP that will be in the DNS that then does route the traffic to the Plesk server, as an example with OpenWRT

If you create the domains on different subscriptions with no hosting and set the DNS correctly, this can be done. Outgoing IP can be set to the subscription one...

Hello Pleskians, If you're using or used this extension, please provide me with feedback :) What is it missing that you would need? How easy or difficult was it to set it up? Anything other complaints or things you like about it? :) TawkTo Extension: TawkTo Best Regards, Martin

You can vote here for this feature: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/38447926-allow-rest-api-for-reseller-an-customer

If only one connection has the problem and changing network helps, then probably the IP where you have the issues did get banned as explained by Monty.

Last time I saw such was because reload was failing due to too many files open

SSL received a weak ephemeral Diffie-Hellman key: how to solve this problem

https://talk.plesk.com/threads/18-0-34-code-editor.360126/

Hi all, We did submit a bug for this under the ID PPPM-12860, we plan to fix this in an upcoming update

Do try it over SSH: plesk bin license -i ACTIVATION_CODE

> [2021-02-14 13:49:49.897] ERR [panel] DB query failed: SQLSTATE[HY000] [2002] No such file or directory: This looks like MySQL being down, check the service and mysql log but that should not be related to the original issue

Probably your server does use NAT, so the IP of your Server is 10.15.0.7 and then outside your server your provider does route the traffic over 104.248.1.x This is quite normal in most Cloud providers, and many VPS

Plesk does not update certain Packages, as they will require a reboot (Kernel, etc.) You can update them manually over SSH

Any additional errors in the panel.log? What OS and Plesk version are you using?