• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

ERROR Ip Nginx after UPDATE

Manuel_Caramia

Regular Pleskian
Hi,
how is it possible that after an update my main site is down? This site: www.orderhosting.it has plesk Panel and I have 20 sites. They work perfectly but my main site is off. I think there is an error in the configuration because:
[root@orderhosting ~]# grep -r 199.99.36.73 /etc/nginx/
[root@orderhosting ~]#
This is strange.
Error log does not report any errors, only this:
[warn] RSA server certificate CommonName (CN) `Parallels Panel' does NOT match server name!?
Anyone can help me?
Thank's
 
Hi Manuel_Caramia,

this is now your THIRD thread to the very same issue. Please stick to your other threads to get some help and try to follow the suggestions and as well the demands which the helpfull people need to suggest solutions.
 
Hi Manuel_Caramia,

this is now your THIRD thread to the very same issue. Please stick to your other threads to get some help and try to follow the suggestions and as well the demands which the helpfull people need to suggest solutions.
The problem is not the same! At the beginning the issue was due to CloudLinux but now it is due to NGINX. In other post I have written but nobody answered.
I have opened this thread beacause this is most specific.
Can you help me please?
Thank you
 
again... please stick to ONE thread, because the mentioned issue was already stated there:

Hi Manuel_Caramia,

if you think, that your issues can be solved without the working services, which are currently blocked for your hosting as stated in the error message from your post

... I must disappoint you. At the moment, as stated before, ALL PORTS ARE CLOSED on your IP and you can check that with "nmap" and "netstat".

netstat -tuplen

nmap -v -p 80 127.0.0.1 ( to scan port 80, choose other ports like 443,8080,8443 as well... or YOUR CHOICE OF the port usage 7080 )
or/and
nmap -v -p 80 XXX.XXX.XXX.XXX ( ( to scan port 80, choose other ports like 443,8080,8443 as well... or YOUR CHOICE OF the port usage 7080 - please replace XXX.XXX.XXX.XXX with your IP for the domain )

... or choose a site like: http://www.dnstools.ch/port-scanner.html for a scan outside of your server environment.​

... again as well... we can only GUESS your configuration files, which might be incorrect and cause issues.... please include them for investigations, as mentioned not only by me, but as well by other helpfull people.
 
there's no need to shout or write large letters. I understand.

These are the outputs. As you can see the first (80 port) is closed, the second opened.
Thank you.

Code:
[root@orderhosting ~]# nmap -v -p 80 127.0.0.1

Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-18 20:31 CET
Initiating SYN Stealth Scan at 20:31
Scanning localhost.localdomain (127.0.0.1) [1 port]
Completed SYN Stealth Scan at 20:31, 0.01s elapsed (1 total ports)
Nmap scan report for localhost.localdomain (127.0.0.1)
Host is up (0.000040s latency).
PORT   STATE  SERVICE
80/tcp closed http

Read data files from: /usr/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds
           Raw packets sent: 1 (44B) | Rcvd: 2 (84B)
Code:
[root@orderhosting ~]# nmap -v -p 80 192.99.36.73

Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-18 20:32 CET
Initiating SYN Stealth Scan at 20:32
Scanning orderhosting.it (192.99.36.73) [1 port]
Discovered open port 80/tcp on 192.99.36.73
Completed SYN Stealth Scan at 20:32, 0.01s elapsed (1 total ports)
Nmap scan report for orderhosting.it (192.99.36.73)
Host is up (0.000041s latency).
PORT   STATE SERVICE
80/tcp open  http

Read data files from: /usr/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds
           Raw packets sent: 1 (44B) | Rcvd: 2 (88B)
 
Hello Manuel,
I have already responded to your ticket ..Please see below:

http://eu.amnotseen.com/browse.php?u=Oi8vd3d3Lm9yZGVyaG9zdGluZy5pdC8=&b=13

Code:
Thanks for your ticket. I'm more than happy to help you with that.

Apparently the problem was with the DNS records.
For starters, your DNS records had the IP address 199.99.36.73 which as I see, is not your server's IP.

I have changed that IP to the actual servers IP address (192.99.36.73) at the NS sv01.orderhosting.it since that resolves to your dedicated server.
Now, you will need also to change that IP address at the NS sdns1.ovh.ca as I guess you have an interface to manage the respective DNS records.

After you have changed the IP address, please let us know so we can look at it ...(but am hoping this will resolve the problem at hand)

I hope I have been able to answer your question. It was a pleasure serving you today.
 
Back
Top