Unexpectedly closed the connection err connection closed

Author: s | 2025-04-24

127.0.0.1 unexpectedly closed the connection try check the connections err connection closed

What causes unexpectedly closed the connection ERR

Web-udpweb-udp is a library used to establish unreliable data channels in Node/browser environments. The key goal of this project to provide a small, stable API that anyone can use to work with real-time data on the Web.The library is currently implemented as an abstraction on top of unordered and unreliable RTCDataChannels. Since WebRTC is a dependency, a WebSocket based signaling server is included with the package to facilitate connections between clients. Client/server connections are available with the help of the wrtc package.API.subscribe(subscriber: T => any)Signal.unsubscribe(subscriber: T => any)Client(options?: { url?: string })Client.connect(to?: string = "__MASTER__", options?: { binaryType?: "arraybuffer" | "blob", maxRetransmits?: number, maxPacketLifeTime?: number, metadata?: any, UNSAFE_ordered?: boolean}): PromiseClient.route(): PromiseClient.connections: SignalConnection.send(message: any): voidConnection.close(): voidConnection.closed: SignalConnection.errors: SignalConnection.messages: SignalConnection.metadata: any// NodeServer({ server: http.Server, keepAlivePeriod?: number = 30000 })Server.client(): ClientServer.connections: Signal">SignalT>.subscribe(subscriber: T => any)SignalT>.unsubscribe(subscriber: T => any)Client(options?: { url?: string })Client.connect(to?: string = "__MASTER__", options?: { binaryType?: "arraybuffer" | "blob", maxRetransmits?: number, maxPacketLifeTime?: number, metadata?: any, UNSAFE_ordered?: boolean}): PromiseConnection>Client.route(): Promisestring>Client.connections: SignalConnection>Connection.send(message: any): voidConnection.close(): voidConnection.closed: SignalConnection.errors: Signal{ err: string }>Connection.messages: Signalany>Connection.metadata: any// NodeServer({ server: http.Server, keepAlivePeriod?: number = 30000 })Server.client(): ClientServer.connections: SignalConnection>Installationnpm i @web-udp/clientnpm i @web-udp/serverExamplesClient/ServerBelow is a simple example of a ping server:// client.jsimport { Client } from "@web-udp/client"async function main() { const udp = new Client() const connection = await udp.connect() connection.send("ping") connection.messages.subscribe(console.log)} { connection.messages.subscribe(message => { if (message === "ping") { connection.send("pong") } }) connection.closed.subscribe(() => console.log("A connection closed.")) connection.errors.subscribe(err => console.log(err))})server.listen(8000)">// server.jsconst server = require("http").createServer()const { Server } = require("@web-udp/server")const udp = new Server({ server })udp.connections.subscribe(connection => { connection.messages.subscribe(message => { if (message === "ping") { connection.send("pong") } }) connection.closed.subscribe(() => console.log("A connection closed.")) connection.errors.subscribe(err => console.log(err))})server.listen(8000)MetadataThe metadata option in Client.connect is used to send arbitrary handshake data immediately after establishing a connection. When a new connection is established, the remote client can access this data on the metadata property of the connection object without having to subscribe to the remote client's messages. Handshake metadata is transmitted over a secure RTCDataChannel, making it a good candidate for sensitive data like passwords.In the below example, a server handles authentication before subscribing to the client's messages:// client.jsconst connection = await udp.connect({ metadata: { credentials: { username: "foo", password: "bar", }, },}) { let user try { user = await fakeAuth.login(connection.metadata.credentials) } catch (err) { // Authentication failed, close connection immediately. connection.send(fakeProtocol.loginFailure()) connection.close() return } // The user authenticated successfully. connection.send(fakeProtocol.loginSuccess(user)) connection.messages.subscribe(...)})">// server.jsudp.connections.subscribe(connection => { let user try { user = await fakeAuth.login(connection.metadata.credentials) } catch (err) { // Authentication failed, close connection immediately. connection.send(fakeProtocol.loginFailure()) connection.close() return } // The user authenticated successfully. connection.send(fakeProtocol.loginSuccess(user)) connection.messages.subscribe(...)})P2Pweb-udp also supports peer-to-peer communication. The below example demonstrates two clients connected in the same browser tab:">script src="/page/node_modules/@web-udp/client/dist/index.js">script>script src="client.js">script> connection.messages.subscribe(console.log), ) connection.send("HELLO")}">// client.jsasync function main() { const left =

