Ошибка 113 no route to host

Выводит ошибку в логе «Нет маршрута для размещения»

error.log:

2017/12/15 10:49:12 [error] 377#377: *6 connect() failed (113: No route to host) while connecting to upstream, client: 10.12.4.5, server: 10.12.4.245, request: "GET /favicon.ico HTTP/1.1", upstream: "http://10.12.4.245:80/favicon.ico", host: "10.12.4.242", referrer: "http://10.12.4.242/"

Помогите пожалуйста кто сможет, что я не так настроил?

nginx.conf:

upstream puma {
  server unix:///home/solovievga/phonebook-api/tmp/sockets/puma.sock;
}
server {
listen   80 default;
listen   [::]:80 default ipv6only=on;

server_name 10.12.4.245;
root /home/solovievga/phonebook-api;

location / {
root /home/solovievga/phonebook-api/phonebook-app/dist;
index index.html index.htm;
        try_files $uri @app;
        gzip_static on;
        expires max;
        proxy_read_timeout 150;
        add_header Cache-Control public;
  }


  try_files $uri/index.html $uri @puma;
  location @puma {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;
    proxy_redirect off;
    proxy_pass http://puma;
  }
   location @app {
     proxy_pass        http://10.12.4.245;
     proxy_set_header  X-Real-IP  $remote_addr;
     proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;
     proxy_set_header  X-Forwarded-Proto http;
     proxy_set_header  Host $http_host  ;
     proxy_redirect    off;
     proxy_next_upstream error timeout invalid_header http_502;
    }

  client_max_body_size 50M;
  keepalive_timeout 10;
}

Frustrated with Zabbix 113  no route to host error? We can help you fix it.

In general, Zabbix 113 no route to host error is mainly related to the firewall.

At Bobcares, we often get requests to fix Zabbix errors, as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix this Zabbix 113 no route to host error for our customers.

Why this Zabbix 113 no route to host error?

The Zabbix monitoring system is really helpful in monitoring the services. It alerts server administrators about server failures.

But we need to configure Zabbix and add servers to it.

However, often while adding servers, Zabbix 113 error occurs due to incorrect firewall settings. Or, it may even happen due to some bad routing/network configuration.

Today, we discuss in detail on this error and let’s see how our Support Engineers find a fix for this error.

How we fix this?

The fix for the Zabbix 113 error can vary based on the cause. Let’s now check them in detail.

Incorrect server key

Recently, one of our customers approached us saying that he was getting an error when he configured the Zabbix agent.

So, we checked in detail and did the following:

Firstly, we checked whether we could connect to the server via ping and it was a success. As we were able to ping, then we confirmed that there was no network error.

So, we did a deep search and found that the server’s active key was not set in agentd configuration file. The customer was using the Zabbix Agent(Active). And, we filled them with the IP address of the Zabbix server.

Further, our Engineers added the key for the customer and this fixed the problem.

Fixing firewall

In a similar scenario, a customer had set up 2 Linux systems in the VM, one as a Zabbix server and the other as a Zabbix client.

However, when checked we found that the icon was showing up as red in Zabbix. The monitoring of the client using the server was failing.

We checked the network connectivity using ping command and it was failing.

Our Support Engineers found that the server firewall was blocking the host. So we modified the firewall to allow connections from the host. Then we deleted the host and created a new one.

And this fixed the Zabbix 113 error.

[Need assistance with Zabbix error – We can help you fix it]

Conclusion

In short, this error occurs mainly due to firewalls and can be fixed by stopping or by adding a rule in iptables. Also, we saw how our Support Engineers fixed the Zabbix 113 no route to host error.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

I’ve got an Apache 2.0.52 server on CentOS 4 that front-ends a couple of App servers (mix of Jetty and Tomcat). Apache has a handful of virtual hosts configured like this:

