• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. T

    Issue Plesk outgoing mail limit - BCC field

    Wow, this is insane. This is not even a bug, it as a serious functionality fail. They even stated here Count each recipient (Including to, cc and bcc headers) as individual limit for Outgoing limits that if using Postfix it is being counted. Not so. And this was in 2014 -- three years ago! I...
  2. T

    Issue Plesk outgoing mail limit - BCC field

    It seems plesk does not count number of recipients but number of emails sent for its outgoing mail limiter. I have a customer sending hundreds of emails using a BCC field, and even if limit is set to 50, everything goes right through. Is there some setting to limit the number of recipients for...
  3. T

    Resolved Plesk outgoing mail limit - BCC field

    oh... wrong forum... its Plesk for Linux (postfix + Centos) I am running this on...
  4. T

    Resolved Plesk outgoing mail limit - BCC field

    It seems plesk does not count number of recipients but number of emails sent for its outgoing mail limiter. I have a customer sending hundreds of emails using a BCC field, and even if limit is set to 50, everything goes right through. Is there some setting to limit the number of recipients for...
  5. T

    Resolved Websocket Error 400, Docker & nginx

    Ok, I fxed it by using this in additinal nginx directives, after turning on he docker proxy rule: location ^~ /api/v3/users/websocket { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $http_host; proxy_set_header X-Real-IP...
  6. T

    Resolved Websocket Error 400, Docker & nginx

    OK, if I put only the following everything except for web sockets works. location ~ ^/.* { proxy_pass http://192.168.0.5:33000; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for...
  7. T

    Resolved Websocket Error 400, Docker & nginx

    I removed the docker proxy rules for the domain completely. As I can not add map in the additional nginx directives, I just removed the line: proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto; So it reads out now as below (just to test): location / { gzip off...
  8. T

    Resolved Websocket Error 400, Docker & nginx

    This is supposed to work as from: mattermost-nginx/mattermost at master · mstrpupt2/mattermost-nginx · GitHub map $http_x_forwarded_proto $proxy_x_forwarded_proto { default $http_x_forwarded_proto; '' $scheme; } server { listen 80; location / { gzip off; client_max_body_size 50M...
  9. T

    Resolved Websocket Error 400, Docker & nginx

    I can telnet to 192.168.0.5:33000 and using GET / HTTP/1.1 HOST: HOSTNAME and I get the page in plain text on the console, if I use the page through 192.168.0.5:33000 I get the full functionality, eveything works. I am missing something in nginx setup, to get the websocket part of it working...
  10. T

    Resolved Websocket Error 400, Docker & nginx

    location /api/v3/ { proxy_pass http://192.168.0.5:33000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; } I tried it all, docker ip, mapped ip... it just makes no difference
  11. T

    Resolved Websocket Error 400, Docker & nginx

    The question is, how can I get websocket to work through nginx reverse proxy ?
  12. T

    Resolved Websocket Error 400, Docker & nginx

    I have a docker app on latest Plesk Onyx running (mattermost) and it works perfectly when opened directly through server IP and Docker mapped port (192.168.0.5:33000) Everything works great. The problem is when I try to make it work through NGINX proxy. If select a domain and set Docker Proxy...
Back
Top