Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Articles in this section

See more

nginx fails to start: nginx: [emerg] bind() to 203.0.113.2:443 failed (98: Address already in use)

Avatar
Leonid Gukhman
Updated
Follow
Plesk for Linux kb: technical ABT: Group B

Applicable to:

  • Plesk Onyx for Linux
  • Plesk for Linux

Symptoms

  • nginx fails to start:

    # service nginx starts:
    nginx: [emerg] bind() to 203.0.113.2:443 failed (98: Address already in use)

  • There are running nginx processes on the server:

    # ps aux | grep nginx
    root 6927 0.0 0.1 38604 4752 ? Ss 06:27 0:00 nginx: master process /usr/sbin/nginx

Cause

nginx processes are stuck.

Resolution

  1. Login server via SSH.

  2. Find the stuck nginx processes:

    # # ps aux | grep nginx
    root 6927 0.0 0.1 38604 4752 ? Ss 06:27 0:00 nginx: master process /usr/sbin/nginx

  3. Kill the stuck processes using the ID(s) taken from the output of the previous command:

    # kill -9 6927

  4. Restart nginx:

    # service nginx restart

Comments

0 comments

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles