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

Resolved Nginx can't bind to 192.168.1.1:80....

apaunovski

Basic Pleskian
So, my Plesk server has 2 IP's...

One external and shared - 95.xxxxxxxxxx
One internal for communication with the backup server - 192.168.1.1

Today I tried to change NGINX configuration for a website and I get an error - "Nginx failed to bind to IP 192.168.1.1:80"...

Why is Nginx trying to bind to that internal IP at all?

I use it to connect my Plesk server to my backup server... It's not for the world and website serving.

How do I solve that? What do I do?
 
Here is the exact error message


Invalid nginx configuration: nginx: [emerg] bind() to 192.168.1.1:80 failed (99: Cannot assign requested address) nginx: configuration file /etc/nginx/nginx.conf test failedUnable to use the current nginx configuration file and to rollback to the previous version of the file because they both contain invalid configuration.
 
The issue has been resolved, but I have to make a few contributions. I tried it too, but I got an error on some pages, especially the 192.168.1.1 page was quite challenging for me. The interface on my modem is quite troublesome, so I found this page by following topics like you. 192.168.1.1 is difficult for Ngix but I was able to solve this by assigning a NAT page. If you take a careful look at the admin login page, you will be able to recognize all I have said very easily. thanks for your support
 
Back
Top