• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Resolved Unable regenerate config due to nginx attempting to bind to a non-existing IPv6

JoeShmoe

New Pleskian
I previously deteled the only IPv6 from my server, I don't intend to use it. However nginx still attempts to use it when regenerating apache/nginx configs for domains
( IPv6 replaced with x:x:x:x:: below)
Bash:
 httpdmng failed: [2020-07-30 16:14:21.070] ERR [util_exec]
      proc_close() failed ['/opt/psa/admin/bin/nginx-config' '-t']
      with exit code [1]
      [2020-07-30 16:14:21.286] ERR [util_exec] proc_close() failed
      ['/opt/psa/admin/bin/nginx-config' '-t'] with exit code [1]
      [2020-07-30 16:14:21.287] ERR [panel] Apache config
      (15961184600.91822500) generation failed: Template_Exception:
      nginx: [emerg] bind() to [x:x:x:x::]:443 failed (99:
      Cannot assign requested address)
      nginx: configuration file /etc/nginx/nginx.conf test failed

      file:
      /opt/psa/admin/plib/Template/Writer/Webserver/Abstract.php
      line: 75
      code: 0
      nginx: [emerg] bind() to [x:x:x:x::]:443 failed (99:
      Cannot assign requested address)
      nginx: configuration file /etc/nginx/nginx.conf test failed

The IP is no longer present anywhere in Plesk, How can I prevent nginx for trying to use it?
I'm on Plesk Obsidian 18.0.28 Update #3 and Ubuntu 18.04.4
 
This also prevents me from configuring new websites. Nginx keeps trying to use the non-existent IP.
sysctl -w net.ipv6.ip_nonlocal_bind=1 is a workaround, but I prefer to prevent nginx using that IP.
 
Last edited:
Back
Top