• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Recent content by dakkafex

  1. D

    Issue 18.0.47 update #5 caused server to become unreachable

    Nope, neither shows up in the logfile
  2. 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...
  3. D

    Question How can I get my WebSocket running in NodeJS?

    yeah, dont bother, plesk developers dont know how to make modern working server software
  4. D

    Question Websocket Problem on wss

    there is no answer in this....
  5. D

    Question How can I get my WebSocket running in NodeJS?

    still nothing?
  6. D

    Question How can I get my WebSocket running in NodeJS?

    same issue here, watching this thread
  7. D

    Sogo Webmail

    it has now been 6 years and its the 12th most voted feature :)
  8. D

    Issue websocket issue with a docker image

    still having this issue
  9. D

    Resolved Problems running reverse proxy on docker container

    fixed this issue
  10. 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...
  11. D

    Issue websocket issue with a docker image

    bump
  12. 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...
See more
Back
Top