Skip to main content

Gracefully terminating process: nginx

Comments

5 comments

  • cPRex Jurassic Moderator

    Hey there!  That seems correct to me - if cPanel doesn't detect one if its webservers, it takes over ports 80 and 443.  There isn't going to be a way around that, as we only recommend trying to configure cPanel & WHM or DNSOnly on a new system.

    0
  • Unnamed User

    Okay, so that's ridiculous..  In order to reduce costs, as well as energy consumption, we use many of our servers for multiple purposes.  Cpanel is basically behaving like malware at this point, and we just discovered that we can't even remove it?

    0
  • cPRex Jurassic Moderator

    The only way to fully remove cPanel is to reimage the server, yes - that has always been the case.  We also don't support converting existing machines to the DNSOnly system:

    https://support.cpanel.net/hc/en-us/articles/360063180033-Can-I-convert-a-cPanel-installation-to-DNS-Only

    0
  • Unnamed User

    We were not converting an existing (cPanel) system.  Only installing DNSOnly on an existing, up to date server that was primarily used for other purposes.  DNSOnly implies "dns only", so we're not entirely sure why it needs to "take over" ports 80, 443.

    0
  • cPRex Jurassic Moderator

    One of the requirements of cPanel has always been that is has to be installed on a clean server with no pre-existing software.

    0

Please sign in to leave a comment.