• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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. D

    Issue 18.0.47 update #5 caused server to become unreachable

    18.0.47 update #5 caused multiple of our servers to become unreachable. It could also not be pinged and it was unreachable by ssh, the only thing that fixed was manually restarting the VPS instances. I have tried digging through the logs, but I didn't see anything that looked like something...
  2. D

    Resolved Problems running reverse proxy on docker container

    Im running into a problem hooking up a domain to a docker container. The container works when i go to the root url of my server and the mapped port directly. But when I try to hook up a domain to it with the docker proxy rules i get ERR_INVALID_RESPONSE in the browser. How do i fix this...
  3. D

    Issue websocket issue with a docker image

    So im trying to set up an image that uses websockets but i cant get it working, i keep getting a failed: Error during WebSocket handshake: Unexpected response code: 200, error i tried adding location /socket.io/ { proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade...
Back
Top