Tcp connect error 111

error trying to connect: tcp connect error: Connection refused (os error 111) [Bug] #51

Describe the bug
Container stops with exit code 1, gives this log:

INFO Listening on port 8080

error: Uncaught (in promise) TypeError: error sending request for url (https://:32400/library/sections?X-Plex-Token=): error trying to connect: tcp connect error: Connection refused (os error 111)

To Reproduce
Steps to reproduce the behavior:

1. deploy container using docker-compose
2. view logs

Expected behavior
The container starts

Server:

• OS: Open-Media-Vault 5.6.0
• Docker: OMV-extras

The text was updated successfully, but these errors were encountered:

This looks like a networking issue with your server. The error means that the Plex server isn’t accessible from MovieMatch.
Can you try finding an IP address route to the Plex server and using that instead? e.g. http://192.168.1.10:32400

Is Plex accessible from other containers using the same name?

Closing due to inactivity. Comment back with more info to re-open

I had tried that before, but when using the internal IP, I get this error:
error trying to connect: invalid dnsname

When using the external IP with the internal port, I get the same TCP error, when using the external port Plex uses I get the DNS error again

At the moment I don’t have any other containers that need to reach plex

If you can SSH into the server, you could try following the debugging steps I’ve posted in #52?

I just tried using the external port with the domain name and got this error:
error trying to connect: invalid certificate: CertNotValidForName

I’ll have a look at the instructions you linked

In the instructions you want me to exec into the container, the thing is that I’ve never seen the container running, it’s always on stopped and when looking in the lights I get the aforementioned errors. I’m using portainer for the bulk of it btw

error trying to connect: invalid certificate: CertNotValidForName

Are you using a valid TLS certificate for your Plex domain?

In the instructions you want me to exec into the container, the thing is that I’ve never seen the container running, it’s always on stopped and when looking in the lights I get the aforementioned errors. I’m using portainer for the bulk of it btw

Can you run docker run —rm -u 0 -it —entrypoint=»/bin/bash» lukechannings/moviematch and follow the instructions for installing curl from #52?

Are you using a valid TLS certificate for your Plex domain?

I have a self signed SSL certificate if thats good enough

Can you run docker run —rm -u 0 -it —entrypoint=»/bin/bash» lukechannings/moviematch and follow the instructions for installing curl from #52?

I’ll try it now but bear with me, I’m on mobile :p

I managed to get into the Interactive shell and executed the command as you specified, here’s the output, or atleas the last bit of it. I apologise for the medium, as I said I’m on mobile

Источник

TCP/IP error 111 (Connection refused).?

I have configured replication using Golden gate. After starting extract .. i am getting following follwing error.

How to resolve this error. please help me

GGS WARNING 150 Oracle GoldenGate Capture for Oracle, ext1.prm: TCP/IP error 111 (Connection refused)

Answers

I have configured replication using Golden gate. After starting extract .. i am getting following follwing error.
How to resolve this error. please help me
Error:

GGS WARNING 150 Oracle GoldenGate Capture for Oracle, ext1.prm: TCP/IP error 111 (Connection refused)

The problem is, most likely, that you have your extract «ext1» writing to a remote trail (RmtHost , mgrPort 7801), and the remote manager is either not running, or is not running on the correct/expected port (in this example, 7801). Also be sure «ext1.prm» uses the correct syntax for specifying the rmthost: it’s «mgrport», not just «port».

Good luck,
-Michael

Now i am getting different error

GGSCI (test1.domain.com) 28> view report ext1

***********************************************************************
Oracle GoldenGate Capture for Oracle
Version 10.4.0.19 Build 002
Linux, x86, 32bit (optimized), Oracle 10 on Sep 18 2009 00:01:59

Copyright (C) 1995, 2009, Oracle and/or its affiliates. All rights reserved.

Operating System Version:
Linux
Version #1 Wed Jan 5 19:22:18 EST 2005, Release 2.6.9-5.EL
Node: test1.domain.com
Machine: i686
soft limit hard limit
Address Space Size : unlimited unlimited
Heap Size : unlimited unlimited
File Size : unlimited unlimited
CPU Time : unlimited unlimited

Process id: 3601

CACHEMGR virtual memory values (may have been adjusted)
CACHEBUFFERSIZE: 64K
CACHESIZE: 2G
CACHEBUFFERSIZE (soft max): 4M
CACHEPAGEOUTSIZE (normal): 4M
PROCESS VM AVAIL FROM OS (min): 2.92G
CACHESIZEMAX (strict force to disk): 2.68G

Database Version:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 — Prod
PL/SQL Release 10.2.0.5.0 — Production
CORE 10.2.0.5.0 Production
TNS for Linux: Version 10.2.0.5.0 — Production
NLSRTL Version 10.2.0.5.0 — Production

Database Language and Character Set:
NLS_LANG = «AMERICAN_AMERICA.US7ASCII»
NLS_LANGUAGE = «AMERICAN»
NLS_TERRITORY = «AMERICA»
NLS_CHARACTERSET = «US7ASCII»

2011-07-21 08:02:08 GGS INFO 406 Socket buffer size set to 27985 (flush size 27985).

2011-07-21 08:02:18 GGS INFO 112 No recovery is required for target file /u01/gg/dirdat/lt000000, at RBA 0 (file not opened).

2011-07-21 08:02:18 GGS INFO Z0-05M Output file /u01/gg/dirdat/lt is using format RELEASE 10.4.

Source Context :
SourceModule : [er.extrout]
SourceID : [$Id: //depot/releases/OpenSys/v10.4.0/src/app/er/extrout.c#4 $]
SourceFunction : [complete_tcp_msg]
SourceLine : [1342]
ThreadBacktrace : [8] elements
: [u01/gg/extract(_ZN15CMessageContext16AddThreadContextEv+0x26) [0x825bb56]]
: [u01/gg/extract(_ZN15CMessageFactory13CreateMessageEP14CSourceContextjz+0x533) [0x824fc43]]
: [u01/gg/extract(_Z16complete_tcp_msgP11extract_def+0x7d7) [0x80c3347]]
: [u01/gg/extract [0x80ce7b1]]
: [u01/gg/extract(_Z19open_targ_ext_filess+0xa5) [0x80c2525]]
: [u01/gg/extract(main+0x6d0) [0x80ff900]]
: [lib/tls/libc.so.6(__libc_start_main+0xe3) [0xc0ee33]]
: [u01/gg/extract [0x809b5e1]]

*2011-07-21 08:02:18 GGS ERROR 112 There is a problem in network communication, a remote file problem, encryption keys for target and source do not ma*
tch (if using ENCRYPT) or an unknown error. (Remote file used is /u01/gg/dirdat/lt000000, reply received is Could not create /u01/gg/dirdat/lt000000).

*2011-07-21 08:02:18 GGS ERROR 190 PROCESS ABENDING.*

Источник

Fix & Solve Error 111 Code Problem Issue (100% Working)

If you are getting Error 111 Windows PC on your PC and finding solutions for this error code problem but couldn’t find any right solution for this error, then check out the below solutions so that you will get rid of this error problem from your PC completely.

This shows an error code message like;

An error occurred while attempting to access the file store.

Error 111

This Error occurs when you are accessing an SSL page via a proxy. It probably means that our MySQL server only listens on the local host. This error includes PC crashes, freezes, and possible virus infection. This error is also due to your antivirus. This bug check error occurs when there is an error in the system management interrupt (SMI). This Error Code 111 problem is usually caused by a prior assembler, compiler, or fatal linker error that can cause an incompatible object file to be generated.

Causes of Error 111 Windows PC Code Issue :

• MySQL server error
• linux error issue
• Connection refused error
• Insufficient memory
• Unknown error
• Linker Fatal error
• Virus or Malware infection
• Windows PC

So, here are some guides and the best methods for quickly fixing and solving this type of Error 111 Windows PC Code problem from your PC permanently.

How to Fix Error 111 Windows PC Code Problem Issue

1. Turn OFF or Disable Windows Firewall Settings on your PC –

• Go to the Start Menu
• Go to the Control Panel
• Click on Windows Firewall there
• Click on the ‘Turn Windows Firewall on or off feature there
• Tick on “Turn off Windows Firewall ( not recommended )” there
• Now, Click on the ‘OK‘ button there
• That’s it, Done

By turning off or disabling the windows firewall settings, it can fix this MYSQL Error 111 problem.

2. Change the LAN ( Local Area Network ) Settings –

Check your proxy settings or contact your network administrator to ensure the proxy server is working. If you don’t believe you should use a proxy server, then,

• Go to the Google Chrome menu
• Click on the Settings tab there
• Click on the ‘Show Advanced Settings‘ option there
• Click on the “Change Proxy Settings” tab there
• Now, go to the “LAN settings” and deselect the
  ” Use a Proxy server for your LAN “
• After deselecting, close the tab there
• That’s it, done

By checking your proxy settings, you can easily get rid out of this Multicraft Error 111 problem from your browser.

3. Reset TCP/IP ( Transmission Control Protocol / Internet Protocol ) on your PC –

• Go to the start menu
• Search or type Command Prompt there
• Opens it & type
  ” netsh int tcp reset resettcpip.txt “
• Press Enter there
• That’s it, done

Resetting TCP/IP on your computer or laptop will surely solve this connection failure with the Error 111 Webex problem.

4. Run a full Malware/Virus Scan of your Windows PC –

• Go to the start menu.
• Search or go to the ‘Microsoft Security Essentials.’
• Click on it and opens it.
• Tick the ‘Full‘ option to run a full scan of your PC
• Now, click on the “Scan Now” option there to scan your PC
• Now, wait for some minutes to scan it
• After completing, close the tab
• That’s it, done

By scanning and running your PC for malware/viruses, Microsoft Security Essentials can easily fix and solve this Showtime Error code 111 problem.

Conclusion:

These are some of the best tricky methods and the solutions to eliminate this Error 111 Windows PC Code problem from your PC completely. Hope these methods will help you to get back from this Error Code 111 problem.

If you are facing this Error 111 Windows PC Code problem or any error problem while fixing it, then comment down the problem below so that we can fix it too with our top best tricky ways, methods, and solutions.

Источник

connect() failed (111: Connection refused) while connecting to upstream

I’m experiencing 502 Gateway errors when accessing a PHP file in a directory ( http://example.com/dev/index.php ). The logs simply says this:

I’ve never experienced this before. What is the solution for this type of 502 Gateway error?

This is the nginx.conf :

8 Answers 8

It sounds like you haven’t started and configured the backend for Nginx. Start php-fpm and add the following to nginx.conf , in the http context:

This answer is only for those who get an error like this:

connect() failed (111: Connection refused) while connecting to upstream, client . fastcgi://[::1]:9000

Rewrite your nginx config to use ip, not dns. For instance, 127.0.0.1 instead of localhost , or remove the ipv6 alias from /etc/hosts.

Got errors like this too. Problem was my abstract backend referencing two servers. php-fpm was only listing to socket.

Had the same problem with proxied requests to a Node server listening on port 5000. Requests would result with 200 OK but sometime 502 Bad Gateway randomly. NGINX showed the error:

1. Set node HTTP server to listen strictly for ipv4 by including localhost as host: server.listen(5000, ‘localhost’);
2. Removed any ipv6 listen directives ( listen [::]:80; or listen [::]:443 ssl default_server; ).
3. Changed location block proxy_pass to use IPs: proxy_pass http://127.0.0.1:5000 (not proxy_pass http://localhost:5000 ).

Hope this helps someone.

In my case the error was a bad location for the error_log file for php5.6-fpm service and thus the php-fpm service was failing to start and nginx was not able to connect to it. You can find it in /etc/php/5.6/fpm/php.ini (you can replace 5.6 with the version you are running).

Same problem has occured for me and finally I found firewalld was blocking required ports after installation and I was missing to open ports in firewall (port 9000 in your logs).

Just in case somebody is deperately trying to fix their problem just to realize there is nothing wrong with their reverse proxy setup:

In my case, the error persisted even after I’ve removed all location directives but a single one that only provides static content.

The error message was caused because Nginx wasn’t able to log it’s log to the syslog server:

Summary:

If you are using a syslog log server, make sure it is available. To test whether the error originates from the logging setup, comment out all logging configs so that Nginx falls back to the native logging scheme.

I hope this saves some people time debugging a fully valid reverse proxy config, just to fid the error somewhere else 😀

Источник

1. Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python
2. How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python
3. Conclusion

This error indicates that the client cannot connect to the port on the server script’s system. Since you can ping the server, it should not be the case.

This might be caused by many reasons, such as improper routing to the destination. The second possibility is that you have a firewall between your client and server, which may be either on the server or the client.

There shouldn’t be any routers or firewalls that may stop the communication since, based on your network addresses, both the server and the client should be on the same Local Area Network.

Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python

This error arises when the client cannot access the server because of an invalid IP or port or if the address is not unique and used by another server.

The connection refused error also arises when the server is not running, so the client cannot access the server as the server should accept the connection first.

Code example:

# server code
import socket

s = socket.socket()
host = socket.gethostname()
port = 1717
s.bind((host, port))

s.listen(5)
while True:
    c,addr = s.accept()
    print("Got connection ", addr)
    c.send("Meeting is at 10am")
    c.close()

# client code
import socket

s = socket.socket()
host = '192.168.1.2'
port = 1717

s.connect((host,port))
print(s.recv(1024))
s.close

Output:

socket.error: [Errno 111] Connection refused

How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python

Try to keep the receiving socket as accessible as possible. Perhaps accessibility would only take place on one interface, which would not impact the Local Area Network.

On the other hand, one case can be that it exclusively listens to the address 127.0.0.1, making connections from other hosts impossible.

Code example:

import socket

s = socket.socket()
host = socket.gethostname()
port = 1717
s.bind(('', port))

s.listen(5)
while True:
    c,addr = s.accept()
    print("Got connection ", addr)
    c.send("The Meeting is at 10 am")
    c.close()

import socket

s = socket.socket()
host = socket.gethostname()
port = 1717
s.bind(('', port))

s.connect((host, port))
print(s.recv(1024))
s.close()

Output:

Got connection('192.168.1.2')
The meeting is at 10 am

When you run the command python server.py, you will receive the message Got connection. At the same time when you run the command python client.py, you will receive a message from the server.

The DNS resolution can be the other reason behind this problem. Since the socket.gethostname() returns the hostname, an error will be returned if the operating system cannot translate it to a local address.

The Linux operating system can edit the host file by adding one line.

host = socket.gethostname()
port = 1717
s.bind((host,port))

Use gethostbyname

host = socket.gethostbyname("192.168.1.2")
s.bind((host, port))

Thus, you must use the identical technique on the client and server sides to access the host. For instance, you would apply the procedure described above in a client’s case.

You can also access through local hostname hostnamehost = socket.gethostname() or specific name for local host host = socket.gethostbyname("localhost").

host = socket.gethostname()
s.connect((host, port))

host = socket.gethostbyname("localhost")
s.connect((host, port))

Conclusion

ConnectionRefusedError in Python arises when the client cannot connect to the server. Several reasons include the client not knowing the IP or port address and the server not running when the client wants to connect.

There are several methods mentioned above to resolve this connection issue.