Search results

like this? Forwarded to devs - Roundcube "Connection to storage server failed" when securing mail with Let's Encrypt certificate

if you look at the webmail configs for domains that do not have webmail activated you will see that they are just comments: I don't think there will be much impact on the loading of the nginx/Apache services! ;) As far as regards Apache config files for domains directly served by nginx... they...

One more thing: Initially I tried to use an IAM identity that has "AmazonS3FullAcces" policy attached to it, but it wasn't accepted. I had to use an IAM identity with full administrative access to cut through...I don't like that at all. Probably there is a subset of rights that will be enough...

Rob, after all... it was it! I just made a test (backup just finished and checked it was indeed uploaded) and that "Path" is exactly the folder path within your bucket, with a couple of "quirks": The folder name can't be empty nor "/" The folder must be created beforehand using the AWS...

No prob! Nice to hear that you're OK now! :)

Hello! If you have updated the verify_peer variable to false and you're still unable to connect, then I'm afraid you are not having the "exact same issue", but just the "exact same symptoms": you're much better off opening a separate issue in Plesk Onyx for Linux, maybe citing the fact that you...

Sorry Rob, it was a really long shot... My apologies for wasting your time!

I don't have direct experience with this, but I believe that "path" is just "path inside the bucket" (like, "/", or "/my-backups", or maybe just empty) P.S.: I hope you'll have changed the IAM secret by now: not much of a secret anymore... Forget this, I'm an idiot...

I think this is a very similar situation: Resolved - Unable to forward requests from nginx / apache

That's not necessarily true... try doing it in 3 steps Open "Apache & nginx settings", deselect "Proxy mode", click "OK" Open "Apache & nginx settings" again, put your "location /" config in "Additional nginx directives", click OK again Be happy!

rDNS, some examples from a quick Google search... Postfix Configuration Parameters setting correct PTR record for domain and postfix email server Require PTR lookups for postfix Postfix Reverse DNS Lookup: 450 4.7.1 Client host rejected and... have you noticed that tools such as mxtoolbox and...

... because the webmail address is visible by every company employee using webmail, and, most important, it is visible by the CEO, CFO, CTO, etc., while the clients configuration is generally visible by the IT monkeys (that's me, no offense taken by anybody, please!). As far as the rest, I'm...

Totally agree. Partially agree: There is always the rDNS issue and some picky server could test for it There is a general expectation (mind you, not any technical reason...) that whatever you put in the MX record will also be what you'll have to configure your clients with Disagree: Having...

:eek::D

Sorry if I insist, and please forgive me if I'm missing something: "telling" your customers (or prospects...) that "with you" they will have "mail.theirdamndomain.com" as their mail "endpoint" can be of some value, as you can tell them that "with you" they will not be "locked in" and the day...

ah, ok, I see! wildcard under wolf.com, so users can use client-com.wolf.com and have their ego happy.... P.S.: actually a "partially happy" ego! TBH I don't see much value added in this solution...

Then why do you need a wildcard certificate?

You sure about that? I have the impression that SNI is in fact possible (server side), but again limitation in the possible number of supported domain names and clients limitation still hold and therefore this is not a generally viable solution. I have always sustained that using...

I found how to downgrade my test VPS to the previous "PHP-FPM by OS vendor: yum downgrade php\*-5.4.16-43.el7_4 After that: I took a snapshot of my VPS, so that I can restart from that point in time. Plesk listed the new "php 5.4.16-43.el7_4.1" packages as available I had already disabled...

Thanks @IgorG ! I've setup a test machine with a trial license and I'm still confident I can duplicate the issue (what a stubborn old man I am!), but I'm facing a problem: during the setup process my "PHP-FPM by OS vendor" has been already updated to the latest version. To duplicate the issue...