View Issue Details

IDProjectCategoryView StatusLast Update
0003800SymmetricDSTaskpublic2019-02-27 13:30
Reporterposeidon_diver Assigned Toadmin  
Prioritynormal 
Status closedResolutionno change required 
Product Version3.9.15 
Summary0003800: Could not communicate with outside:001:001 at http://<servername>:31415/sync/outside because: Connection refused
Description INFO [inside] [PushService] [inside-push-default-2] Could not communicate with outside:001:001 at http://<servername>:31415/sync/outside because: Connection refused
TagsNo tags attached.

Activities

hanes

2018-11-19 18:29

developer   ~0001339

It looks like your node is misconfigured and is using a hostname of "<servername>" and not a valid hostname to reach the "outside:001:001" node.

poseidon_diver

2018-11-19 21:57

reporter   ~0001355

Hi,

<servername> is used to obfuscate the actual server name,

What caught my eye and what I think the problem is the extra "001" in "outside:001:001"

Bruce

hanes

2018-11-28 18:19

developer   ~0001358

No, the formatting of the 001:001 is fairly common. For example:

Could not communicate with corp:000:000 at http://localhost:31000/sync/corp-000

is what I get when I bring a node online where the main node (corp) is not running.

One thing you could try is opening up a browser on the "inside" node and then issuing a "ping" via a URL:
Something along the lines of:
http://<servername>:31415/sync/outside/ping

If the SymmetricDS instance is accessible on that port from the inside node it should return the text "pong" as a response.

admin

2019-02-27 13:30

administrator   ~0001393

Connection refused is a network/environment issue. Use the forums for support. Closing as nothing to fix.

Issue History

Date Modified Username Field Change
2018-11-19 16:17 poseidon_diver New Issue
2018-11-19 18:29 hanes Status new => feedback
2018-11-19 18:29 hanes Note Added: 0001339
2018-11-19 21:57 poseidon_diver Note Added: 0001355
2018-11-19 21:57 poseidon_diver Status feedback => new
2018-11-28 18:19 hanes Note Added: 0001358
2019-02-27 13:30 admin Assigned To => admin
2019-02-27 13:30 admin Status new => closed
2019-02-27 13:30 admin Resolution open => no change required
2019-02-27 13:30 admin Note Added: 0001393