Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

[AEM Gems Webinar] Accelerating Experience Manager as a Cloud Service development with Rapid Development Environments
SOLVED

how to trouble shoot" Replication test failed Connection refused: connect"

Avatar

Level 2

 

Replication test to http://localhost:4503/bin/receive?sling:authRequestLogin=1

2022-12-24 18:00:00 - Create new HttpClient for Default Agent
2022-12-24 18:00:00 - * Auth User: admin
2022-12-24 18:00:00 - * HTTP Version: 1.1
2022-12-24 18:00:00 - * Connect Timeout: 900000
2022-12-24 18:00:00 - * Socket Timeout: 900000
2022-12-24 18:00:00 - adding header: Action:Test
2022-12-24 18:00:00 - adding header: Path:/content
2022-12-24 18:00:00 - adding header: Handle:/content
2022-12-24 18:00:00 - deserialize content for delivery
2022-12-24 18:00:00 - No message body: Content ReplicationContent.VOID is empty
2022-12-24 18:00:00 - Sending POST request to http://localhost:4503/bin/receive?sling:authRequestLogin=1
2022-12-24 18:00:02 - Error while sending request: java.net.ConnectException: Connection refused: connect
2022-12-24 18:00:02 - Replication (TEST) of /content not successful: java.net.ConnectException: Connection refused: connect Conversation follows
2022-12-24 18:00:02 - ------------------------------------------------
2022-12-24 18:00:02 - Sending message to localhost:4503
2022-12-24 18:00:02 - >> POST /bin/receive HTTP/1.0
2022-12-24 18:00:02 - >> Action: Test
2022-12-24 18:00:02 - >> Path: /content
2022-12-24 18:00:02 - >> Handle: /content
2022-12-24 18:00:02 - >> Referer: about:blank
2022-12-24 18:00:02 - >> Content-Length: 0
2022-12-24 18:00:02 - >> Content-Type: application/octet-stream

 


Replication test failed
Connection refused: connect

1 Accepted Solution

Avatar

Correct answer by
Level 6

Hello @Anilkumar0208 

 

We can look for messages like "Error while sending request: java.net.ConnectException: Connection refused" which is appearing in your logs.

Can you please try if a publish instance is running at http://localhost:4503/? The AEM author is unable to connect

View solution in original post

2 Replies

Avatar

Correct answer by
Level 6

Hello @Anilkumar0208 

 

We can look for messages like "Error while sending request: java.net.ConnectException: Connection refused" which is appearing in your logs.

Can you please try if a publish instance is running at http://localhost:4503/? The AEM author is unable to connect

Avatar

Level 4

It looks like there is an issue with the connection to the server at localhost:4503. The error message "Connection refused: connect" indicates that the server is not responding to the connection request.

There could be a few reasons for this:

  1. The server at localhost:4503 is not running. Make sure that the server is up and running, and that the port (4503 in this case) is open and accessible.

  2. There is a problem with the network connection between the client and the server. Make sure that there are no firewall rules or other network restrictions that might be blocking the connection.

  3. There could be a problem with the client configuration. Make sure that the client is properly configured and has the necessary permissions to connect to the server.

You may also want to check the logs on the server and client to see if there are any additional clues as to the cause of the issue.