Unexpectedly closed Connection - WordPress.org

Enables or disables TCP sequence number randomization. See the “TCP Sequence Randomization” section section for more information.You can enter this command all on one line (in any order), or you can enter each attribute as a separate command. The ASA combines the command into one line in the running configuration.Note For management traffic, you can only set the conn-max and embryonic-conn-max keywords.set connection timeout {[embryonic hh:mm:ss] {idle hh:mm:ss [reset]] [half-closed hh:mm:ss] [dcd hh:mm:ss [max_retries]]}ciscoasa(config-pmap-c)# set connection timeout idle 2:0:0 embryonic 0:40:0 half-closed 0:20:0 dcdSets connection timeouts. For global timeouts, see the timout command in the command reference.The embryonic hh:mm:ss keyword sets the timeout period until a TCP embryonic (half-open) connection is closed, between 0:0:5 and 1193:00:00. The default is 0:0:30. You can also set this value to 0, which means the connection never times out.The idle hh:mm:ss keyword sets the idle timeout period after which an established connection of any protocol closes, between 0:0:1 and 1193:0:0. The default is 1:0:0. You can also set this value to 0, which means the connection never times out. For TCP traffic, the reset keyword sends a reset to TCP endpoints when the connection times out.The half-closed hh:mm:ss keyword sets the idle timeout period until a half-closed connection is closed, between 0:5:0 (for 9.1(1) and earlier) or 0:0:30 (for 9.1(2) and later) and 1193:0:0. The default is 0:10:0. Half-closed connections are not affected by DCD. Also, the ASA does not send a reset when taking down half-closed connections.The dcd keyword enables DCD. DCD detects

answers.microsoft.com unexpectedly closed the connection

Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Users cannot connect to POP3 or IMAP4 Article01/24/2024 Applies to: Exchange Server 2016 Enterprise Edition, Exchange Server 2016 Standard Edition, Exchange Server 2013 Enterprise, Exchange Server 2013 Standard Edition In this article -->Original KB number: 3025138Symptom 1Users who have a mailbox on Exchange Server 2016 or Exchange Server 2013 may find that their connections to POP3 or IMAP4 stop working. Additionally, they may receive the following error message:Microsoft.Exchange.Monitoring.ProtocolException: Authentication failed.The connection is being closed. Unable to read data from the transport connection: Anexisting connection was forcibly closed by the remote host.Server response while makingconnection:[]. ---> System.IO.IOException: Unable to read data from the transportconnection: An existing connection was forcibly closed by the remote host. --->System.Net.Sockets.SocketException: An existing connection was forcibly closed by theremote hostThe related service are started, no error/warning events in system orapplication log.Symptom 2Users can telnet to a POP3 or IMAP port by using the server FQDN. However, they don't see the banner. Instead, they see only a blank screen.CauseThis issue occurs because the PopProxy and ImapProxy components are in inactive state.You can use the Get-ServerComponentState command to check on the status of components.ResolutionTo resolve this issue, make the PopProxy and ImapProxy components active. To do this, follow these steps:Use the following command to determine which requester made PopProxy inactive:Get-ServerComponentState -Identity ServerName> -Component PopProxy).LocalStatesIn the following example, HealthAPI is displayed as the requester. 127.0.0.1 unexpectedly closed the connection try check the connections err connection closed

ERR_CONNECTION_CLOSED unexpectedly closed the connection

Size greater than 2048 bitsBugfix : fixed a potential issue with some antivirus programs when running CMD or POWERSHELL session within MobaXterm terminalBugfix : fixed a bug with RDP sessions, when “HighDPI adaptation” mode and SSH gateway options were setBugfix : fixed a status line length bug with Byobu on Ubuntu 18.04Bugfix : removed the limit in paste buffer, huge paste operations are now performed by chunks to prevent pipes overflowsBugfix : fixed a potential issue with window closed unexpectedly during Browser sessionsBugfix : fixed tunnels auto-reconnection feature which failed after network connection cutBugfix : fixed crash issues with SSH tunnels and gateways, especially after waking up Windows from sleep/hibernate modeBugfix : fixed a connection issue with some Huawei routers which require RSA hostkey first in hostkeys listVersion 12.1 (2019-08-05)Bugfix : corrected SSH connection failures caused by hardware accelerated encryptionBugfix : in some specific cases, local terminal output was garbled after a commandline SSH connection and a network error during SSH communicationBugfix : fixed “ldd” command which was missing some DLLs in its listingBugfix : fixed an issue in Windows colors selection dialog resulting in black color being applied in case of dialog failureBugfix : fixed an issue with the “cmd” command when it was started from a local terminalBugfix : fixed an issue with backslash characters being duplicated in SSH sessions “Execute command” fieldBugfix : fixed an issue with backslash characters being duplicated in SSH sessions “Username” fieldVersion 12.0 (2019-07-28)New feature : added a new prompt for local terminal

