• 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!
  • 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.

Issue NGINX dont work since last update from 2017-10-31

Haecki

New Pleskian
Since the update I have the problem that nginx no longer processes my ipv6 addresses.

Code:
[root@server network-scripts]# plesk sbin nginxmng -e
[2017-11-01 03:17:23] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx-config' '-t'] with exit code [1]
[2017-11-01 03:17:39] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx-config' '-t'] with exit code [1]
[2017-11-01 03:17:39] ERR [panel] Apache config (15095026210.03421100) generation failed: Template_Exception: nginx: [emerg] bind() to [ipv6ip]:443 failed (99: Cannot assign requested address)
nginx: configuration file /etc/nginx/nginx.conf test failed

file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php
line: 75
code: 0
nginx: [emerg] bind() to [ipv6ip]:443 failed (99: Cannot assign requested address)
nginx: configuration file /etc/nginx/nginx.conf test failed
 
Do you have this IPv6 address listed in the output of command:

# plesk bin ipmanage -l

If not - Sync IP addresses between Plesk and OS. For that go to Tools & Settings > IP Addresses > Reread IP
 
Tools & Settings > IP Addresses > Reread IP --> will not work i wait 15 minutes than 504 timeout

plesk bin ipmanage --reread will also not work

i cant also set manuell in plesk onyx !!!
 
Code:
ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:xx:xx:xx:23:92
          inet addr:82.xxx.xxx.108  Bcast:82.xxx.xxx.108  Mask:255.255.255.255
          inet6 addr: 20xx:xxx:xxx:xxx:fbd0:98ca:e283:a216/64 Scope:Global
          inet6 addr: 20xx:xxx:xxx:xxx::8b84/64 Scope:Global
          inet6 addr: 20xx:xxx:xxx:xxx:9e88:9c88:7507:2d31:601a/64 Scope:Global
          inet6 addr: 20xx:xxx:xxx:xxx:4069:1f6e:ccae:a21/64 Scope:Global
          inet6 addr: fe80::219:99ff:fea3:2392/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:43320 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50771 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8464811 (8.0 MiB)  TX bytes:32279890 (30.7 MiB)
          Interrupt:18

all my IPV6 Addresses, an ping works to the machine to this ip's
 
Do you have all these IPv6 addresses listed in the output of command:

# plesk bin ipmanage -l

?

Do you have any error messages in Plesk panel.log after Tools & Settings > IP Addresses > Reread IP ?
 
no, the commandline tool
Code:
plesk bin ipmanage -l
State Type IP                                  Clients Hosting PublicIP
0     S    eth0:82.xxx.xxx.108/255.255.255.255 0       79      82.xxx.xxx.108
0     S    eth0:82.xxx.xxx.70/255.255.255.255  0       1       82.xxx.xxx.70
0     S    eth0:82.xxx.xxx.101/255.255.255.255 0       1       82.xxx.xxx.101

The panel.log is clean, no entry's
 
OK, I enabled debug and executed the command
unfortunately I have to stop after 5 minutes with ctrl + c, but nothing is found in the /var/log/plesk/panel.log.
 
I can only recommend creating a request to support team to do the in-depth investigation to find the reason and to fix it. Please create a ticket to support at Plesk Help Center
 
It is possible that the IP configuration is all good, but binding to port 443 can fail, too, if the port is in use by another service, for example if httpd/apache or an additional web server on the system is using it. Check it with
# netstat -plnt | grep ':443'
 
Back
Top