<VirtualHost www1.example.com:443>
    ServerName www1.example.com
    DocumentRoot "/mnt/app_web/html"

    SSLEngine on
    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
    SSLCertificateFile      /etc/httpd/conf/ssl.crt/server.crt
    SSLCertificateChainFile /etc/httpd/conf/ssl.crt/chain.crt
    SSLCertificateKeyFile   /etc/httpd/conf/ssl.key/server.key
    SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0

    RewriteEngine on
    RewriteRule ^/app1/(.*)$ http://app1.example.com:8080/app1/$1 [P,L]
    RewriteRule ^/app2/(.*)$ http://app2.example.com:8080/app2/$1 [P,L]
</VirtualHost>

However, I’m getting the following errors in the logs intermittently:

[Fri Dec 04 07:19:41 2009] [error] (113)No route to host: proxy: HTTP: attempt to connect to 10.0.0.1:8080 (app1.example.com) failed

I initially tried turning off IPv6, and that seemed to largely cure it, but I still have sporadic bursts of these messages.

Additionally, we’re running memcache on same front-end and during the times when I’m getting those messages in Apache’s log, the following command doesn’t work:

echo stats | nc 127.0.0.1 11211

No messages are printed, but neither are the stats printed. I am completely lost as to how to proceed with troubleshooting this. =(

nginx.1 | 2019/10/30 20:43:01 [error] 707#707: *1077 connect() failed (113: No route to host) while connecting to upstream, client: MY.IP, server: sonarr.domain.tld, request: "GET /vendors~index.js?h=faRhAy83bMn0pnvHe55DnQ HTTP/2.0", upstream: "http://172.18.0.14:8989/vendors~index.js?h=faRhAy83bMn0pnvHe55DnQ", host: "sonarr.domain.tld", referrer: "https://sonarr.domain.tld/"

This morning, out of the blue, my sonarr instance started to act weirdly, with 502 errors every now and then, after a while it just stopped working. After checking nginx proxy, I’ve rebuild the Sonarr container multiple times and after checking that accessing IP:8989 was working fine, I went and checked nginx-proxy, and apparently that’s what’s broken.

Anything I should try? I’ve seem other similar issues and nothing worked, I already have a VIRTUAL_PORT and VIRTUAL_HOST on my container env’s.

All other containers are fine, radarr, plex, nginx website, everything is working.

Hope I’ve provided enough information!

Thanks!

Статьи

Возврат к списку

Did you know what is Battlenet Error 113 Chrome Windows PC problem is? If you don’t know this kind of error code problem and also have not found how to fix it, then you can check out this post to quickly conclude how to fix and solve this error problem.

This shows an error code message like,

This webpage is not available

The webpage might be temporarily down, or it may have moved permanently to a new web address.

Error 113 Code Unknown error

This error may occur during an attempt to connect the TCP socket. This error may also happen when you are trying to log into any website; it says an error like can’t log in before asking for an authenticator code. This error may also show when your system requests fail. Sometimes MAC users are also facing this type of Error 113 problem there. This error also shows an error like ‘Unable to validate your login credentials.’ This error indicates a connection problem. This error also indicates when a corrupted file is on the CD-ROM.

Causes of Battlenet Error 113 Chrome Windows Issue:

• Misconfiguration in Windows O.S. (Operating System)
• This webpage is not available
• Netflix issue
• The DNS server is not serving
• Unknown error
• No route to host error
• Firewall blocking connection
• Windows error code issue
• ISP (Internet Service Protocol) down
• Modem not connecting

So, here are some quick guides and effective solutions for fixing and solving this type of Battlenet Error 113 Chrome Windows PC Code problem from you completely.

How to Fix Battlenet Error 113 Chrome Windows Issue

1. Run your Windows PC in Safe Mode –

• Go to the start menu
• Click on the Shutdown option there
• Click on it & wait for it to Shutdown completely
• After that, Remove the battery & reinsert it
• Now, Click on the power button to restart it
• After that, a pop-up will open there
• Click on the ‘Safe Mode option to run in Safe mode
• That’s it, done

By running your PC in safe mode can quickly fix and solve this battlenet Error 113 code problem with you.

2. Check the Hard Disk Corruption for any Error Problems –

• Go to the start menu
• Search or go to the Command Prompt (Cmd) there
• Click on Cmd and opens it
• After that, Type the following command there
  “ chkdsk /f “
• After, press enter there to start it
• Wait for some time to check that if any error
• After completing, close the tab
• Restart your PC once
• That’s it, done

Checking any hard disk corruption & fixing it can quickly fix and solve this battle net Error 113 Code problem.

3. Run a Full Scan of your Windows PC for Malware/Viruses –

• Go to the start menu.
• Search or go to the “Microsoft Security Essentials” there
• Click on it and opens it there
• A Pop-up will open there
• Check the ‘Full‘ option there to scan thoroughly
• After, click on the ‘Scan Now‘ option to scan carefully
• After scanning, close the tab
• That’s it, done

Running a full scan of your PC can completely eliminate this battlenet Error 113 problem from your PC.

4. Create a System Restore Point –

• Go to the start menu
• Search or go to the ‘System Restore.’
• Clicks on it and open it there
• After that, tick on the “Recommended settings” or ‘Select a restore point‘ there.
• After selecting, click on the Next option there
• Now, follow the wizard
• After completing, close the tab
• That’s it, done

So using the above tips on your PC or Device will help you to get back from this Error 113 Wow problem.

” OR “

• Go to the start menu
• Search or go to the ‘System Properties.’
• Click on it and opens it.
• After that, go to the “System Protection” option there
• Now, click on the “System Restore” option there
• & Create a Restore point there
• After completing, close the tab
• That’s it, done

Running a system restore and creating a new restore point by any of these two methods can solve this Error 113 no route to host problem from your PC altogether.

5. Update your Windows Drivers –

• Go to the start menu
• Search or go to the Control Panel
• Click on it and opens it there
• After that, scroll down and go to the “Windows Update” section there
• Click on it & Check if any newly latest driver update is available or not
• If any, Update it fast
• Or, you can set it as ‘automatically update.’
• For that, go to the left side
• & click on the “Changes Settings” option there
• After opening, click on the drop-down menu there
• Select the “Install Updates Automatically” option there
• & click on the OK button to save this configuration
• After completing, close the tab
• That’s it, done

So by trying this guide, you will learn about the Error 113 Chrome issue.

” OR “

• Go to the start menu
• Search or go to the Control Panel or directly go to Device Manager
• Click on it and opens it there
• After going to the Device Manager there,
• check if any driver has an error sign there
• If any, then right-click on it
• & Click on the “Update driver software” there
• Wait for some minutes to update it
• After updating, close the tab
• That’s it, done

Upgrading your driver by any of these two methods can quickly fix and solve your PC’s Windows Error 113 problem.

6. Run an sfc /scannow Command in CMD (Command Prompt) –

• Go to the start menu
• Search or go to the Command Prompt
• Click on it and opens it there
• A Pop-up will open there
• Type “sfc/scannow” command there
• After Press, enter to start it
• Now, wait for some time to scan
• After completing, close the tab
• That’s it, done

Running an sfc scan can completely eliminate this Error 113 problem from your PC.

7. Uninstall and Reinstall the Graphics Driver –

• Go to the start menu
• Search or go to the Control Panel
• Clicks on it and open it there
• Scroll down & go to the “Programs and Features” option
• Clicks and after opening,
• Search for and go to the ‘Graphics Driver‘ there
• Right-click on it there &
• Click on the “Uninstall” option there to uninstall it
• After Uninstalling, close the tab
• That’s it, done

Uninstalling and reinstalling your graphics driver can quickly fix and solve your PC’s Error 113 code problem.

Conclusion:

These are some top best methods and solution guides for an easy fix and solve this Battlenet Error 113 Chrome Windows PC problem for you permanently. I hope you surely get rid of this Error 113 problem.

If you are facing this Battlenet Error 113 Chrome Windows PC problem or any error problem while fixing it, then comment down the problem below so that we can fix and solve it too by our quickly top best guides and the solution methods.