onenote.officeapps.live.com unexpectedly closed the connection

* Request a Connection from the pool of connection threads. */ Connection conn = dataSource.getConnection(); StringBuilder msg = new StringBuilder(); /** * Use Connection to query the database for a simple table listing. * Statement will be closed automatically. */ try (Statement stm = conn.createStatement()) { String query = "show tables;"; ResultSet rs = stm.executeQuery(query); // Store and return result of the query while (rs.next()) { msg.append(rs.getString("Tables_in_JCGExampleDB")); } } catch (SQLException e) { System.err.println(e.getMessage()); } finally { // Release connection back to the pool if (conn != null) { conn.close(); } conn = null; // prevent any future access } model.addAttribute("msgArgument", "Maven Java Web Application Project: Success! The show tables result is: " + msg.toString());...The above code demonstrates how to use JNDI to look up a resource by its name, and use resource’s return class “DataSource” to get a “Connection” from the connection pool. Note, it is very important to release any borrowed resources, and close any resources that needs to be closed.In the example above, Connection, Statement, and ResultSet needs to be closed. We closed Connection explicitly in the finally close of the try/catch block. The Statement is closed automatically as we used try with resources. This approach was introduced recently with Java 7 and allows to close classes automatically on exiting try/catch block, but such classes must implement AutoClosable interface.Since Statement is closed automatically any open resources related to Statement, such as ResultSet are also closed automatically. By closing all borrowed resources, we avoid holding up connection, so that other connection requests are served faster.Also note that we used two names to get two contexts. Those contexts have different scope. The first context retrieved with java:comp/env look up retrieves all configured resources for the web application. After having context with all resources, we need to select a specific

Connection interrupted: 5134: The connection was closed unexpectedly

[08:55:45] FlashFXP 5.4.0 (build 3970)[08:55:45] Support Forums Winsock 2.2 -- OpenSSL 1.1.0e 16 Feb 2017[09:59:24] [R] Connecting to censored -> DNS=censored IP=censored PORT=2295[09:59:24] [R] Connected to censored[09:59:24] [R] Host key algorithm ssh-rsa, size 2048 bits.[09:59:24] [R] Fingerprint (SHA256): censored[09:59:24] [R] Key exchange: [email protected]. Session encryption: [email protected], MAC: , compression: none.[09:59:24] [R] Auth Type: Password[09:59:24] [R] Authentication succeeded[09:59:24] [R] SSH Connection open[09:59:24] [R] Connection established with OpenSSH_7.2p2 Ubuntu-4ubuntu2.4 (SFTP v3)[09:59:24] [R] SFTP Connection Ready[09:59:24] [R] Directory changed to: /mnt/storage/home/public_html/priv/[09:59:24] [R] Retrieving directory listing...[09:59:24] [R] List Complete: 1 KB in 0,12 seconds (1,8 KB/s)[09:59:24] [R] Downloading: /mnt/storage/home/public_html/priv/file.mkv[10:01:16] [R] SFTP Connection closed[10:01:16] [R] Download Error: Connection closed by lower level protocol[10:01:16] [R] SSH Connection closed[10:01:16] [R] Transfer Failed: file.mkv[10:01:16] [R] Connection Lost: censored (Duration: 1 minute 53 seconds)[10:01:16] Transferred 0 Files (0 bytes) in 1 minute 53 seconds (0,0 KB/s)[10:01:18] [R] Attempting to Reconnect.[10:01:18] [R] Connecting to censored -> DNS=censored IP=censored PORT=2295 (attempt # 1)[10:01:19] [R] Connected to censored[10:01:19] [R] Host key algorithm ssh-rsa, size 2048 bits.[10:01:19] [R] Fingerprint (SHA256): censored[10:01:19] [R] Key exchange: [email protected]. Session encryption: [email protected], MAC: , compression: none.[10:01:19] [R] Auth Type: Password[10:01:19] [R] Authentication succeeded[10:01:19] [R] SSH Connection open[10:01:19] [R] Connection established with OpenSSH_7.2p2 Ubuntu-4ubuntu2.4 (SFTP v3)[10:01:19] [R] SFTP Connection Ready[10:01:19] [R] Directory changed to: /mnt/storage/home/public_html/priv/[10:01:19] [R] Downloading: /mnt/storage/home/public_html/priv/file.mkv[10:04:17] [R] SFTP Connection closed[10:04:17] [R] Download Error: Connection closed by lower level protocol[10:04:17] [R] SSH Connection closed[10:04:17] [R] Transfer Failed: file.mkv[10:04:17] [R] Connection Lost: censored (Duration: 2 minutes 59 seconds)[10:04:17] Transferred 0 Files (0 bytes) in 4 minutes 54 seconds

Message erreur ERR CONNECTION CLOSED

To use the better route. The default is 0 (the connection never times out). To take advantage of this feature, change the timeout to a new value.We modified the following command: timeout floating-conn.Configurable timeout for PAT xlate8.4(3)When a PAT xlate times out (by default after 30 seconds), and the ASA reuses the port for a new translation, some upstream routers might reject the new connection because the previous connection might still be open on the upstream device. The PAT xlate timeout is now configurable, to a value between 30 seconds and 5 minutes.We introduced the following command: timeout pat-xlate.This feature is not available in 8.5(1) or 8.6(1).Increased maximum connection limits for service policy rules9.0(1)The maximum number of connections for service policy rules was increased from 65535 to 2000000.We modified the following commands: set connection conn-max, set connection embryonic-conn-max, set connection per-client-embryonic-max, set connection per-client-max.Decreased the half-closed timeout minimum value to 30 seconds9.1(2)The half-closed timeout minimum value for both the global timeout and connection timeout was lowered from 5 minutes to 30 seconds to provide better DoS protection.We modified the following commands: set connection timeout half-closed, timeout half-closed.. 127.0.0.1 unexpectedly closed the connection try check the connections err connection closed This video is about how to fix this site can't be reached - unexpectedly closed the connection or err connection closed.

Postgresql server closed the connection unexpectedly

Later be used with other keywords like `Get Connection` or `Switch Connection` in order toget information respectively to switch to a certain connection that has that alias.When a connection is closed, it is no longer possible to switch or get information about the other connections thathave the same alias as the closed one. If the same ``alias`` is used for more connections, keywords`Switch Connection` and `Get Connection` will switch/get information only about the last opened connection withthat ``alias``.| `Open Connection` | my.server.com | alias=conn || `Open Connection` | my.server.com | alias=conn || `Open Connection` | my.server.com | alias=conn2 || ${conn_info}= | `Get Connection` | conn || `Should Be Equal As Integers` | ${conn_info.index} | 2 || `Switch Connection` | conn || ${current_conn}= | `Get Connection` | conn || `Should Be Equal As Integers` | ${current_conn.index} | 2 |Note that if a connection that has the same alias as other connections is closed trying to switch or get informationabout the other connections that have the same alias is impossible.| 'Open Connection` | my.server.com | alias=conn || 'Open Connection` | my.server.com | alias=conn || `Close Connection` || `Switch Connection` | conn || `Run Keyword And Expect Error` | Non-existing index or alias 'conn'. | `Switch Connection` | conn | Definition at line 442 of file library.py.◆ __init__() def SSHLibrary.library.SSHLibrary.__init__ ( self, timeout = DEFAULT_TIMEOUT, newline = DEFAULT_NEWLINE, prompt = DEFAULT_PROMPT, loglevel = DEFAULT_LOGLEVEL, term_type = DEFAULT_TERM_TYPE, width = DEFAULT_TERM_WIDTH, height = DEFAULT_TERM_HEIGHT, path_separator = DEFAULT_PATH_SEPARATOR, encoding = DEFAULT_ENCODING, escape_ansi = DEFAULT_ESCAPE_ANSI, encoding_errors

Unexpectedly closed Connection - page 2

AZs, single or multi-region✅ Connections from other AZ remain⌛Wait 15 seconds TCP timeout✅ Transactions continue – no errors✅ RF5 is resilient to one more failure, compute or storage. Only the connections to the node failing are canceledThese are the two most common situations in a public cloud running on commodity hardware where failures are the norm:One failure can be an Availability Zone (AZ) inaccessible for a short or long timeIn the case of an AZ down for a long time, another failure happening in the remaining AZsIt is easy to test resilience by simulating a failure in a test environment. Connect to one node and run the following from psql:create extension if not exists pgcrypto;create table demo ( id uuid primary key default gen_random_uuid(), value int, ts timestamptz default now() );\timing onbegin transaction; insert into demo (value) select generate_series(1,1000);\watch count=10commit;It is running for 10 seconds, stop the node in the middle of it. PostgreSQL or Aurora will get an error:INSERT 0 1000Time: 3.433 msINSERT 0 1000Time: 3.545 msINSERT 0 1000Time: 3.480 msINSERT 0 1000Time: 3.502 msFATAL: 57P01: terminating connection due to administrator commandLOCATION: ProcessInterrupts, postgres.c:3300server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.The connection to the server was lost. Attempting reset: Failed.The connection to the server was lost. Attempting reset: Failed.Time: 0.612 ms!?> commit;You are currently not connected to a database.!?>!?>In YugabyteDB, you can connect to any node. Typically, the application in one AZ connects to nodes in the same AZ. To simulate a failure, stop a node (not the one you are connected to). You see a higher latency at the time of failure, a maximum of 15 seconds, as it is the TCP timeout, and the transaction continues and can be committed:INSERT 0 1000Time: 32.165 msINSERT 0 1000Time: 13647.341. 127.0.0.1 unexpectedly closed the connection try check the connections err connection closed This video is about how to fix this site can't be reached - unexpectedly closed the connection or err connection closed.

SMTPServerDisconnected: Connection unexpectedly closed - Odoo

While connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "GET /status.php HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:44:58 [error] 30906#0: *19791 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "GET /status.php HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:45:30 [error] 30906#0: *19793 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "GET /status.php HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:46:17 [error] 30906#0: *19795 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "GET /status.php HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:03 [error] 30909#0: *23972 upstream prematurely closed connection while reading response header from upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d91/UNADJUSTEDNONRAW_thumb_d91.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:03 [error] 30909#0: *23971 upstream prematurely closed connection while reading response header from upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d90/UNADJUSTEDNONRAW_thumb_d90.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:03 [error] 30906#0: *24130 upstream prematurely closed connection while reading response header from upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d91/UNADJUSTEDNONRAW_mini_d91.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:35 [error] 30909#0: *23972 upstream prematurely closed connection while reading response header from upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d93/UNADJUSTEDNONRAW_mini_d93.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:35 [error] 30909#0: *23971 upstream prematurely closed connection while reading response header from upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d92/UNADJUSTEDNONRAW_mini_d92.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:35 [error] 30906#0: *24130 upstream prematurely closed connection while reading response header from upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d92/UNADJUSTEDNONRAW_thumb_d92.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:35 [error] 30908#0: *24003 upstream prematurely closed connection while reading response header from upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "GET /index.php/apps/files/?dir=/ HTTP/1.1", upstream: " host: "cloud.2rock.fr", referrer: " 11:54:35 [error] 30909#0: *23972 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d94/UNADJUSTEDNONRAW_mini_d94.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:36 [error] 30909#0: *23972 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d95/UNADJUSTEDNONRAW_mini_d95.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:40 [error] 30906#0: *24130 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d94/UNADJUSTEDNONRAW_thumb_d94.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:40 [error] 30906#0: *24130 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d96/UNADJUSTEDNONRAW_mini_d96.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:40 [error] 30909#0: *23971 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d93/UNADJUSTEDNONRAW_thumb_d93.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:40 [error] 30909#0: *23972 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d95/UNADJUSTEDNONRAW_thumb_d95.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15 11:54:41 [error] 30909#0: *23971 connect() failed (111: Connection refused) while connecting to upstream, client: 81.57.19.196, server: cloud.2rock.fr, request: "PUT /remote.php/webdav/Pictures/Phototh%C3%A8que.photoslibrary/resources/proxies/derivatives/0d/00/d97/UNADJUSTEDNONRAW_mini_d97.jpg HTTP/1.1", upstream: " host: "cloud.2rock.fr"2016/10/15