View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003800 | SymmetricDS | Task | public | 2018-11-19 16:17 | 2019-02-27 13:30 |
Reporter | poseidon_diver | Assigned To | admin | ||
Priority | normal | ||||
Status | closed | Resolution | no change required | ||
Product Version | 3.9.15 | ||||
Summary | 0003800: 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 | ||||
Tags | No tags attached. | ||||
|
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. |
|
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 |
|
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. |
|
Connection refused is a network/environment issue. Use the forums for support. Closing as nothing to fix. |
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 |