Search results

Igorg, I had a vhost that was all nginx.... meaning FPM application served by nginx and unchecked the proxy mode. then I needed to switch it to "FPM application served by apache"... the site was working (some not all), but odd things were happing? like a php would work, but maybe not the...

question: is this a bug... the following situation: IF you have "FPM application served by nginx" selected on the PHP version AND on the Apache & nginx Settings page... you have Proxy Mode = NOT checked... that is a problem, correct? those 2 items can't exist together?

I have seen a few threads and users (who like me).... want to know but are confused on the details. I'm slowly getting the facts in order and close to understandings all the variables... but not quite there? My hope is this thread can help EVERYONE who wants speed and security for their Plesk...

no. WAF is only for apache... UNLESS, you use nginx plus (the paid version) and fyi. if you use atomicorp ASL, no WAF either when using "FPM application served by nginx" uhm, maybe I'm wrong because I don't know exactly what the checkbox for proxy does/doesn't do? FYI. I ran a simplistic test...

I wanted to inquire if that is an option. Could it be done and not cause problems with Plesk as a whole? thanks

thanks bulent!!

TITLE: the "from" field when viewing log files doesn't work PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: ‪CentOS Linux 7.2.1511 (Core)‬ Product Plesk Onyx Version 17.0.17 Update #18, last updated on Mar 7, 2017 03:24 AM PROBLEM DESCRIPTION: when view log files (either a single one or ALL...

uhmm... great info: https://www.smashingmagazine.com/2016/02/getting-ready-for-http2/ and this: the percentage is much higher than I thought? http://caniuse.com/#search=http2 anyone with a production server/website with a ecommerce site on it using http2? just wondering if you have any "tips...

thanks !! so older browsers (or some browsers in general) -- I'm positive some people have them and don't upgrade....will not work if you have http2 turned on? and then what happens? They go to your http2 website and it shows an error? QUESTION - security advisor can turn on http2 per domain...

In theory, from what i've seen... it all good? is anyone running all 4 of those softwares on your server? does extension Security Advisor work as planned? where you can turn off/on http2 for a given domain with click of button? if all is turned on/working --- a site visitor whose browser...

sorry... that worked... it was cut and paste error :) THANKS UFHH01 !!!

thanks, but [hostname ~] >> /usr/local/psa/admin/sbin/mailmng-outgoing --add-to-whitelist --sysuser=tortix ERROR:outgoing:'getpwnam(): name not found: tortix\xe2\x80\x8b' any thoughts?

hello, I have atomicorp ASL (the gui or asl web) installed. CentOS Linux 7.2.1511 (Core)‬ Product Plesk Onyx Version 17.0.17 Update #17, last updated on Feb 27, 2017 09:33 PM On the ASL Gui, there is a button to send a false positive report, the ASL code using php to send the report via...

in this file: /usr/local/psa/admin/logs/panel.log i found this type of entry multiple times: [09-Jan-2017 04:07:36 America/New_York] response=%27%91%7Erp.... lots of crazy characters....A%9F%9B%0CON%AA [with a domain email address here] it turns out (I think) this entry corresponds to dr web...

while I'm still trying/struggling to find a solution... this "499 issue" does not happen on any other sites the client goes on? it ONLY happens on this vhost. To me, that says it's an issue related to my server, even though everything points to the client having the issue :(

hello, situation: I had old plesk and apache before upgrading to onyx and going to nginx. a client goes to domain.com/admin/index.html (admin is password protected) BEFORE upgrade, the client must enter user/pass to SEE the index.html page AFTER upgrade, the client can 'see' the index.html...

thanks... i had my hosting support team basically come back with the same answers. (from nginx statements, etc. etc) While I don't disagree and guessing the answer/solution doesn't exist? I forget what I was doing today, but the 499 happened to me: see attached image it was a site home page...

yeah... its very weird, odd. i can't explain or figure out how "few/limited" links got changed to the preview link. one theory, maybe technically I did use the preview on the old server and just forgot that I did? and when upgrading... the old link was left in place? i could see that...

thanks Peter for the help... but this is what I know: 1) my client is not doing any of the 4 examples you provided ... this is my client using the browser in a password protect directory, updating DB records, etc. (ie. its not a random site visitor) 2) the browser error page can show up...

updated... this is over my head, but these 2 links list items about "time out settings"? http://stackoverflow.com/questions/15613452/nginx-issues-http-499-error-after-60-seconds-despite-config-php-and-aws/15621223#15621223 http://stackoverflow.com/questions/12973304/nginx-499-error-codes...